Many organizations wait the last minute – sometimes at the brink of disaster– to select a good DITA content management system.
But what if the DITA CMS could facilitate your DITA adoption, right from the start and scale up with your project to full production, freeing up your time so that you can focus on YOUR content and customers?
|Requirement||Without Componize||With Componize|
|Test and troubleshoot new content DITA compliance||Topics with broken links are found at the time of publishing and must be found and fixed manually.
XML validation is applicable only when opening and editing the maps with the DITA compliant editor.
New content from writers starting with DITA must be validated manually.
|Componize sustains your DITA content, filters automatically topics with issues (links or DITA compliance) which can then be quickly accessed and troubleshot.|
|Test your business rules: file and ID naming, content organization, taxonomy and document/project information (metadata)||Changing business rules is cumbersome. The information architects must change every file name and corresponding links manually.
Taxonomy has to be managed in a separate tool. Search on multiple metadata is impossible.
|Change your content organization as you go. Componize takes care of the links for you.
Componize allows you to view directly the taxonomy, changing it in one step where needed to adapt to your content model.
You can also inject metadata model to all content in a specific folder.
|Test your topic and map templates, and adapt the information structure and metadata to each project||Templates must be shared on all authors’ local environments and kept up to date manually, for each project. Maintaining the templates is also risky, with casual authors not using the latest templates available.
|The information architect can multiply, update and version all topic and map templates.
The templates are as easily updated as content topics and made readily available to all writers in the project.
|Select favorite editor-s||Teams with multiple user profiles need adapted tools with access to the repository for reusing and sharing files.
|With Componize, you choose and select the rights editors for you and your team. Because all is stored in native XML, you can also switch tools where needed.|
|Test the information structure with publishing, including conditions and stylesheets
|Local publishing will not make the publishing options available to all. Everyone must copy and configure the exact publishing options.
|With Componize, one person can set up the publishing pipeline and make them available to all|
|Exchange files for QA and editing||Every author must copy content for QA. Then the editor must repack and send back everything, effectively creating copies of the content (original and updated) in multiple locations.
|Componize provides a content-centric repository, where the author can quickly upload their content and the editors can review and comment immediately. Automated versioning ensures no change is overridden by error. The author can see original and updated content, see comments and compare the original version and edited version.|