This weekend I decided to work on my own projects for a change, something I had not had the luxury to do for quite a while, client work always coming first. I took the time to complete a redesign of this site which I’ve worked on very sporadically for months. Earlier today I finally updated pixelyzed.com to version 5.0 which is a big step forward for me, not just only for pixelyzed.com itself but for my entire WordPress workflow. Pixelyzed.com is now powered by the Genesis framework from StudioPress with the help of the powerful Dynamik Web Site Builder child theme made by CobaltApps.
I will soon be writing reviews for some of the main WordPress plugins and theme frameworks that I use in my client projects. But before I do that, I wanted to write a post explaining the basic criteria I use to evaluate a theme because they are not necessarily the same you’ll read about in most other reviews out there that focus on workflow features alone. I’ve read many theme framework reviews in the last 3 years and I found most of them to be lacking in substance. That’s not because they were bad reviews or because the people writing them were doing a bad job, they were just aimed at a specific kind of user (non-coders, beginners or casual users) and limited themselves to what I consider “surface” criteria that become far less relevant when you build Web sites with WordPress for a living. When your business and reputation depend on the quality of the themes and other products you install on client sites, “features” like drag and drop and especially “no coding required” quickly take a second or third seat to more important matters like performance, stability and flexibility.
So here I’ll explain 4 of the basic criteria I use to evaluate a theme framework’s suitability for inclusion in my workflow to be used on specific projects. I’m concentrating on issues I rarely if ever see mentioned in theme reviews so I won’t talk about things like ease of use or flexibility of any workflow related features here. Those things will be included in my specific theme framework reviews. I hope this article will help you make more informed decisions if you are looking for a theme framework to use on a client site and are not sure which one would be the best fit for your workflow and your client’s needs.
WordCamp Montréal 2013 is coming in late June and, as is becoming a tradition for me, I will be attending this great event for the 4th time! It seems that the more experience I get with WordPress, the more I get out of WordCamp. There’s always an great roster of presenters every year and I always meet interesting people.
I was nowhere ready for it this year but I’m starting to think about presenting at WordCamp eventually. I’ve been working with WordPress almost exclusively for well over 3 years now and my experience with multisite used for multilingual sites could certainly help others. I know it’s a topic that will be touched upon this year but it’s a reality for almost every web site for me. We’ll see!
The talks schedule looks like the best I’ve seen so far this year so if you are near or in Montreal during the last weekend in June (29, 30), don’t miss it! As I’ve said before, the Montréal WordPress community is truly awesome!
See you there!
When I wrote the 2012 version of this post last year, I did not expect it to become the most commented post on this blog ever. It made me realize that there is a real hunger for information about premium WordPress themes and frameworks out there, a need for opinions from people working with some of these products every day and who are not afraid to speak their mind. I like to think I do that here.
I also try to make a distinction between what frameworks would work well for professional WordPress designers and developers versus casual users. The former is what interests me and most reviews out there are targeted at the latter. Also, you often get a review from someone who tinkered with a framework on a test site for a few minutes or hours. I work with the themes I mention here all the time. Testing a theme framework for a couple hours will not give you a perspective on things like:
- How well do upgrades and updates work? Do updates typically break client sites layouts? Do you need to tweak your child themes every time you upgrade the parent theme?
- How does the framework perform on a real live site with real traffic? Is the site slower or faster with this framework compared to others?
- How does the developer handle support? How fast, how helpful are they. This is key when your client work depends on a theme framework so heavily.
This post is also a kind of intro to other posts I’ll write in the coming weeks and months where I explain in more detail the reasons I’d choose a WordPress theme framework over others and I’ll finally write some real in-depth theme framework reviews based on these criteria. That is already started.
But for now, here’s the state of my 2013 WordPress themes toolset…
I have done a few end of year / start of new year posts in the past but this one will not be a look back at the past year. 2012 has been a great year for me and my business, a year of growth and the pain that often comes with it. But I prefer to look forward and distill those lessons into areas of focus for the new year so I can improve where I can and do better in 2013.