|
Size: 4185
Comment: moved suggestions to a separate page
|
Size: 3829
Comment: Removed section previous work and put it on a separate page as suggested by Barry. Can be found in the child pages.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #pragma page-filename DEV/versions/10715402 | #pragma page-filename DEV/versions/10715404 |
| Line 18: | Line 18: |
| * [[../~anna.granudd@gmail.com|Anna Granudd]] | |
| Line 44: | Line 45: |
| = Previous work = (This should probably be moved off onto a separate page - BAW) == 2006 Summer of Code == 1. [[..//2006/08/20/Summer of Code summary|Summer of Code summary]] - the project for 2006 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]] == Suggestions for new UI == |
== Suggestions for the new UI == |
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, along with historical notes about previous attempts to update the Mailman WUI.
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!
- Patrick Ben Koetter
Guidelines
- Modern, easy to use web user interface for users, list admins, and site admins.
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.
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.
- WUI template system must be Python-based (framework TBD) and GPLv3 compatible.
JavaScript library must be GPLv3 compatible (framework TBD).
Templating systems
Exactly which templating system we'll choose is TBD. 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 DEV/Internationalization. Meaning it should be possible to extract texts from templates and add them to a gettext catalog.
Of course, written in Python
Here's a table of templating system candidates:
| Framework | Pros | Cons |
| Cheetah |
Status
Status updates on the development can be found and discussed here.
Suggestions for the new UI
To add suggestions what the UI designers should consider when working with the UI, please see this page: DEV/Suggestions for new Mailman 3.0 UI. Parts of the Mailman 3.0 UI page have also been moved there.