Content management

Organize content in sections and bundles, describe it with front matter, link it, translate it, and enrich it with images, shortcodes, math and diagrams.

In fugo’s content model, the content directory is a tree of pages, each a Markdown or HTML file with front matter, and the tree decides the site’s sections and URLs.

• Content organization How the content directory becomes pages, sections and URLs, and how page bundles keep a page together with its images and files.
• Front matter The metadata at the top of a content file — title, dates, draft status, weight, URLs, menus, parameters — in YAML, TOML or JSON.
• Page resources The images and files of a page bundle — list them, find them by name or pattern, give them titles and parameters, and process them.
• Image processing Resize, crop and fill images, convert their format, apply filters, overlay text, read EXIF data and make QR codes — all built into fugo.
• Sections Group pages into sections and nested sections, and navigate the section tree in templates.
• Taxonomies Classify content with tags, categories or your own taxonomies, and list terms and their pages.
• Menus Define menus in the configuration or in front matter, nest entries, and render them with the current page highlighted.
• Summaries The short version of a page for lists and feeds — automatic, marked with a divider, or written in front matter.
• URLs How page URLs are formed, how to change them with slugs, URLs and permalink patterns, and how to redirect old URLs with aliases.
• Links and cross references Link to other pages by their content path, so links survive URL changes, and find broken links at build time.
• Markdown The Markdown fugo renders — CommonMark with GitHub's extensions, attributes, alerts, definition lists and more — and how to configure it.
• Shortcodes Call templates from content with shortcodes, use fugo's embedded shortcodes for figures, videos, posts and QR codes, and write your own.
• Syntax highlighting Highlight code blocks at build time with fugo's port of Chroma, with line numbers, highlighted lines and inline styles or CSS classes.
• Diagrams Draw ASCII diagrams that fugo turns into SVG at build time, or render Mermaid diagrams in the browser with a code block render hook.
• Mathematics Write LaTeX in Markdown and render it to MathML at build time with KaTeX, or in the browser.
• Multilingual sites Publish a site in several languages, link translations, translate strings with i18n files, and serve languages from one host or several.
• Data sources Use data files, remote JSON and CSV, and resources as data in templates, and turn data into pages with content adapters.
• Content adapters Create pages and page resources from data — files, remote APIs, generated reference — with a template in the content directory.
• Build options Keep pages out of lists, render pages without publishing them, and control what is published with the build front matter.
• Related content List pages related to the current one by keywords, tags, dates or headings, with configurable indices and weights.
• Editing in the browser Give people an editor at /admin/ — they sign in with Google or another account, edit pages, translations and images, save drafts and publish them — without access to the git repository.