Hi,
The following directory structure will be used to keep the template based
>> on the locale.
>>
>> config/
>> └── email/
>> ├── en_US
>> │ └── email-admin-config.yaml
>> └── en_GB
>> └── email-admin-config.yaml
>>
>>
> Currently the structure we have is,
>
> config/
> └── email/
> ├── scenario1 (like AccountRecovery)
>
> └── en_US (here we have the actual template)
>
> └── en_GB
>
>
As we discussed offline, I suggest that we group email templates based on
locale and having a template per scenario.
config/
└── email/
├── en_US (locale)
| └── password-recovery.yaml (here we have the actual
template in en_US) (template per scenario)
| └── email-confirmation.yaml (here we have the actual
template in en_US)
| └── ...
├── fr
└── password-recovery.yaml (here we have the actual template in fr)
└── email-confirmation.yaml (here we have the actual template in fr)
└── ...
If we put all the email templates in one template file, then it becomes
hard to maintain as this file may grow as new email templates are
introduces. Also the content of a particular template (ex: html templates)
will also become hard to maintain in one file. With above suggested
separation, CRUD operations for a particular template of a locale become
simple, as those will be file based configurations going forward.
--
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
20, Palmgrove Avenue, Colombo 3
E-Mail: [email protected] <[email protected]>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
