<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Templating on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/templating/</link>
    <description>Recent content in Templating on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 17 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/templating/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Node.js Template Engines in 2026: EJS vs Pug vs Nunjucks — Which One for Server-Side Rendering?</title>
      <link>https://www.pistack.xyz/posts/2026-08-17-javascript-template-engines-ejs-pug-nunjucks-comparison/</link>
      <pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-17-javascript-template-engines-ejs-pug-nunjucks-comparison/</guid>
      <description>&lt;p&gt;Your Express server needs to render HTML. You can concatenate strings — for about a week, until you need layouts, includes, conditionals, and HTML escaping that actually works. That is what template engines are for, and Node.js has three serious candidates: &lt;strong&gt;EJS (8,117 stars), Pug (21,853 stars), and Nunjucks (8,984 stars)&lt;/strong&gt;. They look interchangeable at a glance — they all take data and produce HTML — but they differ so much in syntax, safety defaults, and ecosystem fit that picking the wrong one will cost you either a debugging week or a security review.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
