Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
Reusable Hugo publishing theme for editorial voice plus structured records, archives, projects, and long-form writing.

Responsive, clean Hugo theme porting Hexo Cactus, with four color schemes, client-side search, Disqus/utterances comments, and 17 languages.

Native Hugo port of Hexo Theme Solitude: elegant, feature-rich blog theme that builds without Node.js.

Hugo theme porting the Linen reading experience from hexo-theme-linen, adding series, image grids, and a Moments stream.

A reading-focused Hugo blog theme with dark mode, i18n, advanced code blocks, KaTeX, Mermaid, and related posts, forked from hugo-theme-ladder.
No Fate is a Hugo theme for publications that pair an editorial voice with structured records, archives, projects, and long-form writing, built as a derivative rewrite of Hugo PaperMod.
No Fate is an open-source static-site theme that runs on Hugo 0.158.0 or later, standard or Extended. It takes Hugo content — typically leaf bundles containing an index.md plus images and source files — and renders it as a semantic HTML site with four page modes: editorial, poster, archive, and record. No Fate uses Hugo-native templates and asset pipelines, so it does not require Node.js, Tailwind, webpack, or any JavaScript framework for building.
editorial for essays and histories, poster for arguments and questions, archive for image-led collections, and record for formal tables and bibliographies; mode selection resolves per page, then section, then params.noFate.defaultMode.clean style is quiet and typographically direct; the alternate wild style adds dense editorial grids, signal-colour blocks, oversized display type, and a worn print surface. Both layers share identical content structure and accessibility behaviour.opening, featured_argument, questions, featured_archive, selected_writing, visual_interruption, current_work, and formal_record modules replaces the conventional blog listing.hooks/head-start.html, hooks/head-end.html, and hooks/body-end.html are stable partials to override from the downstream site; assets/css/extended/ loads after the theme styles.Independent journals and small editorial organisations can use No Fate to publish essays, questions, and archival records under a single content model. Researchers and curators building image-led histories benefit from the archive mode and the record mode for bibliographies and formal indexes. Writers and designers who want a portfolio with long-form notes and project archives get a static site without maintaining a JavaScript toolchain.
visual.mode: archive and visual.hero_alt, and let the theme generate responsive images via the Hugo image pipeline.params.noFate.wild for a print-like identity.The repository supports two install paths. With Hugo Modules, a downstream site adds github.com/OliverObst/no-fate to its import graph and pins a semantic version tag; before the first release, evaluators can pin an exact commit SHA. Alternatively, a Git submodule can be added at themes/no-fate and checked out to a release tag. The README recommends pinning a tag and overriding templates rather than editing the theme files.
No Fate is free to use and is distributed under the MIT license. Upstream PaperMod copyright notices remain in the LICENSE file, and UPSTREAM.md records the exact source revision and update policy.
Yes, No Fate is distributed under the MIT license, so it is free to use and modify. Upstream PaperMod copyright notices remain in the LICENSE file, and UPSTREAM.md records the exact source revision.
No Fate requires Hugo 0.158.0 or later; both standard and Extended versions are supported. The CI build matrix tests standard Hugo at that minimum plus the current supported release.
No. Building a site with No Fate uses only Hugo-native templates and asset pipelines. Node.js and Playwright are needed only if you run the repository's optional automated quality-testing suite.