HugoBlox Kit: AI-generated pages you keep as Markdown
🧱 Describe your site, AI builds it, you own it as Markdown. Snap together Tailwind blocks like Lego — landing pages, blogs, portfolios, docs & more. No AI slop. Free to deploy anywhere 👇
At a glance
- What is it?
- HugoBlox Kit is an MIT-licensed Hugo theme and block system that turns structured Markdown into landing pages, blogs, portfolios and academic sites, with an optional AI generator for the first draft. It suits people who want static output they can read and edit, and it is a poor fit if you need a database-backed CMS or a visual editor after handoff.
- Who is it for?
- Adopt HugoBlox Kit if you want a static Hugo site whose pages stay readable Markdown after generation, and you are comfortable running Hugo Extended plus Node.js. Skip it if you need server-side rendering, a database, or a drag-and-drop editor that non-technical staff can use without touching files.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 57 days ago.
- What is it written in?
- Mainly HTML, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 28, 2026, and from our analysis. They are not legal advice.
Editorial analysis
The problem HugoBlox Kit is aimed at
AI site generators produce something you cannot maintain. The README makes this the central claim: tools in the Lovable, v0 and Bolt category output React code, while WordPress and Webflow keep your content in a database you cannot export cleanly. HugoBlox Kit takes the opposite position. The AI writes Markdown, and Markdown is the deliverable.
The audience is narrower than the marketing suggests. It is for people who already accept the Hugo model, meaning a build step, a content directory and a static host, and who want a component library on top of it rather than a blank theme. Academic users are the historical core: the README lists publication pages with BibTeX and DOI workflows, Jupyter notebook rendering, LaTeX, team profiles and event pages among the 20+ structured content types. A researcher migrating a CV, a publication list and a personal site into one repository is the clearest fit.
The secondary audience is anyone who wants a portfolio or landing page and is willing to edit front matter. The block system covers hero, features, pricing, testimonials and CTA sections, so a marketing page is assembled from named blocks rather than hand-written HTML.
How the block and module system actually fits together
The repository is a monorepo, and that shapes how you consume it. Alongside the usual theme files there is a modules/ directory, and the release list is scoped to paths inside it: modules/blox/v0.12.0, modules/blox/v0.11.0 and modules/blox-tailwind/v0.9.0. That naming indicates the project ships as Hugo Modules rather than as a single theme you clone. The practical consequence is that blox and blox-tailwind version independently, so a template can pin one without pinning the other.
The front end is not plain Hugo. package.json lists Vite, vite-hugo-plugin and vite-plugin-static-copy, and the vendor:libs script runs a Vite build. The dependencies reveal what the blocks can embed: KaTeX for math, Mermaid and markmap-autoloader for diagrams, Plotly for charts, MapLibre GL for maps, medium-zoom for image zoom, Alpine.js and Preact for interactive pieces. These libraries are vendored into the site by that Vite step rather than loaded from a CDN, which is why a build is required even though the output is static.
Data flow is conventional Hugo: Markdown files with front matter in the content directory, layouts and shortcodes from the modules, assets processed by Hugo Pipes and Vite, and a final static HTML tree. There is no runtime. The README states this directly: no database, no runtime, free hosting.
Installing HugoBlox Kit and generating a first page
The README gives the CLI path as Option B, and it is the one with concrete commands. It states the requirement inline: Hugo Extended and Node.js. The CLI is a global npm package.
npm install -g hugoblox
hugoblox create siteThe first command installs the CLI; the second scaffolds a site. The README does not list the flags hugoblox create site accepts, so expect an interactive prompt rather than a documented set of options. Option A in the README is browser-based: pick a template from the HugoBlox templates page and launch it there, which the README describes as ready in 60 seconds.
Once a site exists, page generation happens in Hugo Chat, a separate hosted service. The README gives this example prompt: "Create a landing page with hero, pricing, and testimonials". According to the README, Hugo Chat emits structured Hugo pages with correct front matter, shortcodes and HugoBlox blocks. You then edit the resulting Markdown by hand.
If you work on the Kit repository itself rather than a generated site, the scripts in package.json are the entry points. The dev script runs scripts/view-starter-dev.sh and dev:stop kills whatever holds port 8081, which tells you the local preview listens there.
pnpm dev
pnpm dev:stopFor linting, the project uses Biome rather than ESLint or Prettier, and the lint script disables the formatter while enabling the linter.
Where HugoBlox Kit stops being the right tool
The AI step is not part of the repository. Hugo Chat is a hosted service at hugo.chat, and the README links to it as an external product. Nothing in the repository makes page generation work offline, and the README does not document what happens to your prompts or whether generation can be run against a self-hosted model. If your constraint is that no content leaves your network, the AI half of the pitch is unavailable to you, and you are left with a Hugo theme and a block library.
There is also a maintenance asymmetry worth naming. The blox module released v0.12.0 on 2026-04-02 and v0.11.0 on 2026-01-02, a quarterly rhythm; blox-tailwind last released v0.9.0 on 2025-10-23. The last push to the repository was on 2026-08-04, so work is ongoing, but the two modules do not move together. A template pinned to an older blox-tailwind will not automatically pick up block changes from a newer blox.
The build chain is heavier than a plain Hugo theme. Vite, a pnpm workspace, Biome and a Poetry-managed Python toolchain all appear in the repository, and the README requires Hugo Extended specifically. If you wanted a theme you drop into an existing site with no Node.js, this is not it. And the README does not document rollback or downgrade procedure for the modules, so pinning a known-good version before an upgrade is on you.
HugoBlox Kit versus a database-backed site builder
The obvious comparison is WordPress or Webflow, and the README frames it as a table: those platforms keep content in a database and require a runtime, while HugoBlox outputs static HTML and Markdown files. That difference is real and it cuts both ways.
With WordPress, a non-technical editor logs in, writes in a browser, and never sees a file. With HugoBlox, the editing surface is the Markdown file or the Ownable CMS extension for VS Code that the README links to. There is no admin panel in the browser. If your team includes people who will not open an editor, this is a hard blocker, not a preference.
The compensating advantage is portability. The README's claim is that the output is "plain Markdown you can read, edit, and own forever", and because Hugo is the renderer, the content survives without the theme. You can move the content directory to another Hugo theme. You cannot move a WordPress database to a different CMS without a migration script.
Against other AI builders, the distinction is the artifact. Lovable and v0 produce application code; HugoBlox produces content files plus a theme dependency. That is less flexible if you want a web app, and more durable if you want a site.
Licence, upgrade cost and what the repository commits to
The project is MIT licensed, stated in package.json, pyproject.toml and the repository metadata. MIT permits commercial use, modification and redistribution provided the copyright notice and permission notice are retained. The README also links a LICENSE.md at the repository root. The bundled front-end libraries are separate packages with their own licences: KaTeX, Mermaid, Plotly, MapLibre GL, Alpine.js and Preact each ship under their own terms, and vendoring them into your build does not relicense them. Check those individually if you redistribute a built site. This is not legal advice.
Upgrade cost is driven by the module split. Because blox and blox-tailwind version separately, upgrading means deciding which of the two you are moving and whether your template's pin still matches. The repository ships tooling for this: scripts/check-template-deps.mjs is exposed as check:template-deps, and scripts/update.py runs under Poetry as update:starters. There is also test:releaser, which runs scripts/test_release_modules.py. Those script names indicate the maintainers test module releases and template dependency consistency, but the README does not describe a supported upgrade path for end users, so treat the release notes for each module as the source of truth.
Python tooling is pinned to ^3.12 in pyproject.toml and the package is declared package-mode = false, meaning it is a management tool for this repository, not a library you install.
Editorial conclusion
Adopt HugoBlox Kit if you want a static Hugo site whose pages stay readable Markdown after generation, and you are comfortable running Hugo Extended plus Node.js. Skip it if you need server-side rendering, a database, or a drag-and-drop editor that non-technical staff can use without touching files. Before committing, check the modules/ directory for the blox and blox-tailwind versions you actually intend to track, and confirm which Hugo Extended version your chosen template pins, since the README does not state one.
Frequently asked questions
What is Hugo used for?
Hugo is the static site generator that renders HugoBlox Kit sites. The README states the output is static HTML with no database and no runtime, and that Markdown files with front matter are the content source.
What are some websites built with Hugo?
The README names NVIDIA Research, MIT and King's College London among the teams using HugoBlox, and lists publication pages with BibTeX and DOI workflows and Jupyter notebook rendering as supported content types.
Is Hugo good for websites?
The README argues the static approach is an advantage: no database, no runtime server, and free hosting on Netlify, Vercel, Cloudflare or any static host. The trade-off it accepts is that editing happens in Markdown files rather than a browser admin panel.
How to use Hugo template?
The README gives two routes: browse a template on the HugoBlox templates page and launch it in the browser, or install the CLI with npm install -g hugoblox and run hugoblox create site. It requires Hugo Extended and Node.js.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/hugoblox-kit)