Skip to content
DITA Open Toolkit project website ·
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
2.1 Migrate Bootstrap classes in released docs Jan 4, 2019
Gemfile Restore Gemfile Jan 21, 2019
LICENSE Update folder references & add deploy status badge Mar 26, 2019
management.html Run Prettier v1.15.3 on current files Dec 26, 2018

DITA Open Toolkit website Netlify Status

This repository contains the source files for the DITA Open Toolkit project website at

For details and background information on how we build and maintain the site, visit

If you'd like to set up a local staging environment and build a copy of the site, follow the instructions below.

Environment setup

  1. Clone the DITA-OT and project website repositories:

    git clone
    git clone

    NOTE: The examples below assume the the DITA-OT and project website repositories have been cloned to a common parent directory, such as your home folder. If you clone the repositories to a different location, substitute that path for the tilde symbol ~ in the samples below.

  2. Move to the DITA-OT directory:

    cd dita-ot
  3. Fetch the submodules:

    git submodule update --init --recursive
  4. In the root directory, run the Gradle wrapper to compile the Java code and install plugins:

  5. Install the HTML plug-in for the DITA-OT project website: org.dita-ot.html

    src/main/bin/dita --install

Install prerequisite software

  1. Install Jekyll:

    gem install jekyll
  2. Install Bundler:

    gem install bundler
  3. Switch to your clone of the project website repository:

    cd ~/dita-ot-website
  4. Install all of the required gems from the project’s Gemfile:

    bundle install
  5. Run Jekyll.

    bundle exec jekyll serve

    This runs the production version of the site locally, so you can view your local clone of the project website at

    At this stage, what you see there should be identical to the production version of the project website at

    Note: For more details, see Setting up your GitHub Pages site locally with Jekyll.

Building site output

  1. Switch to the docsrc submodule of the local dita-ot clone:

    cd ~/dita-ot/src/main/docsrc
  2. Check out the develop branch of the docs repository to update the docsrc submodule pointer to the latest development state (or to another branch if you need to generate output for that):

    git checkout develop
  3. Run the site build task with the Gradle wrapper to generate the output for the project website:

    ./gradlew site

The output will be generated by default in src/main/docsrc/build/site.

(This appears as unstyled HTML when viewed in place.)

To redirect the output to the dev development folder that Jekyll serves, pass the outputDir parameter to the build script as follows:

./gradlew site -PoutputDir=~/dita-ot-website/dev

After the build completes, you should find the results in the Docs > Development section of the local staging environment

To automatically regenerate the site output whenever documentation source files change, add the --continuous build option:

./gradlew site -PoutputDir=~/dita-ot-website/dev --continuous

Updating JavaScript

If you need to change any of the JavaScript files in the site repository, you'll need to download & install Node.js and run the npm package manager for JavaScript to perform a clean install of the project dependencies:

npm ci

This will install various Node modules including Parcel, the web application bundler.

To make changes to the JavaScript code, add or edit source files in the _js folder. You can then run the install script to re-bundle the modified JavaScript code to the js folder with Parcel:

npm run install

Happy staging!

You can now use the local staging environment to test your changes before committing your work.

When you're ready to share your progress, send us a pull request.

You can’t perform that action at this time.