I know what you’re thinking … “A WordPress post?! I thought this guy drank the Ruby on Rails Kool-Aid.” Truth is, I never really stopped WordPress development, I was simply looking to expand my horizons a bit. I still use WordPress daily for personal blogs and work-related activites. It’s good at its job, which is either as a blog or an easily extendable CMS-like solution. Anyways … in developing my WordPress themes, I try to keep everything as modular as possible. Here’s my general file structure for anything not WordPress-centric:
|- assets/ |- img/ |- inc/ |- functions/ |- templates/ |- vendor/ |- js/ |- sass/
Here’s where things get a little more in-depth. First, everyone reading this will know that WordPress requires a functions.php file in the top level of a theme directory. Usually, people will add all of their theme configuration options to this file, resulting in a file hundreds of lines long. I’d rather write code than dig through it, so I extracted everything out into its own relevant file placed in the aforementioned functions folder. That said, here’s my functions.php: I won’t be going over the screenshot in depth, but the gist is simple: first, I define any constants I’ll be using a lot in my theme. Next, I have a series of includes that hold relevant code for their name. So, if I create any custom posts? In custom-post-type.php it goes. That ensures I always know where my code lies, even if I come back to the project 6 months down the road. I know this was a quick and dirty post, but I hope it helps anyone struggling to maintain a clean directory structure in the face of an ever-evolving theme!