I contribute to the DITA Open Toolkit as a collaborator and have served as the documentation lead since the version 2.0 release at DITA Europe / DITA-OT Day 2014.
With over a thousand commits to the documentation in the past three years, I contribute to the project on a regular basis and communicate closely with the core committers to keep up with recent changes to the toolkit.
The site Colophon explains how we build and maintain the DITA Open Toolkit project website:
The DITA-OT project website is hosted via GitHub pages at dita-ot.github.io, which redirects to dita-ot.org. The website is maintained in Git and updated by pushing commits to the repository at github.com/dita-ot/dita-ot.github.io.
The Documentation section is maintained in DITA using the source files from the DITA Open Toolkit documentation repository at github.com/dita-ot/docs. The OT docs are transformed to HTML5 using the org.dita-ot.html plugin, which extends the default
html5transformation with additional processing specific to the project website.
Site output is built with Gradle using the settings in the site.gradle build file. The DITA Open Toolkit Gradle plugin is used with the Gradle dæmon and the
--continuousbuild option to automatically regenerate the site output whenever documentation source files change. A staging environment provides a preview of generated site output via the
jekyll servecommand for local testing.
Travis CI continuous integration automatically republishes the latest development version of the documentation on the project website whenever changes are pushed to the
developbranch of the dita-ot/docs repository. The development docs are indexed by Algolia DocSearch, which provides the full text search capabilities available via the search form in the navigation bar.