All elements are located in folders named “newsletter” and the reference names are prefixed with “newsletter_” in order to minimize the chance of overwriting existing elements. The most significant elements are: Page templates newsletter_settings: Template for GCA newsletter_settings newsletter_profile: Template for GCA newsletter_profile newsletter: Template for the newsletter itself (using content projection). It includes both the HTML output as well as the XML output for the so called event file. The latter includes the HTML output inline and will be hidden in preview generation. newsletter_form_dummy_page: Empty page as an example to display the newsletter subscription form
Section templates Elements in the folder newsletter_content_sections: Available content sections for the newsletter newsletter_form: Content section to include a form from the Universal Messenger. Add this section template to an appropriate body in your existing page templates
Database schemata: Workflows
Pages/StructureGlobal contentsAll settings specific to the project are managed with two GCA pages: newsletter_settings: General settings for the newsletter integration, this GCA is mandatory for every project using the module EmailMarketing newsletter_profile: Layout settings, footer contents and texts for the specific newsletter.
This implementation uses a data source “newsletter” to manage newsletters as single database entries. You can edit the contents for a specific newsletter here. The feature also includes elements for the project settings managed with the ServerManager. The newsletter layout will use two resolutions provided by the feature: The schedule entries will generate all files needed for the newsletter and send them to the Universal Messenger via REST. Newsletter: Testversand: The schedule entry to send the newsletter to the configured test channel. It will be started by the workflow “newsletter_send_test”. Newsletter: Versand: The schedule entry to send the newsletter to the final recipient groups. It will be started by the workflow “newsletter_send”.
|