Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2024-11-12 12:40:08 +08:00
Code Issues Projects Releases Packages Wiki Activity
Mailspring/examples/N1-Composer-Templates
History
Juan Tejada ef7266d362 update(examples): Update examples to use new ExtensionRegistry api 
- Remove deprecated use of DraftStoreExtension and DraftStore.register
2015-12-05 01:07:38 -08:00
..
assets
lib update(examples): Update examples to use new ExtensionRegistry api 2015-12-05 01:07:38 -08:00
spec Convert Composer Template example to ES6 2015-11-14 22:12:06 -08:00
stylesheets feat(templates-plugin): Add prefs page with template editor, fix bugs. 2015-12-02 21:28:49 -08:00
icon.png fix(sync): Request all labels / folders to avoid paging and missing inbox 2015-10-03 23:53:59 -07:00
package.json fix(license): Mark a few additional packages as GPLv3 2015-11-25 14:41:10 -08:00
README.md fix(examples): small fixes in READMEs 2015-12-01 15:59:00 -08:00
screenshot.png Convert Composer Template example to ES6 2015-11-14 22:12:06 -08: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 ~/.nylas/templates directory on your computer. 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.

Install this plugin

  1. Download and run N1

  2. From the menu, select Developer > Install a Plugin Manually... The dialog will default to this examples directory. Just choose the package to install it!

    When you install packages, they're moved to ~/.nylas/packages, and N1 runs apm install on the command line to fetch dependencies listed in the package's package.json