Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2024-09-21 07:46:06 +08:00
Code Issues Packages Projects Releases Wiki Activity
Mailspring/app/internal_packages/composer-templates
History
Ben Gotow ccac20b250 Make the “Show Templates Folder” link smaller, improve Subscription tab styling
2019-03-12 21:27:01 -07:00
..
assets Fix the example template’s variable regions 2019-01-03 01:17:21 -08:00
lib Make the “Show Templates Folder” link smaller, improve Subscription tab styling 2019-03-12 21:27:01 -07:00
styles Improve composer performance by avoiding expensive draft.body call in render 2018-01-25 22:38:40 -08:00
icon.png Clean up project directory structure, removing legacy packages folder 2017-08-10 19:24:10 -07:00
package.json Switch product name to “Mailspring” 2017-09-05 13:40:25 -07:00
README.md Switch product name to “Mailspring” 2017-09-05 13:40:25 -07:00
screenshot.png Clean up project directory structure, removing legacy packages folder 2017-08-10 19:24:10 -07:00

README.md

Composer Templates

Create templates you can use to pre-fill the N1 composer - never type the same email again! Templates live in the templates folder inside the Mailspring config folder.

Each template is an HTML file - the name of the file is the name of the template, and it's contents are the default message body.

If you include HTML <code> tags in your template, you can create regions that you can jump between and fill easily. Give <code> tags the var class to mark them as template regions. Add the empty class to make them dark yellow. When you send your message, <code> tags are always stripped so the recipient never sees any highlighting.

This example is a good starting point for plugins that want to extend the composer experience.