On Fri, Oct 29, 2010 at 02:33:22PM +0200, Martin Zobel-Helas wrote:
> * The id and class names of the global debian CSS have quite common
> names, which might be accidently overwritten by others.
> Therefore we should think about renaming those to more uniq
> names eg. by prepending something like 'debianci-' ("footermap"
> -> "debianci-footermap").
>
> * Strip down debian.css to only the essential parts, and maybe
> have a debian-common.css, which provides the most common id and
> class names. While we are at this, rewrite them to more
> meaningful names and provide an understandable documentation...
> Will everyone of us know what #outer is going to do?
>
> * Have a technical howto that provides information about the
> (html) structure of a generic page.
> http://kalleswork.net/projects/debian/ has nice pictures, but
> does not provide the HTML code behind that. This howto should
> also document the usage of id tags.
>
> * Provide a set of color codes that mostly match to each other,
> which we recommend to use (note the 'recommend').
>
> * Provide templates and sniplets which are usable for the huge
> number of debian subpages using different engines for rendering
> (ikiwiki, gitweb, moinmoin come in mind). The footermap or the
> toplevel navigation is a good example for that. Rhonda is
> already doing that for most parts, thanks for that help!
Excellent ideas. I started a wikipage intended to deal with many of the
documentation issues you mention.
<http://wiki.debian.org/KredesignManual>
Never had the time to add the actual content though :(
--
Kalle
--
To UNSUBSCRIBE, email to debian-www-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101029140052.ga1...@nokia-n900
