I added this as a child page because the functionality was so well laid out.  The original post is here

Newsletter publishers should be able to :
- manage newsletter entries (as in announcements portlet)
- schedule sending dates (as in announcements portlet)
- manage the mailing list (as in "user group" management, let's suppose a mailing list is a user group in Liferay)
- choose between different html templates dedicated to his community/organization (as in a web template)
- manage an history of newsletters (as in anouncements portlet)

Subscribers should be able to :
- subscribe / unsubscribe (like in "user group" management, "my account" portlet...)
- receive the letter in his own language (impossible for the moment)


I think that a good way to achieve this would be to create a link between the anouncement portlet and the Journal system.

Here's how :
- Liferay admin would prepare a Journal structure called "Newsletter_entry" with subject and body fields and multiple templates linked to it.

- Newsletter writer would write a Newsletter entry with this structure and the template of his choice. He could then localize subject and body fields in any language he wants
- This letter can be approved, tagged, versioned, localized as a classical journal article...

- Newsletter publisher would have an anouncement portlet in his control panel
- He can add/edit an entry like in the current anouncement portlet, excepting that he would have a "journal web content" search container UI that would allow him to select the article made by the newsletter writer (new dev)
- He could then select a scope (like in the current anouncement portlet)
- Preview (like in the current anouncement portlet + new dev)
- Schedule a sending date (like in the current anouncement portlet)
- Then an e-mail containing the article html content would be sent to people in the selected scope (anouncement portlet).
- Plus: each e-mail content would be displayed in a language according to the default language of the user. (new)

So that would be basically like the current anouncement portlet.
Excepting that a link is made to a real journal article and that gives the following benefits :
- multiple languages
- multiple templates
- workflow
- versioning
- tagging
- the ability to display automatically newsletter archives on a web page thanks to the asset publisher portlet
- rich html editor for the body

I would like to know your opinion about that design.
-- Especially Raymond Augé who's the author of the anouncement portlet. --
Would this link to journal be a clever improvement of the anouncement portlet?