I'm a happy user of Scribbish. It's a great foundation, simply and easy to mod. I think it's great to use it as inspiration for an upgrade of the typo theme system.
If you want to get CSS happy, I'll suggest generating CSS from ERb templates. I put together a simple solution for that in Rails - check out this article on my blog: http://blog.hasmanythrough.com/articles/2006/03/23/dirt-simple-rcss- templates The cool thing about using RCSS is you can parameterize style settings in the database and generate the CSS based on those values. The one thing I didn't like about how Scribbish does CSS is that it has so many files. Each reader hits my server six times just to get the CSS for one page! I ended up merging all the modular files into one, and even if it's not a big deal for my server my log files are smaller and easier for me to look at if I need to. But going with an RCSS based system you could generate one file easily. I haven't tried it, but I think my RCSS trick should support partials, which would allow for modular construction of the CSS with little effort. -- Josh Susser http://blog.hasmanythrough.com On Apr 13, 2006, at 11:05 PM, Piers Cawley wrote: > So, I've been looking at Scribbish[1] and the CSS Zen Garden[2] and I > like what I see. In particular, I like the idea of the hAtom > microformat for our articles, and I really like the idea of making > sure we have a robust semantic structure for our core HTML. Every time > someone has to write rhtml in their themes I cringe slightly. > > So, I'm thinking that the whole Theming thing needs looking at. Here's > a few ideas: > > * No more overriding layouts/default.rhtml just to add a couple of > theme specific css files. We've already moved to having most of > the layout's header generated by a helper method, it should not be > beyond our wit to have it do something like: > > <%= render :partial => 'common/stylesheets.rhtml' %> > > as part of its strategy. > > * Nail down the basic semantic structure of our layout and have > more of the > individual divs rendered as partials (and hence more finely > overrideable by a theme). Also, the 'partial' boundary might well > be a good place to insert more granular fragment caching for > better performance. > > * Make use of the hAtom microformat (and possibly other microformats > for other bits and pieces, is there one for tag clouds yet?) > > * Get some feedback from (or become) CSS experts with an eye to > designing a basic page structure that's flexible enough that most > themes can simply provide a css file and a bunch of images. Check > out the CSS Zen Garden for the sort of thing that has been > achieved with 'pure' CSS. > > * As we're breaking themes already, let's break 'em good and proper > so we can rebuild them stronger, better, faster... > > Thoughts? > > 1. http://quotedprintable.com/pages/scribbish > 2. http://csszengarden.com/ > -- > Piers Cawley <[EMAIL PROTECTED]> > http://www.bofh.org.uk/ > _______________________________________________ > Typo-list mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/typo-list _______________________________________________ Typo-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/typo-list
