Search results

How to deliver newsletters for your Jekyll site

by Tom Johnson on Oct 23, 2016
categories: jekyll

Although email may seem somewhat antiquated, it has by far the greatest reach of any online communication method. If you have a Jekyll-based site, here's an easy approach to sending out an email newsletter. This approach involves using a for loop to get a summary of your latest posts and then pushing the content into simple HTML formatting that you can paste into Tinyletter's email template.

I’ve been blogging since 2006, but it took me a number of years before I realized that email usually has a far greater reach than RSS or social media. Regardless of which venue has the most impact, you don’t want to exclude email from your reach. Here’s my approach to delivering email in a free, painless way.

I use Tinyletter (it’s free and works pretty well). (I have 3,500 subscribers, so most other newsletter platforms that have a free threshold at 2,000 don’t work for me.)

Each of my posts has a summary tag in the frontmatter, as well as a bitlink property, which is the shortlink from Bitly that I use to track clicks. I create a new file called newslettertemplate.html and store this in my root directory. The newsletter template has the following code:


---
layout: none
---

* TOC
{:toc}

<!-- site logo -->
<a href="https://idratherbewriting.com"><img src="https://s3.us-west-1.wasabisys.com/idbwmedia.com/images/idratherbewriting-site-logo.png"></a>

{% for post in site.posts limit:6 %}
<h2>{{post.title}}</h2>
<p>{{post.description}} <a href="{{post.bitlink}}">Read more &raquo;</a></p>

{% endfor %}

<!-- advertising -->
<p><a href="https://s3.us-west-1.wasabisys.com/idbwmedia.com/images/comics/adobefm.jpg"><img src="https://s3.us-west-1.wasabisys.com/idbwmedia.com/images/comics/adobefm.jpg"></p></a>

You can view the rendered template here: https://idratherbewriting.com/newslettertemplate/.

My layout none is a layout that has no formatting. The newsletter template code loops through the last 6 posts on the site and pushes in the title, summary, and bitlink.

After the site builds, I go to the page, view the source, and copy this HTML into a new campaign in Tinyletter (pasting into the source) and send it out to my readers.

I’ve noticed that pushing links out on Twitter gets about 10 clicks per post, and Linkedin gets about 10 clicks as well. But when I send out the email newsletter, I get about 100 clicks. (These are all rough estimates.)

I embed the Tinyletter sign-up form in my blog’s sidebar and in the bottom of each post. Generally I get about 50 new subscribers every week. When I send out a newsletter, I lose about 10 subscribers. The process of growing my audience is slow but steady.

In general, I try to include about 3 posts with each newsletter (although sometimes I include more if I’ve forgotten to send it out). The best days to send out a newsletter are Monday through Thursday, especially during work hours. I get most of the hits within the first 2 days of sending out the email. After that it tapers off.

Bitlink is great for gauging how many hits each article has. Some articles get three or four times as many hits as others. I should keep note of those articles and learn to focus more on those topics in the future, but I’m not actually this organized.

About Tom Johnson

Tom Johnson

I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, plain language, tech comm careers, and more. Check out my API documentation course if you're looking for more info about documenting APIs. Or see my posts on AI and AI course section for more on the latest in AI and tech comm.

If you're a technical writer and want to keep on top of the latest trends in the tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me. Finally, note that the opinions I express on my blog are my own points of view, not that of my employer.