The Death of WordPress Theme Frameworks

WordPress theme frameworks are on their way out. They’re dying a slow death. At least that’s what I think.

Nathan Rice recently wrote an article with his thoughts about theme frameworks – in defense of them – however he clearly has some bias towards them since he’s working on possibly the only framework worth considering – Genesis 2. It’s certainly the only framework people seem to talk about these days. I get the impression Canvas from WooThemes is still enjoyed – and others will likely say they are doing well – but in my opinion there’s no longer any need for them.

WordPress Framework

People/ Users?

Defining ‘people’ or ‘users’ is hard. These are terms that can mean different things to different people. So, in this article, I am going to refer to users as the customers I am most familiar with. This isn’t developers – regular people who want a WordPress theme for their site. They don’t know much about design, or about programming (likely they don’t know anything). Possibly they have been tasked with getting a theme for their company to use on their corporate blog.


In thinking about this I wanted to look at the past and why frameworks were first created.

WordPress theme frameworks became popular when WordPress was simpler. People wanted control panels to edit settings, areas to upload headers, built-in thumbnails, custom menus, all these clever things that made their website sparkle.

As time went on these features were slowly developed and integrated into WordPress core. Much of this was driven by and the users there wanting to be able to customise their sites more thoroughly.

Who killed WordPress Theme Frameworks?

Where WordPress kept improving, the requirements for frameworks didn’t really change. So over time WordPress got all the features people wanted and the functionality in themes became redundant. Reading the feature list for a framework these days is like reading the WordPress feature list.

Then we had plugins. Theme Frameworks used to market themselves on their SEO abilities – but frankly that was a sham. Sure – many of them did things that helped with SEO – but many more said they were SEO optimised when they were no such thing. Then the WP SEO plugin came along and made all those claims redundant. There’s still certain things that can be done in themes to help with SEO (semantic well structured html) but in general as long as you’re sensible (and use WP SEO) then you don’t really need a special theme.

Grandchild Themes

Another problem has been caused by WordPress theme shops – myself included – releasing child themes for their frameworks. The problem with this is that we then go back to the problems child themes were created to address. Child themes were meant to be a way for users to edit themes without worrying about code updates; but since the child themes were being sold – new methods were needed to make changes to the styles – which meant additional settings and other methods that are the exact thing child themes are meant to solve.

Grandchild themes are one possible solution to this – children of child themes. However these add additional layers of complexity and confusion, not to mention overhead on the server side (additional file operations). The other solution is to stop using theme frameworks and create child themes as originally planned.

Elemental 2

Last year I mentioned I was working on Elemental 2. I also mentioned my new philosophy towards theme development. When I started it felt really liberating. I was able to cut loads of code and the theme got lighter and lighter and cleaner and cleaner. Eventually the only thing that was left that wasn’t a standard theme element was the settings code – and then the Theme Customisation API was released and even that wasn’t needed.

So I stopped using frameworks. Since then I have worked on a Mimbo Pro, and 3 new themes – Opti was released last year – Isca was released today on – and Traveller is in progress. None of them use a framework, and they have very few customisation options. They are simply good quality themes that I’ve put a lot of time and effort into.

A Solution?

The way I see it there’s 2 solutions.

  1. Build the theme from scratch every time.
  2. Use a starter theme like _s.

For the recent Binary Moon redesign I made the theme from scratch. For Pro Theme Design – Darren and I have developed our own starter theme. It evolves with each new theme we make, and it’s sped us up quite nicely without giving us the overhead and complexity of a framework.

The Future

I’m sure frameworks will be around for a while longer, but in my opinion they create more work than they save. Anything added through a framework that you would want to update or reuse in multiple themes should be developed as a plugin since that offers the most flexibility.

So what do you think?

Was it good/ useful/ a load of old rubbish? Let me know on Mastodon, or BlueSky (or Twitter X if you must).

Link to this page

Thanks for reading. I'd really appreciate it if you'd link to this page if you mention it in your newsletter or on your blog.

WordPress News

The latest WordPress updates from the WPBriefs Podcast.

Related Posts

01 Apr 2015

The State of WordPress Themes #wcldn

I recently spoke on a panel at WordCamp London 2015e. Lance – who used to be the Theme Team lead at – asked me if I wanted to speak on a panel with him at WordCamp London 2015. I’ve...
13 Oct 2016

Lessons Learned from 20 Theme Releases on

In 2007 I partnered with Darren Hoyt to release Mimbo Pro, one of the earliest premium WordPress themes. In 2012 Mimbo Pro was published on Last week – on October 5th 2016 to be precise – my 20th theme...
27 May 2013

WordPress: 10 Years Young, What Does The Future Hold?

WordPress is now 10 years old. I started using wordpress 9 years ago – which means I joined the WordPress community early on. The reason I chose WordPress is simply because of the fabled 5 minute install process – I...
04 Nov 2016

Automating WordPress Development with Gulp, Bash, and PHP

When I wrote about the things I had learned from releasing 20 WordPress themes, I mentioned that I had automated as much as I could. One of the things I automated was the build and deployment process for my themes...
02 Feb 2012

WordPress Theme Framework: Less Is More – Or Is It?

I have a conundrum. I want to improve Elemental – my WordPress theme framework. I want to make it lean and fast; but this will involve removing functionality. This in turn means that when people upgrade their themes things may...
16 Sep 2016

What is the Difference Between and

Recently, I’ve received a couple of emails asking about the difference between and versions of WordPress. The reason for the confusion is that I sell themes for both sites – and I often get people buying my themes...