Improve design of mailman subscription pages #412

New Issue

max.mehl · 2018-07-18T14:48:28Z

max.mehl commented

2018-07-18 14:48:28 +00:00

With the latest Mailman version we're using, all forms to enter one's email to sign up to newsletters or press release lists are not working anymore (like here and there. There's now a CSRF protection which would require us to include active code on the website, something we don't want.

The easiest approach is to link directly to the newsletter signup page. But this currently looks simply ugly and confusing. Therefore, a design update is needed to make it prettier and easier to use.

Mailman supports custom templates. There are already some we could reuse and adapt. We also have a few templates already adapted to the FSFE's corporate design, I attached one of them. They could serve as a good starting point.

With the latest Mailman version we're using, all forms to enter one's email to sign up to newsletters or press release lists are not working anymore (like [here](https://fsfe.org/news/newsletter.html) and [there](https://fsfe.org/press/press.html). There's now a CSRF protection which would require us to include active code on the website, something we don't want. The easiest approach is to link directly to the [newsletter signup page](https://lists.fsfe.org/mailman/listinfo/newsletter-en). But this currently looks simply ugly and confusing. Therefore, a design update is needed to make it prettier and easier to use. Mailman supports custom templates. There are already [some we could reuse and adapt](https://github.com/quimgil/mailman-templates). We also have a few templates already adapted to the FSFE's corporate design, I attached one of them. They could serve as a good starting point.

newsletter-en_subscribe.html

2.7 KiB

max.mehl added the

help wanted

design

labels 2018-07-18 14:48:28 +00:00

max.mehl referenced this issue from a commit

2018-07-23 15:11:54 +00:00

make newsletter form direct to listinfo site to fix subscribe error this is related to #412 which deals with the new CSRF protection of mailman. we urgently need a better design here to make it more appealing

max.mehl commented

2018-07-23 15:24:55 +00:00

With 75fcf34e12 the form directs to the listinfo page in the chosen language instead, and therefore the mail address field isn't necessary.

Since the current design is aweful, we should focus on making this better.

With 75fcf34e12 the form directs to the listinfo page in the chosen language instead, and therefore the mail address field isn't necessary. Since the current design is aweful, we should focus on making this better.

max.mehl commented

2018-07-24 15:37:36 +00:00

First try here. Had to hack a bit with mailman (blacklist of HTML tags) and the fsfe.org webserver (CORS).

https://lists.fsfe.org/mailman/listinfo/radiodirective

This is for the individual list only at the moment.

First try here. Had to hack a bit with mailman (blacklist of HTML tags) and the fsfe.org webserver (CORS). https://lists.fsfe.org/mailman/listinfo/radiodirective This is for the individual list only at the moment.

max.mehl commented

2018-07-25 15:56:02 +00:00

Now the default for all mailing lists, and also translated to German.

I've also edited the default subscribe.html, and adapted the design to the custom newsletter-* layouts.

I wonder whether it would make sense to put all templates to Git to make translations and maintenance easier.

Now the default for all mailing lists, and also translated to German. I've also edited the default subscribe.html, and adapted the design to the custom newsletter-* layouts. I wonder whether it would make sense to put all templates to Git to make translations and maintenance easier.

max.mehl commented

2018-07-26 15:54:34 +00:00

Work on mailman pages can now take place in a new repository: https://git.fsfe.org/fsfe-system-hackers/mailman-templates/

Everything with negative influence on fsfe.org should have been fixed, so I'll close here

Work on mailman pages can now take place in a new repository: https://git.fsfe.org/fsfe-system-hackers/mailman-templates/ Everything with negative influence on fsfe.org should have been fixed, so I'll close here

max.mehl closed this issue

2018-07-26 15:54:34 +00:00

Sign in to join this conversation.

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: FSFE/fsfe-website#412