Consolidate & Govern: Republishing Content from Documentation Islands in a Drupal Documentation Hub
Christoph Weber
Solutions Architect
Is your documentation landscape a heterogenous mess? Are you fighting political battles over tooling choices your department inherited because of past history? Do you have a hard time convincing teams to write documentation in the “right” tool?
Large organizations typically have serious documentation scaling issues:
- teams go rogue and start using a broad range of tooling for their documentation;
- internal changes and reassignments add documentation teams with (working) divergent processes and tooling;
- docs-as-code repositories need to be republished for external audiences with varying levels of openness.
In this presentation, I explain how Drupal as a mature Content Management System can help you address these problems. I will share an example of a unified content strategy that addresses these issues in a generic way, and all of which can be executed using a Drupal-based documentation hub.
Solutions Architect
Is your documentation landscape a heterogenous mess? Are you fighting political battles over tooling choices your department inherited because of past history? Do you have a hard time convincing teams to write documentation in the “right” tool?
Large organizations typically have serious documentation scaling issues:
- teams go rogue and start using a broad range of tooling for their documentation;
- internal changes and reassignments add documentation teams with (working) divergent processes and tooling;
- docs-as-code repositories need to be republished for external audiences with varying levels of openness.
In this presentation, I explain how Drupal as a mature Content Management System can help you address these problems. I will share an example of a unified content strategy that addresses these issues in a generic way, and all of which can be executed using a Drupal-based documentation hub.