The theme around here is feeling a little stale to me. I’ve started working on a new theme for this blog, using WordPress-Skeleton as the base for the git repo and the Bones theme as my theme’s starting foundation.
So far I’ve been enjoying both immensely:
It was easy to move my git repo to use this format (you can see the commits required here). The primary reason I moved to this structure was it returned the power of development back to me as opposed to being completely at the whims of WordPress.
Now WordPress is in a tidy gitsubmodule and all my custom content (theme) is in its own folder and isn’t affected by WordPress upgrades.
One thing I haven’t yet decided how to manage is plugins: should I control which plugins I use and commit that to the repo, or do I let WordPress manage that? Anyone have any thoughts?
Bones WordPress Theme
I haven’t yet fully dived into Bones but so far I’ve enjoyed the clarity of its comments and the strong base it provides. The default HTML structure is semantic and intuitive and I’ve had no confusions when it comes to structure.
bones.php file was the one that managed those tasks. I’m chalking this up to my naivety when it comes to WordPress theme development, as up until now I’ve only worked on child themes.
For my own development pleasure I added grunt to my Bones theme, making it easy to use SASS and LiveReload. I opened an issue on the Bone’s GitHub page to add that work to trunk however I may just have to suffice myself with an additional blog post (oh the horror ).
I hope to get the new theme in Beta state in the near term so I can switch the blog over to it and then enjoy applying updates as I dev.
If you want to watch while I work all updates are going to be pushed to the
new-theme branch of my public harrywolff.com git repo.