Topic on Extension talk:Newsletter/Archive 1

Just an attempt to draft some specs:

For newsletter authors

• Creating a newsletter.
• Drafting and publishing a new edition of the newsletter.
• Send a notification to subscribers when a new edition is ready.
• Check who / how many people is subscribed to the news letter.

For newsletter readers

• A page with newsletters available, with a possibility to subscribe / unsubscribe.
• Possibility to receive the notification of a new edition via email / talk page / Echo.
• Web notifications contain link to the source page.
• Email notifications contain link and full text (optional? plain text and HTML?)

This post was posted by Qgil-WMF, but signed as Qgil.

Would it be a good idea to write the additions as stories?

The only currently implanted narrative is "As a user I can subscribe to newsletters, so that I can indicate i want to receive newsletters." This was implemented as a preference in the email presences section, and the preference will only be visible if a user has a confirmed email address.

I tried to write something in between at Extension:Newsletter. I'm not a big fan of stories in first person but if you or someone wants o take over I won't object to anything as long as the work gets done.  :)

This post was posted by Qgil-WMF, but signed as Qgil.

The anonymous editor makes a good suggestion.

Otherwise, thanks Quim. These stories look good to me.

See phab:M12 for this mockup on phabricator.

A mockup

A mockup of how I understand the "Newsletter reader" part to work.

This is tremendously helpful in understanding what's envisioned. Thanks Quiddity! I had previously thought the intent was to provide a richer set of tools for composing and formatting a newsletter, but now I understand -- this is simply focused on simplifying the subscription process, and adding Echo and email subscription options. Thanks, and sorry I didn't spot this the first time around :) -Pete Forsyth (talk) 05:43, 4 January 2017 (UTC)

We are expecting to post a better description and screenshots to the Extension page (as part of a Google Code-in task proposed). If not, I'll find the time to do it in my volunteering time.  :)