Other setup options
If Docsy as a Hugo Module doesn’t suit your site – for example, if you don’t want to install Go – choose from these setup options:
Prerequisites
Install Hugo
You need a
recent extended version
(version 0.160.1 or later) of Hugo
to do local builds and previews of sites (like this one) that use Docsy. If you
install from the release page, make sure to get the extended Hugo version,
which supports
SCSS; you
may need to scroll down the list of releases to see it.
For the tool versions that Docsy officially supports, see Official support. For comprehensive Hugo documentation, see gohugo.io.
On Linux
If you’ve already installed Hugo, check your version:
hugo version
If the result is earlier than 0.160.1, or if you don’t
see Extended, you’ll need to install the latest version. You can see a
complete list of Linux installation options in
Install Hugo. The following shows you
how to install Hugo from the release page:
Go to the Hugo releases page.
In the most recent release, scroll down until you find a list of Extended versions.
Download the latest extended version.
Create a new directory:
mkdir hugoExtract the files you downloaded to
hugo.Switch to your new directory:
cd hugoInstall Hugo:
sudo install hugo /usr/bin
On macOS
Install Hugo using Brew.
Hugo-extended NPM package
You can install Hugo as an NPM module using hugo-extended:
npm install hugo-extended --save-dev
Node: Get the latest LTS release
If you have Node installed already, check your version of Node. For example:
node -v
Install or upgrade your version of Node to the active LTS release. We recommend using nvm to manage your Node installation (Linux command shown):
nvm install --lts
Install PostCSS (optional)
See Install PostCSS.
Option 1: Docsy as a Git submodule
If you are using Docsy as a Git submodule but would like to migrate to Hugo Modules, see our migration guide.
For a new site
To create a new site and add the Docsy theme as a Git submodule, run the following commands:
Create the site:
hugo new site myproject cd myproject git initFollow the instructions below for an existing site.
For an existing site
To add the Docsy theme to an existing site, run the following commands from your project’s root directory:
Install Docsy as a Git submodule:
git submodule add https://github.com/google/docsy.git themes/docsy cd themes/docsy git checkout v0.16.0To work from the development version of Docsy (not recommended), run the following command instead:
git submodule add --depth 1 https://github.com/google/docsy.git themes/docsyAdd Docsy as a theme, for example:
echo 'theme: docsy/theme' >> hugo.yamlGet Docsy dependencies:
(cd themes/docsy && npm run postinstall)NoteRun
npm run postinstall, notnpm install:postinstallinstalls only the theme’s runtime dependencies; a plainnpm installinsidethemes/docsy/also pulls the repository’s maintainer workspaces, an install more than an order of magnitude larger.(Optional but recommended) To avoid having to repeat the previous step every time you update Docsy, consider adding NPM scripts like the following to your project’s
package.jsonfile:{ "...": "...", "scripts": { "get:submodule": "git submodule update --init --depth 1", "_prepare:docsy": "cd themes/docsy && npm run postinstall", "prepare": "npm run get:submodule && npm run _prepare:docsy", "...": "..." }, "...": "..." }Every time you run
npm installfrom your project root, thepreparescript will fetch the latest version of Docsy and its dependencies.
From this point on, build and serve your site using the usual Hugo commands, for example:
hugo serve
Option 2: Clone the Docsy theme
If you don’t want to use submodules (for example, if you want to customize and
maintain your own copy of the theme directly, or your deployment choice requires
you to include a copy of the theme in your repository), you can clone the theme
into your project’s themes subdirectory.
To clone Docsy at v0.16.0 into your project’s themes
folder, run the following commands from your project’s root directory:
cd themes
git clone -b v0.16.0 https://github.com/google/docsy
cd docsy
npm run postinstall
As with the submodule option, set
theme: docsy/theme in your site configuration. The note above about
npm run postinstall versus npm install applies here as well.
To work from the development version of Docsy (not recommended unless, for
example, you plan to upstream changes to Docsy), omit the
-b v0.16.0 argument from the clone command above.
Then consider setting up an NPM prepare script, as documented in Option 1.
For more information, see Theme Components on the Hugo site.
Option 3: Docsy as an NPM package
Docsy is published to the npm registry as @docsy/theme. To create a new
site that uses the Docsy NPM package:
Create your site:
hugo new site --format yaml myproject cd myprojectInstall Docsy:
npm init -y npm install --save-dev @docsy/themeHugo install tipTo also install Hugo as an NPM package, see Hugo-extended NPM package.
Add Docsy as your site’s theme by including the following in your project’s
hugo.yaml:theme: '@docsy/theme' themesDir: node_modulesBuild or serve your new site using the usual Hugo commands. For example, build your site as follows:
$ hugo Start building sites … ...
To update Docsy later, see Update your Docsy NPM package.
Development versions of Docsy
Use only official Docsy releases in production. For Docsy development or testing, you can also install:
A pre-release, when one is available, through the
nextdist-tag:npm install --save-dev @docsy/theme@nextDocsy directly from GitHub:
npm install --save-dev google/docsyThis installs the repository’s default branch (
main). To pin a tagged version:npm install --save-dev google/docsy#semver:v0.16.0For other revision selectors, see npm install. The GitHub package is named
docsyand contains the theme files in a subfolder, so with this install form usetheme: docsy/themein your site configuration.
Preview your site
To preview your site locally:
cd myproject
hugo server
By default, your site will be available at http://localhost:1313. For common issues, see Troubleshooting.
You may get Hugo errors for missing parameters and values when you try to build your site. This is usually because you’re missing default values for some configuration settings that Docsy uses - once you add them your site should build correctly. You can find out how to add configuration in Basic site configuration - we recommend copying the example site configuration even if you’re creating a site from scratch as it provides defaults for many required configuration parameters.
What’s next?
- Add some basic site configuration
- Add content and customize your site
- Get some ideas from our Example Site and other Examples and templates.
- Publish your site.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.