Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 8. Email Templates
By the end of this section, you will have edited and saved a custom email template.
You can completely customize the content of all standard email communication with developers, allowing you to closely match the workflows you have set up for your Developer Portal.
8.1. Customizing email templates
8.1.1. Define your workflows before email configuration
There are a lot of email template options, only a subset of which will be relevant for your workflows. Save yourself time by making sure you’re happy with your workflows before beginning to edit the email templates. This way, you’ll only edit the templates that you’ll actually use.
8.1.2. Test your workflow and identify active email templates
Perform a dry run of your finalized workflows, making sure to test all the possible branches, such as approval and rejection. Then, identify each email notification that your test developer account receives to determine what to edit in the next step.
8.1.3. Edit and save your custom template
The first time you edit a template, you will actually create a custom template. Then in subsequent edits, you will save your changes.
There is no version control. Red Hat recommends you make a local copy if you want to be able to revert changes.
You can use liquid tags for dynamic content in your email. We especially recommend you make backups when you make changes to the liquid tags.
8.1.4. Repeat for all templates in your workflows
Complete these same steps until you’ve covered all possible branches for your workflows.
8.2. More information
- Before customizing your email templates, it is best to have the signup flows fully finalized and tested.
- If you intend to change any of the liquid tags within the email templates, be sure to read up on the liquid reference documentation.
