plugin-benefits.dita 1.7 KB

1234567891011121314151617181920212223242526272829303132
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
  3. <!-- This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. -->
  4. <concept id="plugin-benefits">
  5. <title>Plug-in benefits</title>
  6. <shortdesc>Plug-ins allow you to extend the toolkit in a way that is consistent, easy-to-share, and possible to
  7. preserve through toolkit upgrades.</shortdesc>
  8. <prolog>
  9. <metadata>
  10. <keywords>
  11. <indexterm>plug-ins
  12. <indexterm>benefits</indexterm></indexterm>
  13. </keywords>
  14. </metadata>
  15. </prolog>
  16. <conbody>
  17. <p>The DITA-OT plug-in mechanism provides the following benefits:</p>
  18. <ul>
  19. <li>Plug-ins can easily be shared with other users, teams, or companies. Typically, all users need to do is to
  20. unzip and run a single installation command. With many builds, even that installation step is automatic.</li>
  21. <li>Plug-ins permit overrides or customizations to grow from simple to complex over time, with no increased
  22. complexity to the extension mechanism.</li>
  23. <li>Plug-ins can be moved from version to version of DITA-OT by reinstalling or copying the directory from one
  24. installation to another. There is no need to re-integrate code based on updates to DITA-OT core processing.</li>
  25. <li>Plug-ins can build upon each other. If you like a plug-in, simply install that plug-in, and then create your
  26. own plug-in that builds on top of it. The two plug-ins can then be distributed to your team as a unit, or you
  27. can share your own extensions with the original provider.</li>
  28. </ul>
  29. </conbody>
  30. </concept>