Its been a while since I last had a redesign on this site. In fact is was early in 2010 and the old design did come off the back of a previous web design I did which I liked rather than one that was designed for purpose. Design is not my strong point and therefore this time I have decided to get a little help from the experts – the guys over at themify.me.
I have previously purchased the Sidepane theme for a project a while ago (purchasing premium themes teaches you lots when you delve into the code) and very much liked the theme. However there were some things that I wanted to change. Like many premium themes these days there are endless theme options and settings and it needed stripping down to the minimum. Therefore I thought I would try my hand at a child theme.
Child theme are used so that you do not alter core theme code. This means when you come to update the theme, as most themes release updates on a regular basis, you won’t lose any of the customisations that you have made. The theory behind this is very true. However in order to get the desired functionality that I wanted, I have ended up with lots of template files and folders, all of which will not get updated and contain important functionality.
The other main thing that I needed to do was to add some more template files for my custom post types of bookmarks and code snippets. These, I suppose where inevitable.
All in all I am happy with the outcome – what do you think?
WordPress theme frameworks are a relatively new thing. In fact they seem to kick off when WordPress introduced the use of child themes back when WordPress 2.7. was released. However they have really caught on over the last couple of years, with many different frameworks now available for use. Here I want to talk about how theme frameworks are built to be used and my thoughts on their success.
As mentioned most theme frameworks rely on the parent and child themes process. You create a child theme based on the parents theme framework and therefore when the framework is update you changes are not lost. Most of the frameworks that I have seen out their including one I have used extensively, Thematic are essentially a parent theme. That is they are a WordPress theme that you add to your
wp-content/themes/ folder. You then build a theme using this parent theme framework as your parent theme. This means you have access to all the frameworks functions and code.
So that all sounds great, but why therefore am I not that keen on using theme frameworks. Well I think it comes down to the fact that I believe that theme frameworks at the moment are going about this the wrong way. They way they are at the moment is more restrictive when they are supposed to add functionality rather than preventing theme authors from doing things in certain ways.
I created a number of child themes for a client recently using the Thematic theme framework. The idea of these child themes was that the parent theme (the framework) could be updated and this would not affect the child themes display at all. However in order to get the design and functionality elements that I wanted I ended up with child theme
functions.php files that we a couple of 100kb each and about 5 or 6 theme template files that would overwrite the template files in the parent framework theme. Surely this cannot be right as child themes are supposed to be lightweight and really on contain a
styles.css file and a
functions.php file so that all the bulk is used from the parent theme.
To me a better way of doing things would be to make it so that the framework was not a theme at all. In fact is was simple a folder that could be added to your own parent theme and then activated with a line of code (like a PHP include) in your themes
functions.php file. This seems to be the approach that themify.me have taken with their theme framework which works well.
I realise that this may well cause a great deal of debate. Maybe I am doing something wrong with the use of parent theme based frameworks. I would love to hear peoples thoughts on this.