Templates Guide

markata-go uses pongo2, a Django/Jinja2-like template engine for Go. This guide covers everything you need to know about creating and customizing templates.

Table of Contents

• Overview
• Cached HTML on Warm Builds
• Template Location
• Template Syntax
• Available Variables
• Built-in Filters
• Template Inheritance
• Including Partials
• Post vs Feed Templates
• Custom Templates Per Post
• Complete Examples

Overview

Templates wrap your rendered Markdown content in HTML layouts. The template system supports:

• Template inheritance - Base templates with extendable blocks
• Includes - Reusable partial templates
• Variables and expressions - Access post, config, and feed data
• Control flow - Conditionals and loops
• Filters - Transform data for display
• Custom templates per post - Override templates in frontmatter
• Presentation templates - Turn markdown into reveal.js slide decks

Cached HTML on Warm Builds

Both DAG and legacy warm builds can reuse cached article and full-page HTML. Restored HTML preserves the exact cached bytes, without changing your template output. Disk restoration reads directly into string-owned storage, avoiding an extra full-page byte buffer and string copy. A small reusable transfer buffer does not retain or modify the returned HTML.

No configuration changes or cache reset are needed: cache paths, keys and freshness checks are unchanged. Missing or unreadable disk entries fall back to rendering rather than returning partial HTML. Once HTML is loaded in memory, later reads in the same build can reuse it without accessing the disk.

Template Location

Templates are loaded from these locations (in order of priority):

1. Project templates: templates/ directory in project root
2. Theme templates: themes/{theme}/templates/ for custom themes
3. Default theme: themes/default/templates/ as fallback

my-site/
├── templates/           # Project templates (highest priority)
│   ├── base.html
│   ├── post.html
│   ├── feed.html
│   └── partials/
│       ├── header.html
│       ├── footer.html
│       └── card.html
├── themes/
│   └── my-theme/
│       └── templates/   # Theme templates
└── posts/

Configure the templates directory in markata-go.toml:

[markata-go]
templates_dir = "templates"

Template Syntax

Variables

Access data using double curly braces:

{{ post.Title }}
{{ config.URL }}
{{ post.Date }}

Attribute Access

{{ post.Title }}              {# Direct attribute access #}
{{ post.Extra.custom_field }} {# Nested attributes #}

Filters

Transform values using the pipe (|) operator:

{{ post.Title|upper }}
{{ post.Description|truncate:160 }}
{{ post.Date|date_format:"January 2, 2006" }}
{{ post.Tags|join:", " }}
{{ post.ArticleHTML|safe }}
{{ value|default_if_none:"N/A" }}

Comments

{# This is a comment and won't appear in output #}

{#
Multi-line
comment
#}

Control Flow

Conditionals

{% if post.Published %}
    <span class="status">Published</span>
{% elif post.Draft %}
    <span class="status">Draft</span>
{% else %}
    <span class="status">Private</span>
{% endif %}

Loops

{% for tag in post.Tags %}
    <a href="/tags/{{ tag|slugify }}/">{{ tag }}</a>
    {% if not forloop.Last %}, {% endif %}
{% endfor %}

{% for post in posts %}
    <li>{{ post.Title }}</li>
{% empty %}
    <li>No posts found</li>
{% endfor %}

Loop Variables

Inside {% for %} loops, these variables are available:

Available Variables

Post Context

When rendering individual posts, these variables are available:

Config Context

Site configuration is available via config:

Shorthand aliases are also available:

Feed Context

When rendering feeds/archives, these additional variables are available:

Built-in Filters

The built-in slides_reveal filter converts rendered HTML into reveal.js slide sections.

• h2 starts a new horizontal slide
• hr starts a new horizontal slide, which aligns with the common Markdown --- slide separator used by reveal.js and Marp
• h3 starts a new vertical slide under the current horizontal slide

Date Formatting

Use human_date for visible HTML dates so cards, post bylines, archive views, and reader metadata stay consistent while datetime attributes remain machine-readable.

Note: Go uses reference time formatting. Common formats:

String Manipulation

Collections

HTML/Text

URLs

Default Values

Template Inheritance

Template inheritance lets you create a base layout that child templates extend.

Base Template

{# templates/base.html #}
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>{% block title %}{{ config.Title }}{% endblock %}</title>
    <meta name="description" content="{% block description %}{{ config.Description }}{% endblock %}">
    {% block head %}{% endblock %}
</head>
<body>
    {% block header %}
    <header>
        <nav>
            <a href="/">{{ config.Title }}</a>
            <a href="/blog/">Blog</a>
            <a href="/about/">About</a>
        </nav>
    </header>
    {% endblock %}

    <main>
        {% block content %}{% endblock %}
    </main>

    {% block footer %}
    <footer>
        <p>&copy; {{ config.Author }}</p>
    </footer>
    {% endblock %}

    {% block scripts %}{% endblock %}
</body>
</html>

Extending the Base

{# templates/post.html #}
{% extends "base.html" %}

{% block title %}{{ post.Title }} | {{ config.Title }}{% endblock %}

{% block description %}{{ post.Description|default_if_none:config.Description }}{% endblock %}

{% block head %}
<meta property="og:title" content="{{ post.Title }}">
<meta property="og:type" content="article">
<meta property="og:url" content="{{ config.URL }}{{ post.Href }}">
{% if post.Date %}
<meta property="article:published_time" content="{{ post.Date|atom_date }}">
{% endif %}
{% endblock %}

{% block content %}
<article>
    {{ body|safe }}
</article>
{% endblock %}

Using {{ block.super }}

Include parent block content with {{ block.super }}:

{% block scripts %}
{{ block.super }}
<script src="/js/post.js"></script>
{% endblock %}

Including Partials

Partials are reusable template fragments. Use {% include %} to embed them:

{% include "partials/header.html" %}
{% include "partials/card.html" %}
{% include "partials/footer.html" %}

Example Partial: Card

{# templates/partials/card.html #}
<article class="card">
    <a href="{{ post.Href }}">
        {% if post.Extra.cover_image %}
        <img src="{{ post.Extra.cover_image }}" alt="{{ post.Title }}">
        {% endif %}
        <h2>{{ post.Title }}</h2>
    </a>
    {% if post.Description %}
    <p>{{ post.Description }}</p>
    {% endif %}
    <footer>
        {% if post.Date %}
        <time datetime="{{ post.Date|atom_date }}">
            {{ post.Date|human_date }}
        </time>
        {% endif %}
        {% if post.Extra.reading_time %}
        <span>{{ post.Extra.reading_time }}</span>
        {% endif %}
    </footer>
</article>

Example Partial: Navigation

{# templates/partials/nav.html #}
<nav class="main-nav">
    <a href="/" class="logo">{{ config.Title }}</a>
    <ul>
        <li><a href="/blog/">Blog</a></li>
        <li><a href="/tags/">Tags</a></li>
        <li><a href="/about/">About</a></li>
    </ul>
</nav>

Post vs Feed Templates

Post Templates

Post templates render individual content pages. They receive the post and body variables.

Default template: post.html

For an image collection, use the built-in gallery.html template and gallery frontmatter. See the photo galleries guide.

{# templates/post.html #}
{% extends "base.html" %}

{% block title %}{{ post.Title }} | {{ config.Title }}{% endblock %}

{% block content %}
<article class="post">
    <header>
        <h1>{{ post.Title }}</h1>
        {% if post.Date %}
        <time datetime="{{ post.Date|atom_date }}">
            {{ post.Date|human_date }}
        </time>
        {% endif %}

        {% if post.Tags %}
        <ul class="tags">
            {% for tag in post.Tags %}
            <li><a href="/tags/{{ tag|slugify }}/">{{ tag }}</a></li>
            {% endfor %}
        </ul>
        {% endif %}
    </header>

    <div class="content">
        {{ body|safe }}
    </div>
</article>
{% endblock %}

Feed Templates

Feed templates render lists/archives of posts. They receive feed, page, and posts variables.

Default template: feed.html

{# templates/feed.html #}
{% extends "base.html" %}

{% block title %}{{ feed.Title }} | {{ config.Title }}{% endblock %}

{% block content %}
<section class="feed">
    <h1>{{ feed.Title }}</h1>
    {% if feed.Description %}
    <p class="description">{{ feed.Description }}</p>
    {% endif %}

    <ul class="post-list">
        {% for post in posts %}
        <li>
            {% include "partials/card.html" %}
        </li>
        {% endfor %}
    </ul>

    {% if page.HasPrev or page.HasNext %}
    <nav class="pagination">
        {% if page.HasPrev %}
        <a href="{{ page.PrevURL }}" class="prev">&larr; Previous</a>
        {% endif %}

        <span>Page {{ page.Number }}</span>

        {% if page.HasNext %}
        <a href="{{ page.NextURL }}" class="next">Next &rarr;</a>
        {% endif %}
    </nav>
    {% endif %}
</section>
{% endblock %}

Custom Templates Per Post

Override the default template for specific posts using the template frontmatter field.

Simple Override

---
title: "My Landing Page"
template: "landing.html"
---

This post will use templates/landing.html instead of the default post.html.

Creating a Slide Deck

---
title: "Platform Roadmap"
template: "slides.html"
---

## Opening

Intro slide.

### Details

Vertical follow-up slide.

---

## Next Section

slides.html renders the page as a reveal.js deck. In the default template:

1. ## headings become new horizontal slides.
2. ### headings become vertical slides nested under the current horizontal slide.
3. --- becomes a horizontal slide break because Markdown renders it as <hr>.
4. Reveal assets use local assets/vendor/revealjs/... URLs automatically when [markata-go.assets].mode is self-hosted or auto and the assets are available. Run markata-go assets download to prefetch them.
5. On small screens, the deck sizes itself to the current viewport so slides stay readable on phones and after rotation.

Creating a Landing Page Template

{# templates/landing.html #}
{% extends "base.html" %}

{% block title %}{{ post.Title }}{% endblock %}

{% block header %}
{# No header on landing page #}
{% endblock %}

{% block content %}
<div class="landing">
    <section class="hero">
        <h1>{{ post.Title }}</h1>
        {% if post.Description %}
        <p class="tagline">{{ post.Description }}</p>
        {% endif %}
    </section>

    <section class="content">
        {{ body|safe }}
    </section>

    {% if post.Extra.cta_text %}
    <section class="cta">
        <a href="{{ post.Extra.cta_url }}" class="button">
            {{ post.Extra.cta_text }}
        </a>
    </section>
    {% endif %}
</div>
{% endblock %}

{% block footer %}
{# Minimal footer #}
<footer class="minimal">
    <p>&copy; {{ config.Author }}</p>
</footer>
{% endblock %}

Template Fallback

If a specified template doesn't exist, markata-go falls back to: 1. post.html (for posts) 2. feed.html (for feeds)

Complete Examples

base.html

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>{% block title %}{{ config.Title }}{% endblock %}</title>
    <meta name="description" content="{% block description %}{{ config.Description }}{% endblock %}">

    {# Open Graph #}
    <meta property="og:title" content="{% block og_title %}{{ config.Title }}{% endblock %}">
    <meta property="og:description" content="{% block og_description %}{{ config.Description }}{% endblock %}">
    <meta property="og:url" content="{{ config.URL }}{% block og_url %}/{% endblock %}">
    <meta property="og:site_name" content="{{ config.Title }}">

    {# Feeds #}
    <link rel="alternate" type="application/rss+xml" title="{{ config.Title }} RSS" href="{{ config.URL }}/blog/rss.xml">
    <link rel="alternate" type="application/atom+xml" title="{{ config.Title }} Atom" href="{{ config.URL }}/blog/atom.xml">

    {# Styles #}
    <link rel="stylesheet" href="/css/style.css">

    {% block head %}{% endblock %}
</head>
<body>
    <a href="#main" class="skip-link">Skip to content</a>

    {% block header %}
    <header class="site-header">
        <div class="container">
            <a href="/" class="logo">{{ config.Title }}</a>
            <nav class="main-nav">
                <ul>
                    <li><a href="/blog/">Blog</a></li>
                    <li><a href="/tags/">Tags</a></li>
                    <li><a href="/about/">About</a></li>
                </ul>
            </nav>
        </div>
    </header>
    {% endblock %}

    <main id="main">
        <div class="container">
            {% block content %}{% endblock %}
        </div>
    </main>

    {% block footer %}
    <footer class="site-footer">
        <div class="container">
            <p>&copy; {{ config.Author }}. Built with <a href="https://github.com/example/markata-go">markata-go</a>.</p>
        </div>
    </footer>
    {% endblock %}

    {% block scripts %}{% endblock %}
</body>
</html>

post.html

{% extends "base.html" %}

{% block title %}{{ post.Title }} | {{ config.Title }}{% endblock %}
{% block description %}{{ post.Description|default_if_none:config.Description }}{% endblock %}

{% block og_title %}{{ post.Title }}{% endblock %}
{% block og_description %}{{ post.Description|default_if_none:config.Description }}{% endblock %}
{% block og_url %}{{ post.Href }}{% endblock %}

{% block head %}
<meta property="og:type" content="article">
{% if post.Date %}
<meta property="article:published_time" content="{{ post.Date|atom_date }}">
{% endif %}
{% if post.Tags %}
{% for tag in post.Tags %}
<meta property="article:tag" content="{{ tag }}">
{% endfor %}
{% endif %}

{# JSON-LD structured data #}
<script type="application/ld+json">
{
    "@context": "https://schema.org",
    "@type": "BlogPosting",
    "headline": "{{ post.Title }}",
    "description": "{{ post.Description }}",
    "author": {
        "@type": "Person",
        "name": "{{ config.Author }}"
    },
    {% if post.Date %}
    "datePublished": "{{ post.Date|atom_date }}",
    {% endif %}
    "url": "{{ config.URL }}{{ post.Href }}"
}
</script>
{% endblock %}

{% block content %}
<article class="post h-entry">
    <header class="post-header">
        <h1 class="post-title p-name">{{ post.Title }}</h1>

        <div class="post-meta">
            {% if post.Date %}
            <time class="dt-published" datetime="{{ post.Date|atom_date }}">
                {{ post.Date|date_format:"January 2, 2006" }}
            </time>
            {% endif %}

            {% if post.Extra.reading_time %}
            <span class="reading-time">{{ post.Extra.reading_time }}</span>
            {% endif %}
        </div>

        {% if post.Tags %}
        <ul class="post-tags">
            {% for tag in post.Tags %}
            <li>
                <a href="/tags/{{ tag|slugify }}/" rel="tag" class="p-category">{{ tag }}</a>
            </li>
            {% endfor %}
        </ul>
        {% endif %}
    </header>

    <div class="post-content e-content">
        {{ body|safe }}
    </div>

    <footer class="post-footer">
        <div class="author-info">
            <span>Written by</span>
            <a href="/about/" class="p-author h-card" rel="author">{{ config.Author }}</a>
        </div>

        {% if post.Extra.prev or post.Extra.next %}
        <nav class="post-nav">
            {% if post.Extra.prev %}
            <a href="{{ post.Extra.prev.Href }}" class="prev" rel="prev">
                <span>&larr; Previous</span>
                <span class="title">{{ post.Extra.prev.Title }}</span>
            </a>
            {% endif %}
            {% if post.Extra.next %}
            <a href="{{ post.Extra.next.Href }}" class="next" rel="next">
                <span>Next &rarr;</span>
                <span class="title">{{ post.Extra.next.Title }}</span>
            </a>
            {% endif %}
        </nav>
        {% endif %}
    </footer>
</article>
{% endblock %}

feed.html

{% extends "base.html" %}

{% block title %}{{ feed.Title }} | {{ config.Title }}{% endblock %}
{% block description %}{{ feed.Description|default_if_none:config.Description }}{% endblock %}

{% block og_title %}{{ feed.Title }}{% endblock %}
{% block og_url %}/{{ feed.Slug }}/{% endblock %}

{% block head %}
<meta property="og:type" content="website">
{% endblock %}

{% block content %}
<section class="feed">
    <header class="feed-header">
        <h1>{{ feed.Title }}</h1>
        {% if feed.Description %}
        <p class="feed-description">{{ feed.Description }}</p>
        {% endif %}
    </header>

    {% if posts|length > 0 %}
    <ul class="post-list">
        {% for post in posts %}
        <li class="post-item">
            <article class="card h-entry">
                <h2 class="card-title">
                    <a href="{{ post.href }}" class="p-name u-url">{{ post.title }}</a>
                </h2>

                {% if post.description %}
                <p class="card-description p-summary">{{ post.description }}</p>
                {% endif %}

                <footer class="card-meta">
                    {% if post.date %}
                    <time class="dt-published" datetime="{{ post.date|atom_date }}">
                        {{ post.date|date_format:"Jan 2, 2006" }}
                    </time>
                    {% endif %}

                    {% if post.tags %}
                    <ul class="card-tags">
                        {% for tag in post.tags %}
                        <li><a href="/tags/{{ tag|slugify }}/">{{ tag }}</a></li>
                        {% endfor %}
                    </ul>
                    {% endif %}
                </footer>
            </article>
        </li>
        {% endfor %}
    </ul>

    {% if page.HasPrev or page.HasNext %}
    <nav class="pagination" aria-label="Pagination">
        {% if page.HasPrev %}
        <a href="{{ page.PrevURL }}" class="pagination-prev" rel="prev">
            &larr; Newer Posts
        </a>
        {% else %}
        <span class="pagination-prev disabled">&larr; Newer Posts</span>
        {% endif %}

        <span class="pagination-info">Page {{ page.Number }}</span>

        {% if page.HasNext %}
        <a href="{{ page.NextURL }}" class="pagination-next" rel="next">
            Older Posts &rarr;
        </a>
        {% else %}
        <span class="pagination-next disabled">Older Posts &rarr;</span>
        {% endif %}
    </nav>
    {% endif %}

    {% else %}
    <p class="no-posts">No posts found.</p>
    {% endif %}
</section>
{% endblock %}

Card Media Helpers

OG, feed, and embed cards share the same media helpers so the image/video preview feels identical everywhere. When rendering card media:

• Pass the URL through with_size(width, height) so the helper appends explicit w and h query parameters that match the printed dimensions of the card. Correct query params keep downstream screenshotters and feed readers aligned with the rendered size. Trusted media URLs are normalized to https first so browser pages do not hit mixed-content errors.
• For trusted remote image hosts that support width-based resizing, use responsive_srcset with candidate widths and a matching sizes attribute so browsers download an image close to the rendered size. For lazy images with variable layouts, sizes="auto, ...fallback..." uses the measured width when supported. The filter skips local paths and unknown hosts; use image_optimization for local files. Use original_media_url for a deferred lightbox URL when the reader should open the original image.
• Use media_url when you only need the first non-empty media field or a search thumbnail URL. It keeps trusted media URLs on https without adding sizing parameters.
• Use the fragment/query-safe is_video filter to decide between <video> and <img>, and call poster_url(post) to resolve the poster. poster_url enforces the alias precedence (poster_image, poster, video_poster, video_thumbnail, thumbnail, thumb) before falling back to deriving a .webp thumbnail from the video URL when the host is trusted.

Only relative URLs and hosts on the default allowlist (dropper.wayl.one, dropper.waylonwalker.com, dropper-dev.wayl.one) gain the sizing parameters and derived posters. Override or extend the list via [markata-go.templates.media] in your configuration when you use a different CDN. If you need to opt out, you can skip these filters in your custom template, but keep alias resolution and sizing in sync across OG/feed/embed templates so the published meta stays consistent.

partials/card.html

<article class="card h-entry">
    {% if post.cover_image %}
    <a href="{{ post.href }}" class="card-image">
        <img src="{{ post.cover_image }}" alt="{{ post.title }}" loading="lazy">
    </a>
    {% endif %}

    <div class="card-body">
        <h2 class="card-title">
            <a href="{{ post.href }}" class="p-name u-url">{{ post.title }}</a>
        </h2>

        {% if post.description %}
        <p class="card-description p-summary">
            {{ post.description|truncate:160 }}
        </p>
        {% endif %}

        <footer class="card-footer">
            {% if post.date %}
            <time class="dt-published" datetime="{{ post.date|atom_date }}">
                {{ post.date|date_format:"Jan 2, 2006" }}
            </time>
            {% endif %}

            {% if post.reading_time %}
            <span class="reading-time">{{ post.reading_time }}</span>
            {% endif %}

            {% if post.tags %}
            <ul class="card-tags">
                {% for tag in post.tags|slice:":3" %}
                <li><a href="/tags/{{ tag|slugify }}/" class="p-category">{{ tag }}</a></li>
                {% endfor %}
            </ul>
            {% endif %}
        </footer>
    </div>
</article>

partials/header.html

<header class="site-header">
    <div class="container">
        <a href="/" class="site-logo">
            {% if config.Extra.logo %}
            <img src="{{ config.Extra.logo }}" alt="{{ config.Title }}">
            {% else %}
            {{ config.Title }}
            {% endif %}
        </a>

        <nav class="main-nav" aria-label="Main navigation">
            <button class="nav-toggle" aria-expanded="false" aria-controls="nav-menu">
                <span class="sr-only">Menu</span>
                <span class="hamburger"></span>
            </button>

            <ul id="nav-menu" class="nav-menu">
                <li><a href="/">Home</a></li>
                <li><a href="/blog/">Blog</a></li>
                <li><a href="/tags/">Tags</a></li>
                <li><a href="/about/">About</a></li>
            </ul>
        </nav>
    </div>
</header>

partials/footer.html

<footer class="site-footer">
    <div class="container">
        <div class="footer-content">
            <div class="footer-section">
                <h3>{{ config.Title }}</h3>
                <p>{{ config.Description }}</p>
            </div>

            <div class="footer-section">
                <h3>Links</h3>
                <ul>
                    <li><a href="/blog/">Blog</a></li>
                    <li><a href="/tags/">Tags</a></li>
                    <li><a href="/about/">About</a></li>
                </ul>
            </div>

            <div class="footer-section">
                <h3>Subscribe</h3>
                <ul>
                    <li><a href="/blog/rss.xml">RSS Feed</a></li>
                    <li><a href="/blog/atom.xml">Atom Feed</a></li>
                    <li><a href="/blog/feed.json">JSON Feed</a></li>
                </ul>
            </div>
        </div>

        <div class="footer-bottom">
            <p>&copy; {{ config.Author }}. Built with <a href="https://github.com/example/markata-go">markata-go</a>.</p>
        </div>
    </div>
</footer>

Microformats2 Support

markata-go's default templates include Microformats2 markup for better interoperability with IndieWeb tools and feed readers.

h-entry on Posts

Single post pages include h-entry markup on the <article> element:

<article class="post h-entry">
  <a class="u-url" href="https://example.com/my-post/" hidden></a>
  <header>
    <h1 class="p-name">Post Title</h1>
    <time class="dt-published" datetime="2024-01-15T00:00:00Z">January 15, 2024</time>
    <span class="p-author h-card" hidden>
      <a class="u-url p-name" href="https://example.com">Author Name</a>
    </span>
  </header>
  <div class="post-content e-content">
    <!-- rendered content -->
  </div>
  <div class="tags">
    <a class="p-category" href="/tags/topic/">topic</a>
  </div>
</article>

Properties used: - h-entry - Entry/post container - p-name - Post title - u-url - Canonical permalink - dt-published - Publication date - e-content - Entry content (HTML) - p-summary - Post description/excerpt - p-category - Tags/categories - p-author h-card - Author information

h-feed on Listings

Feed and listing pages include h-feed markup:

<div class="feed h-feed">
  <h1 class="p-name">Blog Posts</h1>
  <p class="p-summary">All blog posts</p>
  <span class="p-author h-card" hidden>
    <a class="u-url p-name" href="https://example.com">Site Author</a>
  </span>

  <!-- Each card is an h-entry -->
  <article class="card h-entry">...</article>
</div>

Card Types

All card templates include appropriate microformat classes:

Validation

Test your microformats with: - IndieWebify.me - Validate h-entry markup - Pin13 - Parse and view microformats

Text Templates

markata-go generates .txt versions of posts for consumers that need plain text (LLMs, CLI tools, accessibility readers, etc.). Text templates require special handling because pongo2 auto-escapes all {{ }} output by default, which would produce HTML entities (&, <) in plain text files.

The plaintext Filter

Use |plaintext for any variable that contains HTML content (like rendered Markdown):

{{ post.content|plaintext }}

This filter: 1. Strips all HTML tags 2. Decodes HTML entities to literal characters 3. Converts <a href="..."> links to footnote-style references 4. Marks the output as safe so pongo2 won't re-escape it

The safe Filter for Metadata

For plain text strings that never contain HTML (like title and description), use |safe to prevent auto-escaping:

{{ post.title|safe }}
{{ post.description|safe }}

Example: default.txt

{{ body|safe }}

Example: default.ansi

{{ body|safe }}

For terminal output templates, body contains the fully rendered terminal page for the selected format. default.txt uses the plain terminal renderer, while default.ansi uses the ANSI-styled renderer.

Link Footnotes

Links in HTML content are converted to numbered footnote references:

Read the Go docs [1] for more info. See also the
Go blog [2] for tutorials.

References:
[1]: https://go.dev/doc/
[2]: https://go.dev/blog/

Duplicate URLs reuse the same reference number. When link text is the same as the URL, no footnote marker is added.

Tips and Best Practices

1. Always use |safe for HTML content - When outputting rendered HTML (like body or post.ArticleHTML), use the safe filter to prevent double-escaping.

2. Provide fallbacks with default_if_none - Use fallback values for optional fields to avoid empty output.

3. Use template inheritance - Create a solid base.html and extend it for consistency across your site.

4. Keep partials small and focused - Each partial should do one thing well.

5. Use semantic HTML - Include appropriate ARIA attributes and semantic elements for accessibility.

6. Add microformats - Include h-entry, h-card, and other microformats for better interoperability.

7. Cache considerations - Templates are cached for performance. Clear the cache during development if changes don't appear.

See Also

• Configuration Guide - Configure template settings
• Feeds Guide - Learn about the feed system
• Themes Guide - Create and customize themes
• pongo2 Documentation - Full template engine reference