Uhm. Okay, confused, because it sounds like you're saying yes, here is reason to use multiple steps, and then following that up by saying multiple steps are being avoided. So should I set a bunch of variable strings, do the generate_css and whatnot, or should I just go from globals into the css and skip the tossed-salad put-it-together variable string step?

Part of the reason to ask is b/c after conferring with Afuna about the style, it looks as though it'd be best to minimize the changeable parts in the end-user's wizard. That means the CSS doesn't really have a plethora of variables strung together, but mostly fixed values with maybe just one being locally settable. That makes it seem (to me, in this case) like overkill to do a variable string setting when of the four, three are constants. Or for standards compliance should I treat even the constants as potentially adaptable?

Also, you might want to add a few notes in the main post about how to enter comments or descriptions. One thing that bugs the hell out of me is the lack of descriptions in the current wizard, because styles are no more self-commenting than code! I believe the transmog style has descriptions, but the syntax isn't immediately obvious. So maybe a paragraph about where and how to comment, and where those comments will show up -- that is, between doing { des = "here's a bit of info" ; } --- and why the closing semi-colon is INSIDE the curly brackets even though the curly brackets don't enclose the entire line! -- versus doing ## comment goes here ## aka the propgroup lines, versus putting it in the CSS.

Y'know, in all your copious spare time.