Support Center & Knowledge base

Managing Sub Folders & Repositories

The content folder is the base for all the content that is created for the documentation solution. The actual contents are pulled from the linked-to repositories as defined in repositories.json. It’s also possible to build out a helper structure to aid with the linking and grouping of documentation across repositories.


Defining folder hierarchy

To add structure (sub-folders) to the content folder and make these visible, hugo expects an available with a front-matter section that defines the title, description, keywords & relative weighting in its parent tree.

Note! Only use lower cased folder names.

title: Page Title
description: A short description of the pages contents
keywords: comma, separated, keywords, to, help, searching
author: authorname
weight: 2

Making structure deployable

By default the contents folder is ignored in the .gitignore file. This is to avoid including symlinks into the repository. You have to manually add your newly added to git.

Manually add markdown files in content folder

Run the following command from the Source/Hugo folder. Replace with your relevant path

git add content/path/to/ -f

Unignore markdown files in .dockerignore

If the supporting folder structure isn’t in place, the cloning and linking of repositories will fail in the dockerizing process. To avoid this, make sure to explicitly mark the relevant markdown or other static content file as included in .dockerignore

Example of including a sub-folder called tools and its index


Content from other repositories

When linking to a repository for the first time, make sure the Documentation folder exists, otherwise the symlink will fail, and the solution won’t pick up any documentation changes from that repository. Redeploy when the folder exists.

To link to documentation from another repository, add that repository to the repositories.json file located in Source/Hugo . The repository should have a folder named Documentationat its root with its documentation written in markdown.

Example of repositories.json

    "": {
        "name": "guidelines",
        "path": "contributing/where_to_start"
    "": {
        "name": "getting started",
        "path": ""
Parameter Description
name Name of the folder that will be linked to
path Path under content it will be placed

The build.js task iterates over repositories defined in the repositories.json file, and gives them a matching name, and places the link in the relevant sub-folder in the content folder.

The above repositories.json will generate the following output. Note the files should already be in the content folder:

|---getting started [linked to home/Documentation]
        |---guidelines [linked to learning/Documentation]