this page is based on some of the ideas put forward in ThemeStructureIdea some time ago and trying to apply the ideas in userPageLaetzer.

basic folder setup
{CODE()}
<theme>/templates/
<theme>/<style>/
{CODE}

the style folder could contain the following
{CODE()}
<theme>/<style>/css/layout.css
<theme>/<style>/css/style.css
<theme>/<style>/images/
{CODE}

a structure like this would enable us to have themes such as (from laetzers page)
* portal (3 columns)
* classic (2 columns)
* blog (1 main-column, vertical, compliant, accessible, post/comment-centric)
* wiki (center+menu, edit-centric, loose hierarchy)
* directory (center+menu, lot's of links, teaser/header-centric, deep hierarchy)
* minimal/text (3 or 4 "horizontal columns", basic)
* ad (horizontal, flashy, small, pictures, drop down menus, flat hierarchy,)

within a theme you can have as many styles as you like, making it possible to categorise your styles and allowing the user to figure out what they want.

should layout.css be "part of the theme"?
by this i mean, should layout.css be placed in the theme folder for every style to be included? is that just going to produce a ton of differently coloured clones?

^minor update:
to allow for different media types we could include files that use filenames such as these appropriately
style.css
style_screen_tv_projection.css
style_print.css
style_handheld.css
(where style.css gets included as @media all)^

please add any thoughts and ideas. this is just a draft...
Page History
Date/CommentUserIPVersion
29 Apr 2006 (09:09 UTC)
xing194.152.164.457
Current • Source
xing194.152.164.456
View • Compare • Difference • Source
xing194.152.164.455
View • Compare • Difference • Source
xing194.152.164.454
View • Compare • Difference • Source
xing194.152.164.453
View • Compare • Difference • Source
xing194.152.164.451
View • Compare • Difference • Source