Long-time readers of this blog will be aware that I have been a vocal supporter and proponent of the Thesis framework for WordPress for quite some time. This site runs on Thesis, and I am always keen to recommend it to others (for crying out loud, there’s a giant ad for Thesis in my sidebar). That being said, I’ve recently been considering dropping Thesis from this blog and replacing it with my own custom theme.
Why am I thinking about this? Over the past few months, I’ve been working on a side project developing a custom CMS and blog using WordPress for the Chicago Photography Center. When I started the project, I considered using Thesis for the theme/framework…and decided that with the very high level of customization that was going to be required, it was going to be a better solution to develop a custom theme (that, and I wanted to flex my PHP chops).
In the process, I learned a LOT about theme development. And when I had to do some coding updates the other day for It Builds Character, I was actually a little annoyed to have to do them in Thesis, when I had just spent the previous few months wallowing in my own code. This made me start to reconsider my choice of Thesis for this blog (and possible IBC). Here are some of my reasons why.
Another WordPress add-on that I love is W3TotalCache. This is a plugin which is useful for dramatically increasing the performance of your WordPress site through a mixture of page/object caching, CDN configuration, and minification. However, I’ve often run into issues getting this plugin to work – especially when I try to mix the Thesis dynamic CSS file with the minification and CDN delivery in W3TC.
I’m not alone – if you Google “thesis w3 total cache” you will find a multitude of people having issues with the combination of W3TC and Thesis. Of course, one could make the argument that this is more of a W3TC issue than a Thesis one, and you’re probably right. That being said, I have a greater chance of the developer of W3TC testing his code against a stock WordPress install than Thesis (and comments I’ve seen have led me to believe that the developer has no interest in testing against Thesis).
This is true of other plugins as well – when I look to install or update a plugin, WordPress happily reports as to whether or not the developer has tested the plugin with the version of WordPress I am running. There is no such report for Thesis compatibility.
Of course, it’s entirely possible that a plugin would be incompatible with my own custom theme. The upshot is when it’s my code, I can fix it myself. And I don’t run the risk of installing an “upgrade” to my theme that might break plugins or behavior.
This might sound a little wacky, since one of the main benefits of Thesis is its flexibility. And it’s VERY flexible. But it’s not nearly as flexible as writing my own code. For instance, on the IBC site we have enabled the Show interior layout borders option. But when I had to removed it on one portion of the layout, it took a little digging (okay, a VERY little digging, thanks to Chrome Developer Tools) to figure out exactly where Thesis had declared that setting. Which was pretty easy to just override in the custom.css. However, once I did that, I decided I didn’t like the way the sidebar didn’t extend all the way to the footer like the content did. If it was my theme, I could have switched around the layout in the manner I wanted (I’m sure there are all sorts of ways to do this in Thesis, so don’t bother telling me how to do it in the comments – that’s not my point).
Thesis is super powerful and flexible – if you learn Thesis. I know there ‘s nothing I can do in my custom theme that a Thesis guru cannot do with some clever hooks or custom.css wizardry. That being said, I’ve come to the conclusion that I’d rather invest my time and effort in becoming a PHP/WordPress expert, and not a Thesis expert.
One of the things I like about my implementation of Thesis is the use of a “post image” and a “post thumbnail”, which are used outside of the actual post content to create a header image and then a thumbnail for teasers. However the manner of getting them going is a royal PITA in my Thesis implementation. First I have to upload BOTH files (the full post image and the thumbnail) into the Media Library of WordPress (I can’t have Thesis auto-generate my thumbnails because I want to serve them via the CDN). Then I have to copy the URL of the images and paste them into the option boxes in the post.
Is this the end of the world? No. But wouldn’t it be better to just use the built-in “Featured Image” functionality of WordPress? Again, this is totally possible to hook together with Thesis (I am sure) – but why spend all that time coding to hack Thesis, when I could be hacking together my OWN code?
One of the reasons I’m considering investing some time in re-coding It Builds Character into a custom theme is that I am NOT the only person who does work on that site. Occasionally, ChiMomWriter needs something coded or tweaked, and I don’t have time to do it for her – so she hires outside help. Outside help that not only needs to know WordPress (and be capable of understanding my strange configurations of it) but also understands Thesis. It’s basically a secondary level of software knowledge required. Granted, there are eleventy-billion self-granted Thesis gurus out there, but there are even more (possibly within your circle of trust) who know WordPress alone.
Absolutely not. By no means am I trying to say that Thesis is a bad product or that nobody should use it. Quite the contrary – if you aren’t interested in doing anything more than very light coding, Thesis is a GREAT way to add a ton of power and flexibility to your WordPress site. I will continue to recommend it to just about anyone (and if you DO decide to go with Thesis, please feel free to use my affiliate link). But as I’ve learned more about theme development, I feel like I’ve “outgrown” Thesis, and I’d rather expend my skull sweat on writing my own code instead of getting to be a SME on Thesis.
What about you? If you are currently using the Thesis framework, what do you like about it? Have you considered switching to your own custom theme? Let me know in the comments!