HugoBlox (listed in this registry as kit) is a free, MIT-licensed static site framework that turns a plain-English description into AI-generated pages while keeping every page as Markdown you own, built for academics, researchers, developers, and small teams who need professional landing pages, portfolios, blogs, publications, and documentation without a database or a paid site builder.

What it is

HugoBlox is an open-source framework for building professional sites from structured Markdown, running on the Hugo static site generator with a Tailwind-based block system. You pick a template or scaffold a site with the CLI, describe the pages you want to Hugo Chat, and the generated output is plain Markdown with correct front matter, shortcodes, and blocks. It ships 20+ structured content types covering landing pages, portfolios, blogs, publications, docs, team profiles, event pages, slide decks, resumes, and notebook or LaTeX content, and everything is pushed to a static host as HTML with no runtime server and no database.

The concrete problem it solves is the trade-off imposed by the two dominant alternatives. AI site builders such as Lovable, v0, and Bolt generate React code that is hard to maintain by hand, and CMS platforms such as WordPress and Webflow lock content inside a database you cannot leave. HugoBlox produces readable Markdown files on a Tailwind and Hugo stack, so a site stays portable, human-editable after generation, and deployable as static HTML on GitHub, Netlify, Vercel, Cloudflare, or any static host.

Key capabilities

• 20+ built-in structured content types with proper front matter, metadata, and layouts, so publications, projects, team pages, and events are first-class rather than freeform posts.
• A Tailwind block system for landing pages, covering hero, features, pricing, testimonials, and call-to-action sections.
• AI page generation through Hugo Chat, which writes structured Hugo pages with the right front matter, shortcodes, and HugoBlox blocks from a plain-English prompt.
• Academic publication pages with BibTeX and DOI citation workflows.
• Searchable documentation with sidebar navigation and versioning.
• Slide decks rendered with reveal.js, plus native rendering of Jupyter .ipynb notebooks and math-heavy LaTeX pages.
• CLI scaffolding with npm install -g hugoblox followed by hugoblox create site, requiring Hugo Extended and Node.js.

Who uses it and how

• Academic researchers build publication pages with BibTeX and DOI workflows alongside team and author profiles carrying bios, avatars, social links, and publication lists.
• Documentation teams run searchable, versioned docs sites on a static host, avoiding a runtime CMS entirely.
• Individuals and small teams launch landing pages, portfolios, and blogs from a template in the browser, then edit the generated Markdown directly.
• Career-focused users produce structured resumes and CVs exportable to PDF from the same content model.
• Adoption spans 150,000+ sites, with teams at NVIDIA Research, MIT, and King's College London named in the README, alongside Meta, Stanford, and NVIDIA among users, and 4.9/5 from an official user survey since 2016.

Getting started

The fastest path is browsing the hosted templates and launching one in the browser, which the README describes as roughly a 60-second start. For full control, install the CLI with npm install -g hugoblox and run hugoblox create site, which requires Hugo Extended and Node.js.

How it compares

Against paid AI site builders such as Lovable, v0, and Bolt, HugoBlox is MIT licensed and open source rather than proprietary, and its output is plain Markdown instead of React code. Against CMS platforms such as WordPress and Webflow, it produces static HTML that runs without a runtime server and keeps content in files you control rather than a database you cannot export. Hosting is free on static providers, removing the recurring platform fee those products charge.

When to use it — and when not to

Choose it when the goal is a content-led site — landing page, blog, portfolio, docs, or publications — that must stay cheap to host and portable across static providers, and when a Markdown-plus-Git workflow suits the team. A self-hoster still runs the build toolchain (Hugo Extended and Node.js), a Git repository, and deploys through a static host, and AI generation depends on the hosted Hugo Chat service rather than a local model. It is not the right pick for database-backed dynamic applications, and readers should weigh the fact that the README reads largely as marketing, which makes it harder to judge operational detail than a sparse or purely technical document would.

# Requires Hugo Extended & Node.js
npm install -g hugoblox
hugoblox create site