Drupal's theme system, while incredibly customizable, is very
developer-oriented and being
acquainted with Drupal internals, is an implicit requirement. This creates very high barriers for
new non-technical users to take place in the project , but more
importantly .. it leads to a lot of cookie cutter sites, which in turn make
Drupal look like a less capable solution than it actually is. There is a need for a generic template layer,
that allows designers to make use of Drupal's excellent themeability , while not being subjected to the complexity of Drupal iteself.
I have written two articles about it for Drupal.org. The first article Open discussion on Drupal's themeing capabilities and templating engines. covered the problems with Drupal themes as they currently were. It's a justification piece for the next article, Technical discussion on Drupal themeing.. The second article is far more technical in nature, and discussed a high level architectural change for solving the problems encountered currently. This post contains an update on the progress towards this goal, aswell as a discussion of the nuts and bolts of the new system.
An issue has been created on the Drupal issue tracker, that contains the first patch against Drupal HEAD.