Local Setup for Documentation Work

In order to contribute to the Documentation efforts, you can edit pages directly on Github. But if you want a more powerful setup for a better work experience, you can choose to set up a local copy of the files, install our build engine Hugo, and build and serve the site locally.

This is an advanced way of editing the Documentation, it should only be used by people with the necessary technical skills and who want to work on this Documentation extensively.

Install necessary software on your computer

We need to be running the following packages:

  • Git (for source-control)

  • Asciidoctor (to handle Asciidoc mark-up)

  • Hugo (static-site engine)

The following instructions are specific to Ubuntu 64-bit, but should be easy to adapt to other Linuxes and MacOS. A Windows installation is also possible. See the links at the bottom of this article for specific instructions for other environments.

sudo apt-get update

sudo apt-get install git

Here’s a handy command to download the latest Hugo release automatically:

wget https://github.com`wget -qO- https://github.com/gohugoio/hugo/releases/latest | grep -oE -m 1 '\/gohugoio\/hugo\/releases\/download\/v[0-9]+.[0-9]+.[0-9]*\/hugo_[0-9]+.[0-9]+.[0-9]*_Linux-64bit.deb'`

In case that doesn’t work, the point is to get a command similar to this, replace the 0.53 with the latest version: wget https://github.com/gohugoio/hugo/releases/download/v0.53/hugo_0.53_Linux-64bit.deb

Now install the newly downloaded package, if it’s the only one in the current directory you can do it with:

sudo dpkg -i hugo*.deb

Now check Hugo is operational with

hugo version

Go to some appropriate directory, and use this command to create the SuiteDocs subtree and download everything:

cd SuiteDocs

bundle install

That should pick up the local Gemfile asking for the "asciidoctor" package and install it. Check with:

asciidoctor --version

Start running your local version of the site

You’re ready to go! To build the site you can simply type


But you won’t be using that very often because it’s enough to launch the local web server, and any outstanding changes will get rebuilt:

hugo server --bind= --baseUrl= --navigateToChanged --enableGitInfo

Change that into whatever is your local IP address.

This will be the URL you put in your browser to navigate the local website.

While doing your work on content, we recommend keeping a second terminal window always running the server, so you can check any error messages, and see the server picking up your edits automatically and redeploying.


Apart from the advantages of collaborating on content via GitHub, this local setup lets you use the full power of Linux over your content, to grep it, bash it, php it…​ mass operations are quick and easy.

The fast, automatic redeployments, complete with automatic browser navigation to changed content, are extremely convenient while editing content.

Finally, the entire site is up for editing - not just textual content but also visual aspects, features, etc. Your contribution can be a new site feature coded in Golang.

Content is available under GNU Free Documentation License 1.3 or later unless otherwise noted.