To-do
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
"message" could be split in "message text" and "message html" (the latter with template) | "message" could be split in "message text" and "message html" (the latter with template) | ||
| − | * Create a form "Newsletter stats", with fields (first name, last name, email, opens (list of dates), clicks (list of dates and url) -- data of this form will be created by a nodejs script through sendgrid (or other mail provider) hooks | + | * Create a form "Newsletter stats", with fields (first name, last name, email, opens (list of dates), clicks (list of dates and url) -- data of this form will be created by a nodejs script through sendgrid (or other mail provider) hooks *** try to create automatically it, see point below *** |
| − | * ***attention: in a further version of the system all these forms/properties/templates could be automatically created, even localized in a given language, by a server side script, in order to easily allow creation of (public/) private wiki instances | + | * ***attention: in a further version of the system all these forms/properties/templates could be automatically created, even localized in a given language, by a server side script, in order to easily allow creation, and update, of (public/) private wiki instances |
| Line 32: | Line 32: | ||
we could create a form as well (to let the nodejs server side script retrieve them) with fields: | we could create a form as well (to let the nodejs server side script retrieve them) with fields: | ||
name, authors, description, snapshot/preview (so that templates can be listed on the frontend site) the cointainer div of the form must use an identifier known by the nodejs script to parse it | name, authors, description, snapshot/preview (so that templates can be listed on the frontend site) the cointainer div of the form must use an identifier known by the nodejs script to parse it | ||
| + | |||
| + | * debug the files subfolder related functions | ||
==Frontend site== | ==Frontend site== | ||
| + | |||
| + | * create a page (with signin) to select a template, a segment/subset of recipients, enter a text message in a textarea and edit a template with ckeditor, then sending the message: all this information will be recorded in the form above "newsletters" in the private wiki | ||
* | * | ||
Revision as of 23:22, 3 April 2020
Private wiki
- Create form "Meeting participant"
(First name, Last name, email, phone number, status (attended/invited), description (textarea) (eventually: "linked_to", with a multiple select with names of all other participants to the same meeting ... or use another hypothetical form for this)
- Create sidebar entries with forms: Add Language course student, Add member, Add meeting participant
- Reorder our private wiki in order to just have (on the root level) :
- List of language course students
- List of members
- List of meeting participants
and create a main page reflecting this structure with cars similar to the public mainpage
- Create a form "Newsletter", with fields: Date, audience subset/segment, message (this will be filled in by the frontend/nodejs script, but the sending could be also managed in the wiki itself)
"message" could be split in "message text" and "message html" (the latter with template)
- Create a form "Newsletter stats", with fields (first name, last name, email, opens (list of dates), clicks (list of dates and url) -- data of this form will be created by a nodejs script through sendgrid (or other mail provider) hooks *** try to create automatically it, see point below ***
- ***attention: in a further version of the system all these forms/properties/templates could be automatically created, even localized in a given language, by a server side script, in order to easily allow creation, and update, of (public/) private wiki instances
Public wiki
- Create a page, for instance /Sidebar Left, where to list forms and templates to be displayed handled from our extension (ci_culturaitaliana_addons)
- Create a series of email templates in the path /Email templates/[template title]
we could create a form as well (to let the nodejs server side script retrieve them) with fields: name, authors, description, snapshot/preview (so that templates can be listed on the frontend site) the cointainer div of the form must use an identifier known by the nodejs script to parse it
- debug the files subfolder related functions
Frontend site
- create a page (with signin) to select a template, a segment/subset of recipients, enter a text message in a textarea and edit a template with ckeditor, then sending the message: all this information will be recorded in the form above "newsletters" in the private wiki