Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2024-09-22 00:06:06 +08:00
Code Issues Packages Projects Releases Wiki Activity
Mailspring/internal_packages/composer-templates
History
Evan Morikawa 1498bcfac6 fix(lint): final linter fixes 
fix(lint): final set of linter fixes
2016-05-06 16:32:34 -07:00
..
assets feat(composer): new composer footer and icon design 2016-02-23 13:42:10 -08:00
lib fix(lint): final linter fixes 2016-05-06 16:32:34 -07:00
spec fix(lint): Various linter issues 2016-05-06 16:06:16 -07:00
stylesheets 🎨(preferences): Adjust textbox styles for signatures and templates 2016-04-07 14:12:35 -07:00
icon.png 💄(icon): A delightful seafoam green icon 2016-02-23 10:35:08 -08:00
package.json rename(templates): Use "Quick Replies" name in plugins screen 2016-01-07 15:23:54 -08:00
README.md fix(examples): examples => packages, move away from installing them 2016-01-07 14:56:34 -08:00
screenshot.png fix(examples): examples => packages, move away from installing them 2016-01-07 14:56:34 -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