Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2008-06-18 13:34:21 →
Size: 2034
Editor: terri
Comment:
← Revision 4 as of 2008-06-19 12:22:53 → ⇥
Size: 2629
Editor: terri
Comment: adding my own idea
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#pragma page-filename DEV/versions/4489291 #pragma page-filename DEV/versions/4489292
Line 31: Line 31:
From [[http://www.mail-archive.com/mailman-users%40python.org/msg49700.html]] (this is [[../~terri|~terri]])

My solution would be to have an "expert" and a "simple" interface. Three reasons:

 1. Even '''as''' an expert, I'd love to have a small interface that met my most common needs.
 1. Choosing what options to keep and which to toss would likely slow down the process so much that we'd never get a new interface.
 1. Giving people access to files is more of a pain than letting them interact through a web UI. (eg - don't have to worry about shell access, bad file syntax, etc.)

Summer of Code/Templating:

  1. Summer of Code summary - the project for 2006 concentrated on new ideas for the web UI, and ~mindlace has an excellent summary here of what was tried

    1. StyledPages

    2. TemplatingNotes

Specific suggestions

Member/subscriber Interface

From http://www.mail-archive.com/mailman-users%40python.org/msg49681.html: 

It is not obvious from the list information page how one would obtain a password reminder. 
You have to click the "Unsubscribe or edit options" button to get to the page with the 
password reminder button. This really needs to be FAR more obvious. It really should be 
an item on the very first page a user sees.

List Admin interface

From http://www.mail-archive.com/mailman-users%40python.org/msg49698.html 

I think the admin UI suffers from:

  1. Too many options.
  2. Weak categorization.
  3. Typographically bad, e.g. no visual cues about significance, related options, etc. 
     and right-aligned labels make it difficult to skim down through a page.
  4. Labels are too verbose, contributing with noise to the overall view, and the "Details 
     for «the_mailman_option_name»" under each label does not help in this regard.

From http://www.mail-archive.com/mailman-users%40python.org/msg49700.html (this is ~terri)

My solution would be to have an "expert" and a "simple" interface. Three reasons:

  1. Even as an expert, I'd love to have a small interface that met my most common needs.

  2. Choosing what options to keep and which to toss would likely slow down the process so much that we'd never get a new interface.
  3. Giving people access to files is more of a pain than letting them interact through a web UI. (eg - don't have to worry about shell access, bad file syntax, etc.)

Other Notes

MailmanWiki: DEV/Postorius Web Interface (last edited 2016-03-02 17:35:48 by SimonHanna)