Differences between revisions 13 and 15 (spanning 2 versions)
Revision 13 as of 2007-05-07 12:36:10
Size: 3640
Editor: munitoris
Comment:
Revision 15 as of 2007-07-03 11:12:25
Size: 3840
Editor: amk@amk
Comment: Migrated to Confluence 4.0
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#pragma page-filename DEV/versions/786588
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.
#pragma page-filename DEV/versions/163933
As a first step before [[../TemplatingNotes|adding full templating]], the existing pages<<BR>> 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]].
Line 6: Line 8:
Line 9: Line 12:
Line 11: Line 15:
&nbsp;&nbsp;&nbsp; Logical scopes and a proposed representation of those scopes within the style sheet cascade: Logical scopes and a proposed representation of those scopes within the style sheet cascade:
Line 13: Line 17:
 * 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?
 * 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          
Line 21: Line 24:
&nbsp;&nbsp;&nbsp; Possibilities: OPEN: where does the default stylesheet live? Is there a suitable static directory created by installing mailman?
Line 23: Line 26:
 * ./mailman/archives/public/ is accessible by HTTP whether by design or oversight
  * What other issues might stem from this?
Possibilities:

* ./mailman/archives/public/ is accessible by HTTP whether by design or oversight  
  * What other issues might stem from this?   
Line 27: Line 33:
&nbsp;&nbsp;&nbsp; This is 'considered harmful' as style="" overrides everything. We should never need to do this.&nbsp; This is 'considered harmful' as style="" overrides everything. We should never need to do this. 
Line 30: Line 36:
Line 32: Line 39:
Line 33: Line 41:
Line 35: Line 44:
 * [[http://databaseadvisors.com/mailman/listinfo]]  * [[http://databaseadvisors.com/mailman/listinfo|http://databaseadvisors.com/mailman/listinfo]]
Line 37: Line 46:
Line 38: Line 48:
Line 41: Line 52:
Line 42: Line 54:
Line 50: Line 63:
Line 51: Line 65:
Line 52: Line 67:
Line 53: Line 69:
Line 54: Line 71:
Line 55: Line 73:
Line 56: Line 75:
Line 57: Line 77:
Line 58: Line 79:
Line 59: Line 81:
Line 60: Line 83:
Line 61: Line 85:
Line 62: Line 87:
Line 63: Line 89:
Line 65: Line 92:
Line 66: Line 94:
Line 70: Line 99:
Line 71: Line 101:
Line 74: Line 105:
Line 75: Line 107:
Line 76: Line 109:
Line 77: Line 111:
Line 78: Line 113:

As a first step before adding full templating, the existing pages
can be restyled to use CSS and to look more up-to-date.

Currently being developed in the 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 <head>, <body> etc. are defined in one pair of header and footer files, so they can be turned off easily;

  • the CSS files "namespace" everything by placing all Mailman content within a div, e.g. <div id="mailman">...</div> and then prefix all CSS rules with "#mailman" - this stops the Mailman styles from leaking out into the parent page elements.

Ideas

Does anyone know of heavily customized MM archives that we could look at for ideas?

Places to change

  • The HTML templates in templates/.
  • MailMan.HTMLFormatter

  • The CGI scripts in MailMan/Cgi (they use htmlformat.Table all over the place).

Templates

Particular changes to each template are recorded below.

For all templates:

  • Lowercase all HTML tags.
  • Wrap entire <body> inside <div id="mailman">...</div>.

  • Update the DOCTYPE declaration (to HTML 4.0?)
  • Check validity of generated pages

admindbdetails.html

admindbpreamble.html

admindbsummary.html

admlogin.html

archidxentry.html

archidxfoot.html

archidxhead.html

archlistend.html

archliststart.html

archtocentry.html

archtoc.html

  • Wrap archive listing with a <div>

archtocnombox.html

  • Wrap archive listing with a <div>

  • OPEN: Merge this with archtoc by using a 'display:ignore' around the link to the raw archive?

article.html

  • Add class=subject, author, date
  • Wrap body with a <div class="message">

  • Wrap "More information" with a <div class="?">.

  • OPEN: wrap the links to the various indexes with a special class?

emptyarchive.html

No specific changes.

headfoot.html

listinfo.html

options.html

private.html

roster.html

subscribe.html

MailmanWiki: DEV/StyledPages (last edited 2015-03-04 05:29:55 by msapiro)