Mailspring/app/internal_packages/composer-templates
Ben Gotow 21bc2ef398
Upgrade to Slate 0.45.1 for better composer perf and "setStart on Range" error fix (#1518)
* Move to Slate 44, start using types more extensively in Composer

* More types and cleanup

* Expose the editor object to the draft session, try exposing editor to session

* Bump to Slate 45 for https://github.com/ianstormtaylor/slate/pull/2225/files

* How did the unsubscribe plugin get in here

* Bump Slate types, fix TS errors, start testing

* Polish

* Fix issue with emails not shrinking when you close quoted text

* Fix the “remove quoted text” button

* More polish

* Fix issues with PR, improve typings

* Remove spurious log
2019-06-10 19:15:07 -05:00
..
assets Fix the example template’s variable regions 2019-01-03 01:17:21 -08:00
lib Upgrade to Slate 0.45.1 for better composer perf and "setStart on Range" error fix (#1518) 2019-06-10 19:15:07 -05:00
styles Upgrade to Slate 0.45.1 for better composer perf and "setStart on Range" error fix (#1518) 2019-06-10 19:15:07 -05:00
icon.png
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

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.