Skip to content
This repository has been archived by the owner. It is now read-only.
Switch branches/tags

Latest commit


Git stats


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

Migrated to

This is the source code powering It primarily consists of the SilverStripe framework and the docsviewer module with minimal configuration.

For adding functionality or editing the style of the documentation see the docsviewer module.

Getting started

To set up a local development environment:

  1. Use a _ss_environment.php file to configure your site.
  2. Clone this repository to a LAMP server.
  3. Install Composer.
  4. Run composer install to install dependancies.
  5. Run BuildTask ./framework/sake dev/tasks/RefreshMarkdownTask flush=1
  6. Make sure to flush the cache for markdown content to show up.

Source Documentation Files

Documentation for each module is stored on the filesystem via a full git clone of the module to the assets/src/ subdirectory. These checkouts are ignored from this repository to allow for easier updating and to keep this project small. For the main documentation, a branch is used for each minor version of SilverStripe CMS.

To update or download the source documentation at any time run the following BuildTask command with sake:

cd /Sites/
sake dev/tasks/RefreshMarkdownTask flush=1

This build task will download / update each module as listed in the app/_config/docs-repositories.yml file. Running sake dev/tasks/RebuildLuceneDocsIndex flush=1 will then create a search index and reindex the documentation to facilitate searching.

Once the build task has executed and downloaded the latest files, those files are registered along with the module version the folder relates to through the app/_config/docsviewer.yml file.

      Path: "assets/src/userhelp_3.2/docs/"
      Title: "User Help"
      Version: "3.2"
      Stable: true
      DefaultEntity: true

Set Stable: true on the set of documentation relating the current stable version of SilverStripe CMS.


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

The content for is stored in a separate repository: If you wish to edit the documentation content, submit a pull request to that Github project. Updates to the content are synced regularly with via the cron job UpdateDocsCronTask.

Cron job

The cron job UpdateDocsCronTask includes tasks that fetch the latest documentation for each module from git and rebuilds the search indexes.

public function getSchedule() {
    return "0 8 * * *"; // runs process() function every day at 8AM


Deployment is via the SilverStripe Platform deployment tool.