Docsy

Docsy is an Apache-2.0-licensed Hugo theme for technical documentation sets, providing simple navigation, site structure, and reusable page components for docs-heavy websites. It is a community-maintained project (not an officially supported Google product) that ships as an npm package named @docsy/theme and integrates directly into a Hugo site as a theme, npm dependency, Hugo module, or Git submodule.

What is Docsy?

Docsy is a Hugo theme purpose-built for technical documentation sites, so a Hugo content tree of Markdown pages is rendered into a documentation website with built-in navigation and site structure. Docsy does not generate content itself — you supply Markdown pages and configuration, and Hugo plus the theme compiles them into HTML and CSS. It is maintained as an open-source project under the Google GitHub organization, distributed via npm as @docsy/theme, and documented on its own Netlify-hosted user guide at docsy.dev.

What makes Docsy stand out?

• Hugo-native theme — works with the Hugo static site generator, so existing Hugo content and config carry over rather than requiring a new framework or content format.
• Extended Hugo and Dart Sass required — the build expects a recent extended release of Hugo and the Dart Sass compiler, which Hugo looks up as the sass CLI on the system PATH.
• PostCSS-based CSS pipeline — creating final CSS assets requires autoprefixer and postcss-cli; with postcss-cli version 8 and later you must also install postcss separately.
• Multiple installation paths — Docsy can be added as an npm package, as a Hugo module (recommended, and the one that also requires Go), as a Git submodule, or by cloning the theme into the project.
• Ready-made example project — the google/docsy-example repository hosts a pre-configured basic site (live at example.docsy.dev) that can be customized into your own documentation site.
• Self-hosted user guide — the Docsy documentation is itself built with Docsy and is served from Netlify at docsy.dev, with deploy logs and a main deploy preview available in the Netlify dashboard.
• Cross-platform npm scripts — repository npm scripts run under Bash on every platform via a script-shell pin in .npmrc, which on Windows means Git Bash's bash must be on the PATH.
• Apache License 2.0 — permissive licensing with a code of conduct and a CONTRIBUTING.md process for pull requests.

Who should use Docsy?

• Open-source maintainers documenting a project in Markdown who want navigation, sidebar structure, and search-friendly page layout without building a docs front end from scratch.
• Technical writers and developer-experience teams migrating an existing Hugo site to a docs-oriented theme while keeping their current content files.
• Platform or API teams that need a multi-section documentation set — guides, references, and tutorials — organized by Hugo's content structure.
• Teams already invested in JavaScript tooling who want to install a docs theme through npm and control the CSS output through PostCSS autoprefixing.

How does Docsy work?

After installing the prerequisites, you add Docsy to a Hugo site by cloning or forking the example project, or by adding it as npm package, Hugo module, Git submodule, or cloned theme. Hugo then builds the Markdown content with the theme's layouts and runs the Sass and PostCSS steps that emit the final CSS assets. To build the Docsy user guide locally you clone the repo and run npm run install:safe followed by npm run serve.

Pricing

Docsy is free and open source, licensed under the Apache License 2.0; there are no paid tiers described on the project page.

Alternatives

• Docusaurus — a React-based documentation framework rather than a Hugo theme, so content and build tooling differ from a Hugo setup.
• MkDocs Material — a theme for the Python-based MkDocs static site generator, an alternative if the site pipeline is Python rather than Hugo's Go-based toolchain.

FAQ

Is Docsy free to use?

Yes. Docsy is released under the Apache License 2.0, which permits commercial and private use alongside modification and redistribution. The theme is published on npm as @docsy/theme, and the license text lives in the project's LICENSE file.

Is Docsy an officially supported Google product?

The project page states that Docsy is not an officially supported Google product, though it is actively maintained. The main branch is explicitly marked as under development and unsupported — for supported use you should rely on the tagged Docsy releases.

What are the prerequisites for building a Docsy site?

You need a recent extended release of Hugo, the Dart Sass compiler available as the sass CLI on the PATH, and PostCSS tooling installed through npm (autoprefixer and postcss-cli, plus postcss for postcss-cli 8 or newer). The recommended Hugo module installation also requires Go.

Can I add Docsy to an existing Hugo site?

Yes. Besides using the example project as a starting template, Docsy can be added to an existing Hugo site as an npm package, a Hugo module, or a Git submodule, or by cloning the theme into the project. The Get started guides on docsy.dev cover each option.