thor/site/content/docs.md

{ "title": "Docs", "date": "2026-07-22T08:54:00-04:00", "toc": true }

Introduction

This guide assumes you have either read The Guide, or have built a Hugo site before. It also assumes you have a basic knowledge of HTML and CSS.

Features

Thor has many features and content processors available. In an effort to provide the best out of the box experience, most of them are enabled by default.

Opt-In Features

TODO: #### deflist syntax

TODO: #### footnotes

Minify

If enabled, minify will perform simple whitespace removal on all your output .html files, and any .css files in your assets directories. Minifying JavaScript is not supported (yet).

TODO: Do we minify inline css?

Opt-Out Features

• emoji
• sidenotes/marginnotes
• syntax highlighting
• heading ids
• TODO: Table Of Contents Generation
• GitHub style alerts

Directories

Like Hugo, a Thor project is a collection of specially named directories, plus an optional config file. All directories are optional, but it is recommended to at least have a content directory.

content

content holds your pages and page bundles. See Content. If not found, thor will look for content files in the root of your current working directory.

assets : assets contains any static files for your site (favicon.ico, etc.), as well as files you want to send through the asset pipeline (CSS or JS files).

layouts

layouts holds your templates and partials. See Templates.

public : public will contain your completed site.

All of these names can be remapped in thor.json.¹

Assets

Currently, there is only one asset processor, and that is the minifier, though more are planned (i.e. Image processing).

TODO: Expand

Content

Pages & Page Bundles

Page content can either be defined in a single file (contact.md), or in a directory (contact/index.md + contact/our-team.jpg). Single file pages are preferred to page bundles.²

Thor currently supports 2 formats for page files: MarkDown (.md), and HTML (.html).

TODO: Content

Frontmatter

TODO: Frontmatter

Menus

TODO: Describe

TODO: Don't forget to highlight differences from Hugo.

Templates³

Sites are built using one or more template files written in an extended version of mustache templates. The mustache manual has great explainations and a lot of examples if you want to know more, but I'll summarize them for you here.

The beauty of Mustache is that there is very little syntax; there are just 10 symbols you need learn: {{, {{&, {{^, {{>, {{<, {{#, /}}, {{$, {{!, and |.

TODO: ^^ Badly worded sentence ^^

TODOS: Gotta describe base templates somewhere. (the same way we describe the partials)

Tags

Variables

In order to display a scalar (not-list) value in your template, simply wrap it in double curly braces. e.g. {{ page.title }}.

This content will be HTML escaped (for safety), so if the value you're rendering contains HTML, you'll need to use the raw syntex instead {{& page.title}}⁴ which will output the value without stripping or re-writing content.

In most⁵ cases, invalid keys will be silently ignored (nothing between the braces will appear), in keeping with the official mustache spec.

Leading and trailing whitespace(s) are ignored by the parser, so the folllowing are all equivilent: {{& title }}, {{&title}}, {{& title}}.

Sections

TODO:

Inverted Sections

TODO:

Partials

TODO:

TODO: Talk about MAX_CONTEXT_DEPTH (currently 16) and how it limits the total number of nested templates to 13. (3 for [site, page, ctx])

Dynamic Partials

Blocks

TODO:

Parents

TODO:

Summary

{{page.title}} for normal values {{&page.title}} for values that contain HTML. <ul>{{#pages}}<li>{{title}}</li>{{/pages}}</ul> for list values. {{#params.is_starred}}<i class="fas fa-star"></i>{{/params.is_starred}} for conditional content. {{^pages}}No pages yet!{{/pages}} to draw content when the value is empty.

Section Names

When building your own templates, you are of course free to pick whatever names you choose for your partials and content slots. However, sticking to conventions helps create consistency in the ecosystem, and reduces friction when relying on built-in templates.

{{$main}}...{{/main}}

the main section should be used in templates to denote the part of the page that is unique to that page. For the most part, your templates should look like this

{{<base}}
{{$main}}
<main>
  <h1>Actual page content goes here</h1>
  {{&page.content}}
</main>
{{/main}}
{{/base}}

Context

When building your page(s), the following keys are accessible to your template files:

now

The Current DateTime. see DateTime

date_format

The default format to use for dates. Configured in thor.json:date.format.

timezone

The timezone to convert dates to when using {{ date | format }}. Configured in thor.json:date.timezone.

site

The site parameters that are usable in templates, see site.

pages

Returns all regular pages, sorted by ?. Regular pages exclude index pages like home and section roots.

posts

TODO: Section groupings

og

Contains the Open Graph metadata for the current page.

menus

The site's constructed menus. See menus.

Page

page.content

The HTML rendered page content

TODO: write

Site

TODO: Write

Params

site.params and page.params are an escape hatch to let users inject arbetrary data into their website. The following are some conventional examples theme developers may want to use to ensure a consistent experience across themes.

author

The author of the current page or site. See schema.org for the recommended format.

stylesheets

A list of paths to css files the users wants to include globally. These are rendered by the {{> styles }} partial, and can be omitted on sites that use custom templates.

TODO: ^^ Bad sentence? ^^

The Context Stack

When building your page(s), each template is fed a Context⁶ stack that contains all the data should you need to build your page.

The context stack is initialized⁷ as [site, page, context], meaning if you use a key like {{title}} in your template, it will look up context.title, page.title, and then finally site.title, using the first available value it can find.

TODO: As you descend into sections/partials, new contexts are placed onto the stack, so they resolve first. (LIFO order)

{{<base}}
{{$main}}
<main>
  {{&page.content}}
  <!-- Is the same as -->
  {{&content}}
  <!-- Or -->
  {{$page}}{{&content}}{{/page}}
  <!-- Or -->
  {{$page.content}}{{&.}}{{/page.content}}
</main>
{{/main}}
{{/base}}

Filters

Because mustache is a logic-less language, (there are no for or if tags), Thor extends mustache to include a handful of data filters in the form of pipes. Bash users will feel right at home here.

group_by <field>

Allows you to group pages by the given field. e.g.

{{#pages | group_by year }}
<section>
<header>{{$key}} {{! The group's year}}</header>
<ul>
{{#items}}<li>
{{title}} {{! The title of each of that year's pages }}
{{/items}}</li>
</ul>
</section>
{{/pages}}

sort_by <field> <asc|desc>

Allows you to sort pages by the given field.

first <n>

Given a list, returns only the first n items. n defaults to 1. Given a string, returns the first n runes of the string. To help catch mistakes, n is required for strings.

last <n>

Given a list, returns only the last n items. n defaults to 1. Given a string, returns the first n runes of the string. To help catch mistakes, n is required for strings.

format "<format string>"

Used to display a date in a particular format. See DateTimes. If no format is given, the default will be used.

Chaining Pipes

Thor allows you to chain two or more pipes, to allow complex data manipulation. However for performance and stylistic reasons, you are limited to no more than 8 pipes⁸ for any given tag. If you believe you need more than 8 pipes, please open an issue with a concrete example of the problem you are facing.

Examples:

{{ pages | group_by year | first }} {{! All pages from the current year }}

{{ pages | sort_by date desc | first }} {{! The latest page }}

Partials

Partials are templates that render a portion of a page. To include a partial, the standard mustache syntax is used. All partials are resolved relative to the root partial's directory, so to include a partial at layouts/partials/my_partial.html, you would use {{> my_partial}}.

Users can create or override as many partials as they want; several are included for convienience:

{{> title }}

The title of the current page. It should be placed inside the <title> tag. By default, it will appear as {{ page.title }} | {{ site.title }}.

{{> nav }}

Nav renders the main menu for the site (menus.main). It should be placed inside the <body> tag, just before the <main> block.

{{> home-link }}

This partial is rendered inside the home anchor in {{> nav }}. By default, it wil display the name of the site, or Home if no name is set.

{{> styles }}

This partial renders any stylesheets specified either by the user (via params.stylesheets) or by the theme author (specified directly in the template). params.stylesheets is intended as an escape hatch for users that want to add CSS to their site, but don't want to customize any templates. Styles should be placed inside the <head> tags.

{{> scripts }}

This partial renders any script tags specified either by the user (via params.scripts) or by the theme author (specified directly in the template). params.scripts is intended as an escape hatch for users that want to add javascript to their site, but don't want to customize any templates. Scripts should be placed at the end of the <head> block.

TODO: Scripts must currently be given in raw form, whereas styles are just paths/urs.

{{> opengraph }}

This partial willl render the Open Graph meta tags for your page. It should be placed inside the <head> tag. See the Open Graph section for more details.

{{> footer }}

This partial will render content on every page after the main page content. It should be placed at the end of the <body> tag. By default, it displays a simple copyright line with the current year and author's name (configured in params.author.name).

TODO: styles/css?

TODO: comments?

TODO: toc?

TODO: We keep referring to blocks and tags, should probably use consistent language.

DateTimes

TODO: Should this be a subsection of a "Data Types" section?

Dates are strings in one of the following formats:

Format	Time zone
2023-10-15T13:18:50-07:00	America/Los_Angeles
2023-10-15T13:18:50-0700	America/Los_Angeles
2023-10-15T13:18:50Z	Etc/UTC
2023-10-15T13:18:50	Default is local system time
2023-10-15	Default is local system time
15 Oct 2023	Default is local system time

If you want to display a date in a different format, you can use the | format Filter. With no argument, it will default to formatting the date with site.date_format.

Open Graph

TODO: default Template support TODO: Template override support TODO: how to overwrite defaults (in page frontmatter / thor.json)

Zen

The guding principals behind Thor.

Simpler is Better

We are Grug developers. We do everything the "dumb" way first, then optimize the measured bottlenecks.

Zero is Beautiful

The less configuration needed, the better. A site can be built from multiple modules or a single index.md.

On By Default

Users shouldn't have to enable features, unless those features significantly impact performance or mangle regular content.

Fault Tolerant

When possible, mistakes should be recovered with warnings. When fatal errors occur, the user should have all the information they need to fix it quickly.

---

1. While directories can be remapped at the site level, modules must (currently) adhere to the defaults. ↩︎

2. That's not you say you shouldn't use bundles, but if you have no additional resources on your page, there's no benefit to using a bundle. ↩︎

3. Template modification is an "advanced" feature, and shoud probably be discussed later in the page. (or possibly in the guide.) ↩︎

4. Official Triple brace syntax ({{{ raw }}}) is also supported, but {{& raw }} is preferred, as it's easy to accidentily insert too many braces. ↩︎

5. TODO: in what cases won't it? spelllcheck + strict mode? ↩︎

6. (for developers) Template_Context is not the same as Odin's implicit context parameter. ↩︎

7. TODO: Don't use programmer speak. ↩︎

8. TODO: This number must be kept in-sync with MAX_PIPES. ↩︎