Mateo,
I recently tested building a theme using
BlankTheme as a base to start from.
My thoughts:
While its powerful, its also complex.
The trade-off comes in simplicity versus the upgradeability, and reconfiguration of a standards / cross-compatible theme "framework".
I was several hours into the test case when I noticed the YAML licensing - you must either have a link at the bottom of the page, or pay $59 euro per site or $119 euro per developer (ie, unlimited usage by one developer FOR clients - ie, custom work goes to a single client, not redistributed en masse).
I don't disagree with the licensing costs (its a lot of work to maintain a well coded theme!), but presenting it more matter-of-fact to Postnuker's would probably be prudent - Non-commercial AND commercial must all have a backlink unless a license is purchased.
Usability / Standards
I found the original code base and resulting themes to be very well put together in their final, rendered versions. Due to the complexity (many different templates and
CSS files and permutations of such depending on column choices), you must have a good grasp on
CSS, sub-templating and a basic understanding of the YAML methodology to customize it to any extent. Simple styling customizations are as easy as finding the correct
CSS element.
Saying that, the
CSS and templates themselves are clean and well-laid out, and well commented.
Desires / Wish-list
I'm always on the prowl for good,
CSS based, cross-compliant themes. I love to start with a good clean base that has some built in cross-compliancy.
What would be the perfect situation is if with YAML and
BlankTheme, one could configure a basic theme and perform an "export" to provide a set of templates and
CSS just for that specific configuration - cutting out the "extra" fluff that would not be used unless you choose a different theme configuration.
The same can be done by "carving" out and combining the basic YAML templates and
CSS (which is what I did when testing it - so that I know have a single template file, with a few sub-tempaltes for modules, and a single
CSS, stripped of much of the YAML stuff).
Then, a user could create a nice, clean, cross-compliant theme BASED on YAML, but not tied to it and the resulting bloat (again, a tradeoff for flexibility and future reconfigurability).
(And the YAML docs suggest as much - remove everything your theme doesn't need in the long run.)
As such, I see it as a good theme framework for the developer who would like to have flexibility and semi-upgradeability in their themes, or for a team that may choose the YAML framework to maintain their theme code.
I generally theme in one-shot efforts (theme once, slight tweaks, but if a new layout or different theme is needed, start from a nice clean base again). so the benefits of YAML are a little overkill as I understand BUT it would be a benefit to someone that needs all YAML offers - screen, print, remote
CSS, flexibility in layout for future changes, etc.
edited by: uheweb, May 23, 2008 - 03:22 PM
Posted: 23.05.2008, 21:27
Nice!
