Chaining template filters in Eleventy

Posted on 8 February 2020. Tagged with web development, eleventy

This week I've been making the blog section of this site a little more sophisticated. Using Eleventy's collections, I've added post categories so you can filter posts by topic.

I wanted to show the post's tags in a single line, each linking to a page where you can see posts about that topic, separated by a comma. You can see what I wanted to achieve above, below the post title.

To display a list of the current page's tags, you use the tags variable from the frontmatter. To display a list of tags in a <ul> element, you could do something like this:

    {% for tag in tags %}
        <li><a href="/blog/tags/{{tag}}">{{tag}}</a></li>
    {% endfor %}

This wasn't good enough for my use case because:

Template filters to the rescue

Eleventy's template filters make it easy to do little tweaks to your content. These are added to the .eleventy.js config file so you can use them throughout your project. A good example of this is readableDate, which takes a date object and returns a nice string:

eleventyConfig.addFilter('readableDate', dateObj => {
  return DateTime.fromJSDate(dateObj, {
    zone: 'utc'
  }).toFormat('d LLLL y');

Chaining filters together

Something really cool about these filters is that you can chain them together, passing the output from one filter to the next. This means you can solve more complicated problems without writing more complicated code.

This means that I could solve my tags list problem in a readable, concise way. This is the code in my Nunjucks template:

<p>Tagged with {{ tags | withoutPostTag |
  transformToLinks | joinWithComma | safe }}</p>

Below, I'll explain what each filter does and show you the code.


This filter returns the same array, without the post tag.

In .eleventy.js:

eleventyConfig.addFilter('withoutPostTag', tags => {
  return tags.filter(t => t !== "post")


This filter takes the array of tags and uses the map function to return an array of <a> elements with the proper href attribute.

In .eleventy.js:

eleventyConfig.addFilter('transformToLinks', tags => {
  return => {
    const tagUrl = `/blog/tags/${tag}`
    return `<a href="${tagUrl}">${tag}</a>`


This filter takes the array of links and returns a string of the elements, separated by a comma.

In .eleventy.js:

eleventyConfig.addFilter('joinWithComma', strings => {
  return strings.join(", ")


This is a built in Nunjucks filter that tells Nunjucks not to escape the content.

Pros and cons of this approach

I like this approach because:

I can see a couple of limitations:

What do you think about this pattern? I'm keen to hear if there's a better way, or more limitations I haven't considered.

I don't have comments on my blog yet. Tell me what you think on Twitter.