Differences between revisions 1 and 28 (spanning 27 versions)
Revision 1 as of 2008-06-18 13:12:38
Size: 1499
Editor: terri
Comment:
Revision 28 as of 2012-03-15 08:51:31
Size: 4151
Editor: toshio@fedoraproject
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/4489287
= Summer of Code/Templating: =
 1. [[..//2006/08/20/Summer of Code summary|Summer of Code summary]] - the project for 2007 concentrated on new ideas for the web UI, and [[../~mindlace|~mindlace]] has an excellent summary here of what was tried
  1. [[../StyledPages|StyledPages]]
  1. [[../TemplatingNotes|TemplatingNotes]]
= Specific suggestions =
== Member/subscriber Interface ==
From [[http://www.mail-archive.com/mailman-users%40python.org/msg49681.html]]:
#pragma page-filename DEV/versions/17891472
= New Web Interface =
Line 10: Line 4:
{{{
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.
}}}
Mailman 3 comes with a new architecture which allows for a separation between the web user interface (WUI) and the mailing list engine. In fact, you can run Mailman 3 with no WUI at all, or integration Mailman 3 with the rest of your web site by accessing the REST admin interface.
Line 14: Line 6:
== List Admin interface ==
= Other Notes =
For standalone systems, we want to develop and ship our own updated WUI. The original Mailman 2 user interface was designed in the late 1990's so it's clearly dated, and the technology backing it is ancient, inflexible and non-standard. Today, there are tons of great Python-based web frameworks, and of course `JavaScript` is all the rage today. We want a modern, good looking, well-organized WUI that can be used with Mailman 3 but is optional for those sites that want to heavily customize their use of Mailman.

Here are some [[../Web UI Mockups|Web UI Mockups]].

Here then are some guidelines, historical notes about previous attempts to update the Mailman WUI can be found [[../Previous work on UI|here]].

To make suggestions the developers should consider when creating and designing the UI, please visit [[../Suggestions for new Mailman 3.0 UI|this page]].

The Mailman WUI will be developed on [[https://edge.launchpad.net/mailmanweb|Launchpad]], and discussions will be conducted on the [[http://mail.python.org/mailman/listinfo/mailman-developers|mailman-developers]] mailing list.

Please add your name to this list if you are interested in helping out!

 * [[../../~barry/Home|Barry Warsaw]]
 * Patrick Ben Koetter
 * [[terri|Terri Oda]]
 * [[anna.granudd@gmail.com|Anna Granudd]]
 * [[f@state-of-mind.de|Florian Fuchs]]
 * Claudia Fleiner
 * [[benste|benste]]
 * Toshio Kuratomi

== Guidelines ==

 1. Modern, easy to use web user interface for users, list admins, and site admins.
 1. Progressive enhancement; i.e. can use `JavaScript` for dynamic aspects, but must remain usable for non-`JavaScript` browsers, and must be friendly to screen readers.
 1. WUI templates must support internationalization by allowing us to mark up translatable texts for inclusion in the `gettext` catalog. Technology must integrate with Python's `gettext` module and/or Mailman's i18n infrastructure.
 1. WUI template system must be Python-based (framework TBD) and GPLv3 compatible.
 1. `JavaScript` library must be GPLv3 compatible (framework TBD).

== Templating systems ==

Exactly which templating system we'll choose is '''Django'''. A couple of thoughts though:

 * It would be nice to use the same templating system in the WUI and core engine. I'd like to be able to use templates for all email that Mailman sends
 * It should be friendly to [[../Internationalization|Internationalization]]. Meaning it should be possible to extract texts from templates and add them to a [[http://www.python.org/doc/current/library/gettext.html|gettext]] catalog.
 * Of course, written in Python

== Status ==

Status updates on the development can be found and discussed [[../Web Interface Status|here]].

== Wish List / Random Ideas ==

 * "moderate_all" option for admins: "Consider an admin that is reviewing a bunch of bounces/spam, etc. It might be handy for him to have some buttons to freeze the list (eg. moderate-all) in that context without having to navigate over to a different section to set that flag." (wacky via irc)
 * showing the Log in the WUI (C Nulk via Mailinglist)
 * allowing a user 'to be on vacation' (wacky via IRC)

New Web Interface

Mailman 3 comes with a new architecture which allows for a separation between the web user interface (WUI) and the mailing list engine. In fact, you can run Mailman 3 with no WUI at all, or integration Mailman 3 with the rest of your web site by accessing the REST admin interface.

For standalone systems, we want to develop and ship our own updated WUI. The original Mailman 2 user interface was designed in the late 1990's so it's clearly dated, and the technology backing it is ancient, inflexible and non-standard. Today, there are tons of great Python-based web frameworks, and of course JavaScript is all the rage today. We want a modern, good looking, well-organized WUI that can be used with Mailman 3 but is optional for those sites that want to heavily customize their use of Mailman.

Here are some Web UI Mockups.

Here then are some guidelines, historical notes about previous attempts to update the Mailman WUI can be found here.

To make suggestions the developers should consider when creating and designing the UI, please visit this page.

The Mailman WUI will be developed on Launchpad, and discussions will be conducted on the mailman-developers mailing list.

Please add your name to this list if you are interested in helping out!

Guidelines

  1. Modern, easy to use web user interface for users, list admins, and site admins.
  2. Progressive enhancement; i.e. can use JavaScript for dynamic aspects, but must remain usable for non-JavaScript browsers, and must be friendly to screen readers.

  3. WUI templates must support internationalization by allowing us to mark up translatable texts for inclusion in the gettext catalog. Technology must integrate with Python's gettext module and/or Mailman's i18n infrastructure.

  4. WUI template system must be Python-based (framework TBD) and GPLv3 compatible.
  5. JavaScript library must be GPLv3 compatible (framework TBD).

Templating systems

Exactly which templating system we'll choose is Django. A couple of thoughts though:

  • It would be nice to use the same templating system in the WUI and core engine. I'd like to be able to use templates for all email that Mailman sends
  • It should be friendly to Internationalization. Meaning it should be possible to extract texts from templates and add them to a gettext catalog.

  • Of course, written in Python

Status

Status updates on the development can be found and discussed here.

Wish List / Random Ideas

  • "moderate_all" option for admins: "Consider an admin that is reviewing a bunch of bounces/spam, etc. It might be handy for him to have some buttons to freeze the list (eg. moderate-all) in that context without having to navigate over to a different section to set that flag." (wacky via irc)
  • showing the Log in the WUI (C Nulk via Mailinglist)
  • allowing a user 'to be on vacation' (wacky via IRC)


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