Mailspring/app/internal_packages/composer-templates
2017-09-25 16:56:47 -07:00
..
assets Clean up project directory structure, removing legacy packages folder 2017-08-10 19:24:10 -07:00
lib Fix broken specs 2017-09-25 16:56:47 -07:00
specs Fix specs, move super broken specs out of the way for now 2017-08-26 00:25:49 -04:00
styles Clean up project directory structure, removing legacy packages folder 2017-08-10 19:24:10 -07: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

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.