Tera Templates

Customizable templates without recompilation

sukr uses Tera, a Jinja2-like templating engine. Templates are loaded at runtime, so you can modify them without recompiling sukr. See the Tera documentation for template authoring syntax (filters, blocks, inheritance).

Template Directory Structure¶

templates/
├── base.html               # Shared layout (required)
├── page.html               # Standalone pages and homepage
├── section/
│   ├── default.html        # Fallback section index
│   ├── blog.html           # Blog section index
│   └── projects.html       # Projects section index
├── content/
│   ├── default.html        # Fallback content page
│   └── post.html           # Blog post
└── tags/
    └── default.html        # Tag listing page

Template Inheritance¶

All templates extend base.html:

{% extends "base.html" %} {% block content %}
<article>
  <h1>{{ page.title }}</h1>
  {{ content | safe }}
</article>
{% endblock content %}

base.html defines two overridable blocks: {% block title %} for the HTML <title> tag, and {% block content %} for the page body.

Available Context Variables¶

All Templates¶

Variable	Description
`config.title`	Site title
`config.author`	Site author
`config.nav.nested`	Whether hierarchical nav is enabled
`nav`	Array of navigation items
`page_path`	Current page path
`prefix`	Relative path prefix for assets
`config.base_url`	Canonical base URL
`title`	Current page title

Each nav item has:

label — Display text
path — URL path
weight — Sort order
children — Child nav items (when config.nav.nested is true)

Page Templates¶

Variable	Description
`page.title`	Page title
`page.description`	Page description
`page.lang`	Resolved document language from frontmatter or auto-detection
`page.toc`	Whether TOC is enabled for this page
`page.extra`	Custom metadata table from frontmatter
`content`	Rendered HTML content
`anchors`	Array of heading anchors for TOC

Use page.lang when you want the current rendered document's language in templates. In multilingual sites, it is often better to keep a fixed site language on <html> for shared chrome and apply page.lang to the content container instead:

<html lang="en">
  <body>
    <article lang="{{ page.lang | default(value="en") }}">

This lets the layout remain in English, for example, while an individual page or post can still declare Spanish or another language.

Each anchor in anchors has:

id — Heading slug (for href="#id")
label — Heading text
level — Heading level (2-6, h1 excluded)

Section Templates¶

Variable	Description
`section.title`	Section title
`section.description`	Section description
`section.lang`	Resolved language for the section index document
`section.extra`	Custom metadata table from frontmatter
`items`	Array of content items in section

Content Item Fields (in )¶

items

Items expose path and slug directly, and document metadata under item.frontmatter.

Variable	Description
`item.path`	URL path
`item.slug`	URL slug
`item.frontmatter.title`	Content title
`item.frontmatter.description`	Content description
`item.frontmatter.date`	Publication date
`item.frontmatter.lang`	Resolved item language from frontmatter or auto-detection
`item.frontmatter.extra`	Custom metadata table from frontmatter

If you want listing cards to expose language, use item.frontmatter.lang. You do not need a separate item.lang unless you want a flatter API surface for convenience.

Tag Templates¶

Variable	Description
`tag`	The tag name
`items`	Array of content items with this tag

Template Override¶

Set template in frontmatter to use a custom template:

+++
title = "Special Page"
template = "special.html"
+++

This uses templates/special.html instead of the default.