The latest version of my Bootstrap plug-in for DITA Open Toolkit 3.3 generates HTML5 output with a Bootstrap 4 styling base.
At DITA Europe in Rotterdam, I spoke about producing custom output with DITA Open Toolkit and suggested it may no longer be quite as hard as you recall.
DITA-OT 3.2 introduces a new plug-in registry that makes it easier to discover and install new plug-ins via a searchable list at dita-ot.org/plugins.
As of version 3.0, DITA Open Toolkit supports Markdown out-of-the-box along with the alternative authoring formats proposed for Lightweight DITA.
Join the DITA Users Berlin meetup on September 27 to learn how HERE Technologies tests and validates DITA docs with open-source plugins for DITA Open Toolkit.
At DITA Europe this year, I’ll be speaking about how the DITA Open Toolkit project uses DITA features and open-source tools to build the toolkit documentation.
Join our first meetup to learn how Markdown can help you to simplify the authoring process and gather input from contributors who are less familiar with DITA.
At the XLIFF Symposium in Berlin, I showed how to transform XML files from the Darwin Information Typing Architecture to a single XLIFF file and back.
On the rise of Markdown as an alternative input method for DITA projects.
Now that the DITA Open Toolkit is hosted on GitHub, it’s easier than ever to contribute changes to the DITA-OT source code or the documentation.
At DITA Europe in Munich, the DITA Open Toolkit contributors split the toolkit documentation into a dedicated repository to make it easier to contribute.
When generating PDF output via DITA Open Toolkit, users often stumble over image scaling issues. You can make images fit by setting dimensions and resolution.
Dan Ochs has posted several nice tutorials on customizing the output produced by the DITA Open Toolkit PDF2 plugin.
Today Robert Anderson announced the availability of Milestone 10 of the DITA Open Toolkit version 1.5.
When building PDFs for different products with DITA Open Toolkit, you can store customizations in separate folders and reference them with customization.dir.