Dx5 manages content as DITA components inside Microsoft SharePoint, authored in Word through DxAuthor+, with review, approval, quality and publishing on top as a structural layer.
Most organizations manage regulated, technical or commercially sensitive content as finished documents: Word files, PDFs, manuscripts. Searchable, but not reusable. Change one approved paragraph and you update one file; the same paragraph in twenty other documents is left to find by hand. The cost stays invisible until a regulator notices, an audit asks, or a translator bills again for the same content.
The fix is structural. Manage content as components: small, identifiable units with their own version history and approval record, assembled into documents on demand. The same component used in twenty documents is updated once, reviewed once, translated once, and refreshed everywhere it appears. That is what a component content management system does, and Dx5 is the one built for organizations already on Microsoft.
Dx5 is built around seven themes that map onto how regulated, technical or commercially exposed content actually has to behave. Each theme is a capability area in the platform; together they cover the lifecycle from external pressure to global reach.
Regulators do not ask whether the document looks consistent. They ask whether the system can prove who approved each component, when, and against which version of the rule. Dx5 is built so the answer is queryable, not reconstructable.
The hardest problem in any CCMS rollout is SME adoption. Dx5 solves it by keeping authoring inside Microsoft Word through DxAuthor+, with the DITA structure applied behind the scenes. Editors see the editing tools; reviewers see a clean read-only view.
The component model is what makes structured content economic. A single approved paragraph used in twenty documents is updated once, reviewed once, translated once, and refreshed in every assembly that uses it.
When an auditor asks for the chain of custody on a regulated statement, the answer should be a query. Dx5 captures the change history, the approval trail, the broken link, the orphan, and the precise diff between revisions, the things that turn an audit response from days into seconds.
Built-in approval workflows replace the email-and-chase pattern. One-click publishing with real-time progress replaces the waiting game. Self-provisioning replaces the deployment ticket. Each step compounds into faster cycle times across the team.
Dx5 is not a separate product to add to the inventory. It is a SharePoint application. React and TypeScript on Microsoft Fluent UI, SharePoint Framework (SPFx) for integration, ASP.NET back-end, Microsoft Entra ID for single sign-on. Same access control, identity model and security posture as the rest of the M365 tenant.
The same component library that feeds an EU-only labeling pack feeds the US English version, the German installer manual, and the Japanese chatbot answer. Translation packages generated per language in one operation. Output formats chosen at publish time, not designed in upstream.
Topics and maps live once in the SharePoint library. From there Dx5 assembles them into whatever the downstream audience needs. The same paragraph that lands in a printed manual lands in an HTML portal page and an API response: drawn from the same approved source, refreshed automatically when the source changes.
Word, HTML and XML, generated on demand from the component library. Template-driven, with table-of-contents, figures and index options chosen at publish time.
REST endpoints exposing components, maps and assemblies to downstream consumers: supplier portals, in-app help systems, partner integrations.
Customer- or operator-facing published portals built from the same component library. EASA's Easy Access Rules format is one example.
Authoritative, version-controlled content for AI assistants, in-product help, and LLM-backed answer surfaces, drawn from the approved source rather than from PDFs the model has to re-interpret.
Dx5 sits in the middle of a regulatory content stream that has two sides. DitaExchange customers run on both.
Regulators, safety authorities, standards bodies and rule-publishing teams. They draft, approve and publish the rules that everyone else has to comply with. EASA publishes European aviation regulations on Dx5 since February 2018. CNSC publishes Canadian nuclear safety regulations. EDA coordinates military aviation rules across EU member states.
Dx5 is the editorial system: components, workflow, version history, multi-format publishing.
The regulated organizations on the receiving end: primes, manufacturers, operators, energy producers, financial-services firms. EASA's regulations alone reach more than 20,000 stakeholder companies across Europe. Each of them has to integrate, distribute and use the rule content the upstream organizations publish. Lockheed Martin, GKN Fokker, MagVenture and Grundfos all run Dx5.
Dx5 is the integration system. APIs, portal pages, downstream republication, AI-ready content.
The same DitaExchange platform serves both sides because both sides are working with the same content: one creating it, the other consuming it. The component model is what makes that economic.
Dx5 is not the right answer for every content team. It is the right answer for organizations where the consequence of inconsistent content is regulatory, legal, financial or operational, and where the IT environment is already Microsoft.
Labeling, clinical, pharmacovigilance and CMC, with audit-grade approval at the fragment level.
ExploreDisclosures, prospectuses, factsheets and DORA documentation across multiple filings.
ExploreRegulatory rule sets, technical publications and capability frameworks across NATO and EASA standards.
ExploreMulti-decade asset documentation, licensing dossiers and decommissioning records.
ExploreRulemaking, guidance and consolidated law, published so the version everyone reads is the version in force.
ExploreProduct manuals, multi-language publishing and reuse across product families.
ExploreThe common thread is not the sector. It is the cost of inconsistency, the regulatory expectation of traceability, and the practical advantage of working inside the Microsoft platform IT already runs.
One place to look for each of the four jobs: bringing existing content in, managing and publishing it, writing it, and checking it against your rules.
The content you already have, brought in as components.
Content management and publishing inside Microsoft SharePoint.
Structured DITA authoring inside Microsoft Word.
Rule-based content quality across the SharePoint repository.
DitaExchange does not make that claim. What Dx5 records is an approval trail at the component level: who approved which component, when, and against which version of it, held as platform data rather than reconstructed from email. That is a different thing from a validated electronic signature, and no 21 CFR Part 11 sign-off claim is made for it. If a qualified e-signature is a hard requirement in your quality system, raise it in the first conversation rather than the last.
Probably not. The argument for Dx5 is that the substrate is a SharePoint estate you already run and have already cleared with security, legal and procurement. Without that estate you would be adopting Microsoft in order to adopt a CCMS, which is the wrong order to do things in. Organizations on another stack, or that want the vendor to hold the substrate and the identity model, are better served by a cloud-native DITA CCMS such as Heretto or Paligo.
No. Dx5 generates a translation package per language and tracks the language variants alongside the source content, so one component set feeds every market. The translation work itself stays with your vendor and your translation memory tooling. What changes is the volume going out: one approved component translated once, instead of the same paragraph translated again in every document that contains it.
In the browser, inside SharePoint. The topic tree, map assembly, workflow state, snapshots and publishing runs are Dx5 surfaces, and that is where a technical publications team spends most of its day. Word is the surface for writing and reviewing the content itself. One honest limit: DitaExchange has no help-authoring tool of its own, so a team that wants a Flare-style output studio next to the CCMS is comparing MadCap, not us.
The previous DitaExchange line split the platform into many separately named components, DxReview among them. This generation consolidates that surface into four products, and review and approval are Dx5 platform capabilities rather than a separate product alongside it. Anyone running an older version should ask us about their own installation rather than reading a version number off a web page.
Most Dx5 rollouts start with the one document set where inconsistency already costs the most, then let the component model compound from there.
