Skip to content
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Netlify Status

This repository contains the source code powering the Silverstripe CMS developer documentation website and userhelp website.

This application is build on Gatsby, a static site generator based on React. It sources content from the framework repository for each major release.

This repository does NOT contain any documentation.

The developer documentation is stored in the framework module repository, in the docs folder. For example, the documentation for the master branch of Silverstripe CMS is stored in

The userhelp documentation is stored in the userhelp-content repo.


To set up a local instance of

  • Clone this repository to an empty directory
   git clone path/to/ssdocs

Docker install

No local NodeJS nor gatsby-cli is required for this option.

  • Make sure docker and docker-compose are installed and docker daemon is running
  • Simply use ./docker/run to run gatsby commands
    • ./docker/run build would be equal to run gatsby build within a container
    • ./docker/run develop -p 8000 would run gatsby develop -p 8000 within a container.

Native install


Once cloned, from the root of the repository, run the command yarn dev-docs to instantiate a development server. This will consume all of the markdown files in both major release branches and allow you to browse the developer documentation site on http://localhost:8000 by default (see the Gatsby docs for instructions on customising the port).


To test a static build of the site, first create a production environment file.

cp .env.development .env.production

Then, run the build.

yarn build-docs
yarn serve

These commands will give you an exact representation of how the site will run on a production server, with statically generated html files and server-side rendering.

Toggling between docs and userhelp

Whether the application uses the content or is determined by the environment variable, DOCS_CONTEXT. You can set this in the .env.development file, or use one of the script shortcuts:

yarn dev-docs
yarn dev-user
yarn build-docs
yarn build-user


You can make changes directly to the source markdown files and get live updates in the development server without having to rebuild the app or even refresh the browser. The clones of the silverstripe/framework repositories are in the .cache/gatsby-source-git folder in the root of this project. There are subfolders for 3/ and 4/, respective to their branch names. You can edit the files in docs/en from there.

Just don't forget to merge your changes upstream once you're done. Building the gatsby app will not preserve your content changes, since the remote repositories are the source of truth.

Deploying content changes

Once your contribution has been merged into the master branch, it will be deployed to production via a Github action in the repository that holds the markdown files (e.g. silverstripe/silverstripe-framework for docs).

Deploying app changes

Once your change is merged in to the master branch of this repository, it will be deployed to production.


To contribute an improvement to the or functionality or theme, submit a pull request on the GitHub project. Any approved pull requests will make their way onto the or sites in the next release.

If you wish to edit the documentation content, submit a pull request on the framework Github project or the userhelp documentation repository or corresponding module.