Skip to content

Rhaptos Software Development

Personal tools
You are here: Home » Developer Blog » Max's Blog » Plone stylesheets, mostly

Plone stylesheets, mostly Plone stylesheets, mostly

Document Actions
Submitted by maxwell. on 2005-07-15 19:12. Style
Updates on what I've been doing, mostly regarding the new Plonish stylesheet

This week I believe I spent most of my time working on the last minutiae of the Plone-like stylesheets for the software release (well, I'm sure there will be more minutiae to come, but I'll wait till other people spot them before I fix them), even though I didn't quite make my final commits till Brent had already finished up the release (sorry, Brent).

This was mostly the NS4 style sheet (should we even bother anymore?) and the Print style sheet (yeah, I guess we should bother), both of which, of course, have their own special issues to deal with and took longer than I had hoped. But they look like Plone now, instead of Summer Sky (reminder to self: recommit the Summer Sky ns4.css and print.css files).

I also made some changes to the module EIP CSS, since it a) had some issues when people tried using it on bokken, and b) had room for improvement in terms of making it usable in both the Plone look-and-feel and the Summer Sky look-and-feel.

I also spent some more time splitting content stylesheets into two different files. Instead of having a document.css and sidebar.css, I have been calling them metacontent.css and content.css (don't worry, they're not set in stone). Basically, everything around the module (such as the header, footer, sidebar) is styled in metacontent.css and everything inside the module is styled in content.css. The reason for doing this was so that we could pull the content.css file into the EIP module-editing interface (i.e. the one on beta), therefore eliminating the need to duplicate any changes I make to the basic content style in module_edit.css (the file currently used to make things like sections look like sections, notes to look like notes, etc., when using EIP). But I came across a few areas of uncertainty, such as what to do with my specific stylings to table cells (which file do they go in?, will they conflict with Plone?), and tags like pre, code, and blockquote (will they turn out looking more like Plone than Sky?, will I need to add counterbalancing code?, where will that code go?).

Developer Blog
« November 2008 »
Su Mo Tu We Th Fr Sa
            1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30            
2008-11-10
13:39-13:39 Suggestion for live site slowness reports
Categories:
Content (55)
Copyright (0)
Deep Code (3)
Development (203)
Markup (22)
Metadata (1)
Printing (7)
Style (9)
Testing (2)
Usability (6)