Re: Re: life into plone design mailinglist / documentation todo list for 2.0

Can I put forth a plan of action then, that we make
up a scheduel for documentation and have everyone
commit to it.

I reckon I can manage at least 3 hours a week not
much I know, but I am pretty busy right now. If we
can work out a focus and more particularly a
timeline with deadlines then we can get on. I
suggest we start with a CSS reference listing and
explaining what every class, id (including generated
ones like portal tabs) and other selectors do. At
least that way people proficient in CSS can quickly
get down and dirty into the Plone CSS. Next we need
to document what hack we use and standardize them so
people are using the same methods throughout. For
example I don't want people using FIR just because
they know we use image replacement.

More over as Michael said as a long term goal I
would like to sciphen off classes which need bug
fixes, maybe do them right (TM) in plone.css but
then override them in ploneBrowserFix.css or
something. That would make it easy to remove non
nice hacks once the browsers fix stuff.

Anyone else got suggestions for what we could/should
be doing. How long and when.

Oh and well done, I have had more than a few "we
love the new skinning" comments.


Tom



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click