The website is maintained in Git and updated by pushing to the repository at github.com/dita-ot/website.
Source files for the project website are stored in Markdown and HTML, enriched with Liquid templating tags and styled with Sass. The Bootstrap framework provides the foundation for the site layout. The Jekyll publishing engine combines these plain text components to the final static website you see here.
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
html5 transformation 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
--continuous build 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 serve command for local testing. The
--livereload option updates the content in the browser whenever source files change on disk.
Travis CI continuous integration automatically republishes the latest development version of the documentation on the project website whenever changes are pushed to the
develop branch 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.
The pages in the development documentation include Edit this page links that open the DITA source file for the topic in oXygen XML Web Author. The web-based authoring workflow prompts users to log in to GitHub and fork the dita-ot/docs repository if necessary. Changes saved in the authoring environment are committed to a new branch, and a pull request is created to submit changes for review by the DITA-OT documentation team.