Hi,
as you might have noticed, I am working on integrating KalleDesign
into debian.org sites for some time now, and trying to convince
others to do so as well. I think/hope we will reach the 'break-even'
where the website team does not need to do all the work quite soon.
Also I would like to share some concerns and ideas a friend of me
brought up and which might help others to convert their sub-page to
KallesDesign.
* 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!
Cheers,
Martin
--
Martin Zobel-Helas <zobel@debian.org> | Debian System Administrator
Debian & GNU/Linux Developer | Debian Listmaster
Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870
GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870
Attachment:
signature.asc
Description: Digital signature