Project Documentation with Hexo Static Site Generator

By Bruno Mota

This article was peer reviewed by Panayiotis Velisarakos, Dan Prince and Julian Motz. Thanks to all of SitePoint’s peer reviewers for making SitePoint content the best it can be!

When starting an open source project, one of the most important things is to create project documentation. Documentation is essential if we want our project to be used by others, and it can be done in many ways:

  • GitHub Wiki – GitHub lets us make a wiki associated with each project. It is composed of pages written with markdown and is definitely a tool to take into consideration to build documentation. However, it does have a few limitations: contributions to a wiki don’t appear in the project contributions; is limited to a strict structure and layout; you must host assets in other locations.
  • README – we can create a, which will show on the GitHub project page. It might be a good solution if the documentation will be very short, otherwise it gets a big one page full of information. Usually this serves to introduce the project and not to show documentation.
  • Self Hosted – we can create a custom site for our documentation. This gives us total freedom to create what we want, but it prevents possible contributions to our documentation. It also comes with the price of hosting.
  • GitHub Pages – GitHub also provides a way of hosting a static site for each project. By creating a branch called gh-pages in your project’s repo, GitHub will publish its contents as a website. This is great to place a documentation site, although, maintaining documentation in a separate branch is not optimal: documentation files get hard to find for contributors and contributions won’t show up in the master branch.

Fortunately, there’s a way of combining the best parts of the options above.

Introducing Hexo

Hexo is a static site generator built with Node.js. It is mostly used as a blog framework, but it has a deploy integration for GitHub which makes it a great fit to build a documentation site for a GitHub project.

With Hexo, we can create markdown files and HTML layouts which will be converted to static HTML files when deployed. Hexo provides a deploy configuration which builds our static files into a GitHub branch. This means we can maintain our documentation as markdown in our project’s master branch and deploy it, with one command, to gh-pages.

Installing Hexo

Hexo is built with Node.js, so to install and use it we’ll need Node.js installed in our system. We’ll also need Git which will be used by Hexo to deploy our documentation site to gh-pages.

Installing Node.js

To install Node I recommend using a version manager, such as nvm. There are other version managers out there that you can use, but they all make life easier when it comes to installing and switching between Node.js versions.

Using nvm, let’s run the following:

nvm install 4

This will install the most recent release of Node.js 4.x, which also comes with npm ready to use.

Installing Git

We’ll also need Git installed in our system. If you’re not sure you already have it, run the following:

git --version

If the result is a Git version you can skip this section. If instead you see an error, you’ll have to install it first.


On a windows system we can run an installer provided by Git.


On OS X, we can install it in one of three different ways:

  • Using the installer.
  • Using Homebrew by running brew install git.
  • Using MacPorts by running sudo port install git +doc +bash_completion +gitweb.

Usually, I prefer using Homebrew to install this type of software, but if you’re more familiar with MacPorts or just want to use the installer, there’s nothing wrong with that.

Linux – Ubuntu or Debian

On an Ubuntu or Debian-based system we can install Git with apt:

sudo apt-get install git-core

Linux – Fedora, Red Hat or CentOS

On a Fedora, Red Hat or CentOS system we can install Git with yum:

sudo yum install git-core

Installing Hexo CLI

After installing Node.js and Git we can now finally install Hexo by running:

npm install -g hexo-cli

To make sure everything is set up, type the following:

hexo --version

If you see a list of versions, good news: you have everything ready to use Hexo!

Setting Up

Now that we have Hexo installed, we can now start to create our documentation on our GitHub master branch. To follow this article, you can either:

  • Create the documentation for one of your existing GitHub projects
  • Create a new repo here

For simplicity, I’ll assume you’re creating a new project called hexo-documentation, but you can follow the article with an existing one.

Let’s clone the GitHub repo locally by running:

git clone

Replace USERNAME with your username and REPOSITORY with the name you gave to your repo. In my case, the command would be:

git clone

Now let’s cd into it and create a folder called docs:

cd hexo-documentation
mkdir docs

The docs folder is where our documentation site will be, and it’s where we’ll initialize Hexo by running:

hexo init docs

What the command above does is add a bunch of Hexo’s configuration and dependency settings. But we still need to install those dependencies, which are defined in a package.json file inside the docs folder. To do so, let’s run the following:

cd docs
npm install

If no error occurred we now have Hexo’s dependencies installed, as well as the following structure inside our docs folder:

  • _config.yml – our site configuration data.
  • package.json – Node.js dependencies.
  • scaffolds – used for blog posts (in this article we won’t be covering the Hexo blogging feature).
  • source – where we’ll put our markdown files, as well as anything that we want to be public such as images.
  • themes – where the theme we’re using is placed.

We can already check our site running by executing:

hexo generate
hexo server

The first command will generate our static site from our source files, using the selected theme. The second one will start a server that provides those static files. We can now visit http://localhost:4000/, which will show something like the following:

Hexo initial state

At the moment it looks more like a blog than a documentation site, but we’ll get to that.

Creating a Theme

To change the current look of the site, we’ll need to create a Hexo theme. A theme defines the looks and layout of your site. There are a lot of themes created for Hexo that you can use for free. In this article though, we’ll create a simple one from scratch.

Hexo comes with a theme by default, you can see it inside the docs/themes folder. You can have multiple themes there, but only one can be active at a time. So, let’s create our own. Inside the themes folder let’s create a directory for our theme. Let’s name it ‘documentation’.

Now, a Hexo theme should have the following structure:

  • _config.yml – extra configuration for the theme.
  • languages – internationalization support (i18n).
  • layout – the theme layouts (that will give structure to the pages).
  • scripts – the place to put plugin scripts for Hexo.
  • source – any assets placed here will be processed by Hexo and put as public. Files starting with _ (underscore) are ignored.

We’ll create a simple and static theme, so we won’t need the scripts folder. And we’ll write in English only, so we can discard the languages folder as well.

What we’ll do is create a layout for our pages, and some CSS to put everything in order. We’ll use Sass to generate the CSS so we can define some variables and divide our CSS into modules. Hexo can’t process Sass on its own, but fortunately there’s a plugin for it, hexo-renderer-sass, and we can install it with npm.

So with the terminal at ./docs(note it’s not inside the theme), let’s run:

npm install --save hexo-renderer-sass

Now, back to the theme. Let’s configure Sass, otherwise it won’t be used. So in the docs/themes/documentation/_config.yml let’s add the following:

  outputStyle: nested
  precision: 4
  sourceComments: false

You can see a full list of available configuration properties for Sass here.

Great! Now we can start using Sass. We won’t go into detail about the writing of the Sass styles, as it is not relevant to the article’s scope and it is quite extensive. In any case, you can find them here, and you can copy these files into your project or create your own styles.

Let’s move on to the layout. This is the most important piece when building a theme. It defines the layout of your pages with a template language. Although you can use others, by default, Hexo provides Swig as the template engine, and that’s what we’ll use. So, let’s create a file docs/themes/documentation/layout/default.swig with:

<!DOCTYPE html>
  <meta charSet='utf-8' />
  <title>{{config.title + ' - ' + page.title}}</title>
  <link href='' rel='stylesheet' type='text/css'>
  <link href=',600,300,700' rel='stylesheet' type='text/css'>
  <link href='{{ url_for("css/docs.css") }}' rel='stylesheet'>
  <div class='menu'>
    <div class='logo'>
    <nav class='menu-nav'>
      {% for section in %}
        <ul class='nav'>
          <span>{{ section.title }}</span>
          <ul class='nav'>
            {% for item in section.items %}
                <a href='{{item.href || url_for( + ".html") }}'{% if == %} class='active'{% endif %}>{{item.title}}</a>
            {% endfor %}
      {% endfor %}
    <a class='footer' href=''>
      Project on github
  <div class='page'>
    <div class='page-content'>
  <div class='switch-page'>
    {% if page.prev %}
      <a class='previous' href='{{ url_for(page.prev) }}'>Previous</a>
    {% endif %}
    {% if %}
      <a class='next' href='{{ url_for( }}'>Next</a>
    {% endif %}

Let’s break this down to see what we’re doing here.

  <meta charSet='utf-8' />
  <title>{{config.title + ' - ' + page.title}}</title>
  <link href='' rel='stylesheet' type='text/css'>
  <link href=',600,300,700' rel='stylesheet' type='text/css'>
  <link href='{{ url_for("css/docs.css") }}' rel='stylesheet'>

In the header we’re setting up:

  • a titleHexo provides variables that we can use to build a smart title. In our case, we’re concatenating the site’s title, set in the configuration file, and the page title, defined in each page.
  • links – we’re including: the normalize CSS stylesheet, so that our site’s base styles are consistent across browsers; Open Sans font family from Google Fonts, to give a better look to the text; and finally our created styles generated from the Sass files. Note that for this last one we’re calling a Hexo helper function url_for, since we don’t know where the site will be located. What this does is basically to concatenate the root URL with the URL passed through as an argument.

Next follows the body. It is mostly normal HTML except some parts that I’ll explain in more detail.

{% for section in %}
  <ul class='nav'>
    <span>{{ section.title }}</span>
    <ul class='nav'>
      {% for item in section.items %}
          <a href='{{item.href || url_for( + ".html") }}'{% if == %} class='active'{% endif %}>{{item.title}}</a>
      {% endfor %}
{% endfor %}

This is what generates our menu. It is iterating through a structure,, that we’ll setup later on in our site’s _data folder. It expects each item in to be have a title and an items array which contains the actual navigation links. It loops through those items and generates the link for each one.

The next important part we’re setting up in this file is the content area:

<div class='page-content'>

Here we’re including the current page title, followed by the page’s content. In our case the page content here will be the resulting HTML generated from the markdown files we’ll write.

Finally, as more of an extra, we’re including a previous and next page buttons:

{% if page.prev %}
  <a class='previous' href='{{ url_for(page.prev) }}'>Previous</a>
{% endif %}
{% if %}
  <a class='next' href='{{ url_for( }}'>Next</a>
{% endif %}

In the code above we’re assuming each page should have a prev and a next property where applicable. And we’ll see later how we define that. This renders a link depending on whether each one is available or not.

And that’s it! Not only for our layout file, but for our theme as well. The final missing piece is changing the actual theme you want Hexo to use for your site. To do this, in docs/_config.yml you need to change the theme property to:

theme: documentation

All done! We can now head on to actually creating our content.

Creating Content

Now we have reached the most important part of the process, the creation of the actual documentation for our project. For this we’ll be working in the docs/source folder. This is where all pages will go, as well as our menu data structure.

Let’s start with the menu data. Hexo provides a way for us to define data structures which will be available in For this, inside docs/source, let’s create a new folder called _data. Hexo will go through this folder if it exists and process the supported files in it into the variable, namespaced by file name.

Since our theme is looking to find our menu data in, we’ll create a nav.yml file. Let’s put the following content in it:

- title: Introduction
  - id: index
    title: What is it
  - id: how-it-works
    title: How it works
- title: Usage
  - id: installation
    title: Installation
  - id: using
    title: Using It

Here we’re including two sections with two pages in each. And that’s it, our menu is all setup. We just need to create the pages now. Since we’re going to write them in markdown, let’s create the following files:


Now let’s put some content in them. The first thing to do when creating a new content file is writing the front-matter which is where you define your page’s settings. This is a block prefixed and suffixed by three dashes and usually written in YAML format.

Let’s start from the file then.

layout: default
id: index
title: What is it?
next: how-it-works.html

This is our index markdown file

- one
- two
- three

We’re setting four values in this page’s front-matter:

  • layout – the layout to use for this page.
  • id – unique identificator of the page.
  • title – the page title, will be available in page.title.
  • next – variable indicating the next page.

We follow the settings with some markdown content. When the site is built, this content will be converted to HTML and put into a static HTML file using the layout we created earlier for our theme.

The other files follow the exact same rules, so we won’t go through them here.

We can now check our site by running:

hexo generate
hexo server

When visiting http://localhost:4000/, it should look like the following image, if you included the styles:

Hexo article final stage of the page

Deploying to GitHub Pages

Now that we have our documentation site all done, we need to be able to deploy it to GitHub pages. If we were doing this manually, we’d have to create a gh-pages branch, generate our Hexo site locally, copy paste the resulting static files into our gh-pages local working copy branch, commit and push it, only to realize we had a typo so we needed to do this all over again.

Fortunately, Hexo provides a much better way to deploy to gh-pages. For this we’ll need the hexo-deployer-git package, which we can install by running the following command in docs/:

npm install --save hexo-deployer-git

All we have to do now is set the configuration in the docs/_config.yml file. Let’s open it and head to the deployment section, which should be all the way at the bottom, and add the following:

  type: git
  branch: gh-pages
  message: "Docs updated: {{ now('YYYY-MM-DD HH:mm:ss') }})"

And that’s it! Before deploying, let’s change some final configurations for the site as well:

# Site
title: Hexo documentation
subtitle: Hexo documentation article
description: Hexo documentation article
author: Bruno Mota
language: en
timezone: GMT

root: /hexo-documentation/

Great, so all that is left to do is to actually deploy! In the terminal, run the following:

hexo generate
hexo deploy

Hexo will now deploy the generated output to the gh-pages branch for us. After it is complete, we can visit the resulting site at


Documentation is essential if you want your work to be used by others. There are simple ways of creating project documentation on GitHub but they don’t always facilitate the best results. For medium to large projects it is often necessary to have a documentation site to hold all the information. Hexo not only enables this but also provides a quick setup and deploy process that makes this framework a great tool for the job. Thanks, Tommy Chen for the superb work on Hexo!

Let me know in the comments if you’ve decided to give Hexo a try, I’d love to hear how you get on!

  • Cool!

  • Emanuel Quimper

    Nice articles thank for all this tips. Do you have a idea about how can I just have a plain html file inside a section. I mean I want my resume who are in plain html to be in my Resume section.

    • Emanuel Quimper

      Oh I find just need to change the name for index and put in inside resume folder in the public dir. Sorry

      • Bruno

        Yes it’s that simple :-) Cheers!

  • Stevie

    thank you for this. i have always wanted to use a static site generator, was using pelican before, same principle. i get a blank screen when following these steps, any idea why this is happening maybe?

    • Stevie

      ok i found something, renamed the default.swig file to index.swig, its displaying now but stylesheet not showing and links not working, obviously because its referenced in md files to the specific pages. so just to confirm, is default.swig the correct page, did i maybe miss something?

  • dden

    Nice article but cant get it to work when I launch the server as I try to follow step by step. A white screen and getting on the terminal:WARN No Layout: index.html.
    Any hint please,

Get the latest in JavaScript, once a week, for free.