Combine with this approach...

pull some of our CSS out to a settings.css file that has really basic CSS stuff, like header height, fixed width, font, block spacing; allow the theme wizard to write it out and encourage customisation

This is a nice elegant solution, as the end result is easy to edit and explain too, and it pulls away complexities without changing our core architecture at all.

Composr should be smart enough to merge global.css and settings.css at run-time, for performance reasons.

All done except:

1) Different background settings (fixed position, standard, tiling)
REASON) Trivial CSS changes that people can make themselves. At this point we'd be second guessing people and nannying them too much.

2) Save theme creation options within the Theme, and allow re-application of the original parameters, or tweaked versions there-of, to any theme aspects of the users choice.
REASON) New Equation solver added to edit-css screen to allow changes on CSS done easily. For anything else user can add a new theme and copy the theme image back over.

3) The stuff in the note above. People need to learn CSS or pick a closer base theme. Allowing little tweaks won't really get people much closer to their goal so is a distraction.


Also instead of removing the old themegen algorithm, we're providing a choice. This gives the best of both worlds.

Also dark themes are now supported.