How juicer works — content, layouts, partials, shortcodes, themes.
Juicer borrows its mental model from Hugo: a tree of markdown content, a tree of HTML templates, and a small set of conventions that bind them together. Read this section once and you’ll understand the rest of the docs without effort.
Pages
Content files— Markdown files with YAML frontmatter — the source of truth for every page.
Templates— How squiggly templates render content into HTML.
Themes— Drop-in skins that ship layouts, partials, shortcodes, and static assets.
Theme inheritance— How a theme pulls in other themes via theme.toml, and how the full lookup chain is resolved.
Blogging features— Tags, categories, pagination, dates, reading time — the cluster of features that turn a juicer site into a blog.
Shortcodes— Markdown-embeddable templates for callouts, tabs, embeds, and more.
Markdown— Every markdown extension juicer turns on, with examples.
Internationalization (i18n)— Publish a site in more than one language — language-prefixed URLs, per-language navigation, translated UI strings, and automatic hreflang.
