Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2024-11-11 18:32:20 +08:00
Code Issues Projects Releases Packages Wiki Activity
Mailspring/internal_packages/composer-templates
History
Ben Gotow 298eb06548 💄: White buttons, dropdown / popover cleanup, hairline dividers
2016-02-18 15:21:42 -08:00
..
assets fix(templates): rewritten "welcome" file / example template 2016-01-13 12:08:41 -08:00
lib fix(lint): Fix new eslint rule introduced with babel-eslint upgrade. 2016-02-01 20:07:36 -08:00
spec fix(specs): Minor change to templates package for Travis 2016-01-08 10:52:37 -08:00
stylesheets 💄: White buttons, dropdown / popover cleanup, hairline dividers 2016-02-18 15:21:42 -08:00
icon.png feat(metadata): add cloudState that sync with Metadata service 2016-02-02 15:28:06 -05:00
package.json
README.md
screenshot.png

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