Mailspring/app/internal_packages/composer-templates
2017-11-07 20:44:13 +01:00
..
assets Removed "Nylas Team" from quick replies preferences 2017-10-24 14:49:27 -07:00
lib Fix linter errors, replace old references to N1 2017-10-08 11:18:29 -07:00
specs Rename nylas-component-kit, nylas-exports, nylas-store, nylas-observables 2017-09-26 11:42:18 -07:00
styles Improve preferences messaging, display on small screens 2017-11-07 20:44:13 +01: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.