#pragma page-filename DEV/versions/163933
As a first step before [[../TemplatingNotes|adding full templating]], the existing pages<
> can be restyled to use CSS and to look more up-to-date.
Currently being developed in the
[[https://code.launchpad.net/~amk/mailman/html-cleanup|html-cleanup bzr branch]].
== Goals ==
* Avoid using tables for layout.
* Make pages look more modern.
* Add a stylesheet URL setting, and use it when generating HTML output.
OPEN: is the stylesheet URL a list-specific or site-wide setting?
Logical scopes and a proposed representation of those scopes within the style sheet cascade:
* server level - defaults.css , not represented in the XHTML at all.
* site level - mailman.css, the "global" stylesheet linked into every page. it uses an @include statement to incorporate defaults.css.
* domain level - example.com.css added if present as a linked stylesheet into every page of that domain.
* list level - listname.css if present.
* page level - included within style elements.
* tag/code level - use setting class="$values" for most style manipulations. Ideally no style="$style" use though browser bugs may require it
OPEN: where does the default stylesheet live? Is there a suitable static directory created by installing mailman?
Possibilities:
* ./mailman/archives/public/ is accessible by HTTP whether by design or oversight
* What other issues might stem from this?
OPEN: Allow embedding style directives in the output HTML?
This is 'considered harmful' as style="" overrides everything. We should never need to do this.
== CSS requirements ==
* the bits of the template which define