Currently we replace core WordPress email templates with better looking email templates created by Inbound Now. The data that defines these template replacements are defined in /shared/templates/ (https://github.com/inboundnow/cta/tree/master/shared/templates/email-templates) and imported directly into the WordPress database into the 'email-template' custom post type.
We then allow these templates to be editable so users can customize how their email templates look.
These are the current email templates and the processes they are related to:
New comment moderation - Sends to the administrator when a new comment is posted and awaiting moderation.
New comment notification - Notifies administrators that a new comment has been published.
New lead notification - Notifies administrators when an inbound now form is filled out.
New user signup notification - Contacts user after signup with username and password information.
Challenges
Email templates should not be editable
I believe we will want to get rid of the email-template custom post type all together. Landing Page templates and Call to Action templates to not have their own custom post type. Their templates provide a structure for defining inputs and those inputs help control the layouts in the landing-page and wp-call-to-action post type. We should take the same approach with email templates and the 'inbound-email' custom post type.
We should allow users to set which email templates their core processes use:
Because these emails are related to automated processes we can't really call them an email campaign. They are more of an autoresponder.
So the question becomes how should we differentiate automated email campaigns from manual email campaigns? I believe automated email campaigns and manual email campaigns can live under the same post type differentiated by categories. But there are other options too:
Create a custom post type for autoresponders and pre-build the autoresponder campaigns that will handle core email processes and not let users delete them.
Have autoresponders listed in the inbound-email custom post type, but categorize them into 'autoresponders' instead of 'campaigns'.
Either way we would want to allow users to change which template to use for an autoreponder process as well as edit the content within those templates.
atwellpub
commented
9 years ago
Currently we replace core WordPress email templates with better looking email templates created by Inbound Now. The data that defines these template replacements are defined in /shared/templates/ (https://github.com/inboundnow/cta/tree/master/shared/templates/email-templates) and imported directly into the WordPress database into the 'email-template' custom post type.
We then allow these templates to be editable so users can customize how their email templates look.
These are the current email templates and the processes they are related to:
Challenges
Email templates should not be editable
I believe we will want to get rid of the email-template custom post type all together. Landing Page templates and Call to Action templates to not have their own custom post type. Their templates provide a structure for defining inputs and those inputs help control the layouts in the landing-page and wp-call-to-action post type. We should take the same approach with email templates and the 'inbound-email' custom post type.
We should allow users to set which email templates their core processes use:
Because these emails are related to automated processes we can't really call them an email campaign. They are more of an autoresponder.
So the question becomes how should we differentiate automated email campaigns from manual email campaigns? I believe automated email campaigns and manual email campaigns can live under the same post type differentiated by categories. But there are other options too:
Either way we would want to allow users to change which template to use for an autoreponder process as well as edit the content within those templates.