That move was not the first time I had made such a change and, if you’ve read the previous 3 articles I wrote on the subject, you’ll see that I’ve been on a journey to find a flexible and powerful theme framework that meets specific criteria that I don’t think are commonly addressed or even talked about in most theme review posts you may have read in the past. The most important of those for me has become stability, both for the product and the vendor.
These State of my Toolset blog posts are becoming a annual tradition on pixelyzed.com and this year will be no different. If 2012 had been a year of all around stability and growth for me and my business, 2013 was one of continued growth in my business but one of significant change in my toolset.
Those changes were brought by the same desire for efficiency and refinement to my workflow that I’ve described before but also because I’ve been going back to some of the core principles I learned and followed when I first learned my craft and started my business in the mid to late 90’s and early 2000s. I was a strong Web standards advocate then, long before it was popular to do so and long before Web professionals realized that clean, semantic HTML code was good for search engines optimization and accessibility (that was before Google…).
While not exactly bad in that respect, I started to feel that iThemes Builder, my main theme framework in 2012 and the first half of 2013, was not as good as I’d liked in that regard. I was starting to find its HTML markup way too heavy with an overuse of div containers, too many CSS classes and not enough effort placed on semantics. This was done by design at iThemes with the goal to make creating different layouts Builder as flexible as possible. I was also starting to find styling it (CSS) tedious and frustrating because of all those extra containers with similar class names that made the code difficult to read.
In addition to that, my business partnership with a designer has given me more time to concentrate on strategy for my clients in the last year and see what I could do to help them better with their business. This entails many things not related to WordPress but, one of the ways I felt I could improve our offering and our WordPress development process is with natural on page SEO. That means, among other things, clean semantic markup and faster load times. So I started re-assessing my themes toolset and looked for ways to improve it. Again, not because Builder was bad at this but it’s not using HTML 5 elements and it’s heavier markup makes it so search engines have to get through more code to get at the actual content. It’s not a ton more, but SEO is so competitive, I figured that every little bit counts.
If like me you use the Genesis Framework (and if you don’t, you really should! ;), you now have less than 24 hours to purchase the Dynamik Web Site Buider (a Genesis child theme) and the Genesis Extender plugin. Both are very powerful products that can help both beginner and seasoned WordPress developers and designers build Web sites on Genesis faster.
Up to now, CobaltApps had been selling these products for a one time fee with unilmited usage rights and free update and support for the life of the product. It is an awesome deal! But in 24 hours, that will change to a yearly fee. The details of that new pricing are not yet known but you now have less than 24 hours to get into the unlimited one time payment option.
This review of WooThemes Canvas is my first theme review after writing my 4 Basic Criteria to Evaluate a Theme Framework post a while ago. I chose to start with Canvas because it’s a theme I’ve used often in the last 2 years and it’s been receiving a few major updates recently. As one of my 4 criteria is stability through upgrades, I can speak to that with more experience with the theme now.
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…