Support Center & Knowledge base

Getting started

Writing documentation can be done by just working on each repository individually or you can work with the documentation engine and see the end result while working. This is a good idea to get a feeling for how it will look like and verify that links, images and diagrams are correct.

You’ll have to start by cloning the Documentation repository, which has sub modules:

$ git clone --recursive

If you’ve already cloned it, you can get the submodules by doing the following:

$ git submodule update --init --recursive

Creating Documentation from the working repository

At the root of the working repository, create a Documentation folder with at least a matching and other markdown files if needed.

Adding the working repository as a submodule

In the Documentation repository, navigate to the Source/repositories/ folder and then in the corresponding Organisation folder (e.g. fundamentals, runtime, interaction etc.). You can here pull your working repository as a submodule:

$ git submodule add <repository_url> <repository_name>

_Repositoryname has to be in lower case only


$ git submodule add dotnet.fundamentals

Linking to repositories

The system is relying on all content sitting in the content folder:

The content folder should contain the parent folders, with a matching and the contents of the Documentation folder from the repository directly in this. This is best achieved by creating a symbolic link to the repositories Documentation folder.

<Documentation root>
└── Source
    └── content
        └── fundamentals
        └── runtimes
        └── ...

Open a shell and navigate to the correct sub-folder in the content folder and then in the corresponding organisation folder.


$ ln -s ../../repositories/<organisation-folder>/<repository>/Documentation <folder-name>


c:> mklink /d <folder-name> ..\..\repositories\<organisation-folder>\<repository>\Documentation



$ ln -s ../../repositories/runtime/Runtime/Documentation runtime


c:> mklink /d runtime c:\Projects\Dolittle\Documentation\Source\repositories\runtime\Runtime\Documentation

Chances are you are contributing to the code of the repository and you can therefor leave it in place and maintain code and documentation side-by-side.

All folder names given in this process will act as URL segments, be very carefull to change these after they have been deployed.

Keep main Documentation syncronized with the working repository

An Azure pipeline has been set up to allow to keep the Documentation repository up to date automatically when a modification is made in the documentation inside the working repository.

To use that from a working repository, a simple pipeline is needed to call the Documentation update.

azure-pipeline.yml :

    - master

        - repository: templates
          type: github
          name: dolittle-tools/AzureDevOps
          endpoint: dolittle-tools

    - template: Source/Documentation/documentation.yml@templates

You can use another template if needed but Source/Documentation/documentation.yml has to be triggered.

Building and running locally

Install dependencies

You need to install node dependencies in the Source/Hugo folder. You can do this through using npm or yarn.


$ npm install


$ yarn

Install Hugo

You will need to install Hugo. Once you have Hugo installed, you open a shell and navigate to the Source/Hugo folder. From this you simply do:


$ hugo server


c:> hugo server

This should then yield something like the following:

                   | EN
  Pages            | 191
  Paginator pages  |   0
  Non-page files   |  32
  Static files     | 209
  Processed images |   0
  Aliases          |   2
  Sitemaps         |   1
  Cleaned          |   0

Total in 149 ms
Watching for changes in /Users/einari/Projects/Dolittle/Documentation/Source/Hugo/{content,repositories,themes,..}
Watching for config changes in /Users/einari/Projects/Dolittle/Documentation/Source/Hugo/config.toml
Serving pages from memory
Running in Fast Render Mode. For full rebuilds on change: hugo server --disableFastRender
Web Server is available at //localhost:1313/ (bind address
Press Ctrl+C to stop

It is now a matter of opening up a browser to the URL http://localhost:1313 and start writing documentation. With the default option, the page will live reload when saving any files.


All documentation is written in markdown following the GitHub flavor. Markdown can be written using the simplest of editors (Pico, Nano, Notepad), but there are editors out there that gives great value and guides you through giving you feedback on errors. Editors like Visual Studio Code and Sublime Text comes highly recommended. VSCode has for instance a markdown preview feature.