[MGNLMAIL-95] Support using registered templates for email template processing Created: 06/Aug/18  Updated: 16/Mar/21  Resolved: 16/Mar/21

Status: Closed
Project: Magnolia Mail Module
Component/s: Templates
Affects Version/s: 5.5
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Viet Nguyen Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: split
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Documentation update required:
Yes

 Description   

Currently we're using email templates which are configured under '/modules/mail/config/templatesConfiguration' with similar mechanism as our template rendering system.
In this improvement, we'll consider to use registered templates as an email template and consider splitting mail modules into core services, templating and app sub modules.
Mail tools app documentation would also be updated accordingly.


Generated at Mon Feb 12 06:03:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.