Bugzilla CSS plan

Fri Jul 23 20:15:06 UTC 2004

Myk Melez wrote:
> We move the Bugzilla CSS files, which currently live in css/, to 
> skins/default/.  We style all Bugzilla pages with 
> skins/default/global.css, and we style pages needing special styling 
> with page-specific files named after the page they style (f.e. 
> skins/default/buglist.css).

Why not mirror (fairly closely) the template structure? So 
skins/default/reports/foo-page.css and 
skins/default/search/bar-page.css? This gives a level of familiarity, 
and allows us to separate things a bit more.

> checksetup.pl creates a skins/custom/ directory.  We add notes to the 
> skins/default/ files telling customizers to override default rules by 
> putting them into the equivalent files in skins/custom/.  

Would it make more sense just to have a "skins/<skinname>" directory, 
and have a Param giving the current skin name?

People also sometimes ask if they can present different skins according 
to different rules; this sort of organisation would make that easier, 
even if the ability to do it never makes it into Bugzilla.

> easier.  We give all body tags page-specific IDs to make this possible.  

Presumably a combination of site name and page name? Or can we put the 
site name on the <html> tag and the page name on the <body>? That might 
be better - keep the two separate. Or we could (hackily) surround every 
page with one big <div>.

> checksetup.pl creates a skins/other/ directory.  We tell installation 
> admins who want to add skins as alternate stylesheets to put them into 
> this directory.  

Could this mechanism be combined with the multiple skins thing above? 
For example, the Param could instead give a list of permitted 
alternative skins, with the first one being the default.

Having read the rest of your post, you may already have suggested some 
of this stuff.

Gerv