nodeletter is a Node.js module that can be used for creating email newsletters.
It was developed and has been tested on Node.js vr. 0.8.18.
nodeletter requires the following modules:
This Node module is intended for developers/designers tasked with creating a unique newsletter design for email. Normally services like MailChimp, etc., are good routes to go for such efforts. But, if you're stuck creating a solution from scratch to handle through some distribution service, that usually means you're in for a lot of trivial work, including:
- using antiquated HTML/CSS strategies to lay out content (grr)
- testing with numerous email browsers (yuck)
- embedding CSS inline as
styleattributes for MUA's that don't process header or inline CSS (wut)
- making sure all links are referencing valid external location (mmph)
- having multiple copies of the same design for email/online display (hnngghh)
- entering content into source directly (&@#$D!)
- updating context sensitive variables (dates, names, etc.) (sigh)
- remembering to create a text version (aw, crap)
nodeletter attempts to solve at least some of these problems from the get go, or at least make your life easier. A more over-arching goal is to make newsletter development more akin to common web development.
nodeletter separates newsletter creation into concerns you're used to when developing for the front-end interwebz.
Render modes refer to sets of behavior by which *nodeletter will render an existing email template. By default, the following render modes are supplied (and are overrideable):
- email: CSS is inlined, compiled into the DOM as
styleattributes, and compressed, link references are made external
- online: CSS is inlined, references are made external
- default: the template is served with no intermediate processing
nodeletter newsletters are created using the Kiwi templating engine, which is itself based on jQuery Templates.
Content refers to what is featured in your newsletter, which is usually text like an article, or whatever.
Content is derived using
markdown. Simply create a markdown file and include
it in your template within the
Feeds are lists of items that a newsletter might use, like a list of news items, events, or links.
Feeds are derived using
JSON files that are imported from
Static files are your CSS, JS, and images. These are smartly handled depending on your defined render modes.
Obviously you want to be able to create different editions (digest, volumes, versions, whatever) of your newsletter. Normally email newsletters are sent out once a month, week, year, etc.
To handle this, content and static files are overrideable according to the path which you supply to the nodeletter url.
As an example, say we release a newsletter monthly and I want to create a newsletter for March, 2013.
- Create a folder structure under content:
- Put your junk in that folder
- Get your browser to open the folder by visiting:
- And that's how you do it
Note: nodeletter will ONLY look for content within the subdirectory you give it.
- Create a folder structure under content (not static):
- Put your junk in that folder
Note: nodeletter will OVERRIDE static files it finds in the subdirectory, but also load static files from the main static directory.
- Build the directory structure using the
nodeletter create template_name
This uses the
nodeletter project template to get you started.
Configure things appropriately in the .js file (like base path and such).
Get crackin' on your sweet newsletter (Kiwi template, generation logic, styles, images, content, Hobbits, etc.).
If you want some markup to start with, I suggest taking a look at MailChimps excellent email newsletter templates
Start the nodeletter server.
- Define render modes for developing and testing your newsletter. Render modes are displayed according to the specified path:
- render_mode: type of render mode, default is
- If a render mode is set given the "generate: true" option, it will save the produced output to the content path under '.gen'
This project is in its infancy but is being actively developed. Let me know you have any problems.
Copyright (C) 2013 Matthew Coleman
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.