Your client's content is trapped in a CMS. Be the one who frees it.
Structured content briefs keep landing on agency desks and keep getting declined, because nobody has a DITA team. We are that team — working behind your brand, converting WordPress, Joomla, Confluence, Sitecore and legacy PDF into clean, validated DITA.
Not an agency? We take direct engagements too — book a migration assessment.
A CMS renders pages. It was never built to hold a product library.
Your client probably can't name the problem, but they can describe it. Here's what they're actually saying — and what you can now say back.
"We change one thing and miss it in nine places."
- The same safety warning is pasted into 40 pages. One gets corrected; 39 don't.
- A PDF manual and a help article contradict each other, and nobody knows which is live.
- Every new output format means rebuilding the content by hand.
What changes: content becomes topics. The warning lives once, is referenced everywhere, and is corrected in one place. Every channel builds from the same validated source.
"Translation costs more every single release."
- Vendors quote on full word count each cycle, because nothing is reusable.
- Regional variants have been forked into separate documents that now disagree.
- Arabic or right-to-left output is handled as an entirely separate build.
What changes: translation memory bills only what actually changed. Conditional attributes let one source serve every region, so variants stop being separate documents.
"An auditor asked who changed it. We couldn't say."
- No ownership metadata, no review dates, no approval record on any page.
- Support agents search the portal, don't find the answer, and raise a ticket instead.
- The AI assistant project stalled, because retrieval quality died on unstructured pages.
What changes: every topic carries version history, ownership and metadata you can query. Clean, bounded, labelled topics are also exactly what a retrieval system needs — so the AI project unblocks as a side effect.
Three services. They chain.
A client who buys the first almost always buys the next two — which is what makes this a practice rather than a project.
Source to DITA, with metR
Extract from the CMS or PDF library, map to an agreed information model, convert with metR's rule packs. Validated topics, working map structure, resolved links and a reuse report — not a pile of untagged XML.
Information model & taxonomy
Topic types, metadata scheme, conditional attributes, reuse strategy and map architecture — agreed and signed off before anything converts. This is the deliverable that makes the migration worth doing.
Ongoing content operations
Authoring capacity, review workflow, DITA-OT plugin work, localisation handoff and a publishing pipeline wired into the release cycle. Run by us, or handed over with runbooks.
Five stages. Each ends in something you can hold.
No black box. Stop at any gate and keep everything produced to that point.
Content audit
Page counts, duplication, orphaned assets, broken links, language coverage. Usually the first time anyone has seen the whole library at once.
Information model
Topic types, metadata scheme, conditional attributes, naming conventions, map architecture.
Pilot conversion
A representative slice — usually the hardest 40 to 60 topics — run through metR and tuned against real output.
Full conversion & QA
Batch conversion, DTD and Schematron validation, link resolution, reuse extraction, human review of everything flagged uncertain.
Publish & hand over
DITA-OT configuration, custom plugins, CI pipeline, author training and runbooks.
What gets a migration approved.
These are the arguments you'll be making in the room. Ranges are indicative of structured-content programmes generally — the audit replaces them with the client's own numbers.
Compliance you can evidence
Version history, approval trails and ownership metadata on every topic. "Who changed this and when" becomes a query.
Support deflection
Topic-level content is findable content. Structured help surfaces the specific answer, which is what stops a ticket.
AI-ready by construction
Retrieval quality depends on chunk quality. DITA topics with real metadata already are clean, bounded, labelled chunks.
Vendor independence
DITA is an OASIS standard, not a product. Content stays portable across Heretto, Tridion, IXIA, AEM Guides, oXygen or plain Git.
Faster releases
Documentation builds from the same pipeline as the product, and stops being the thing that holds up a date.
Bounded cost
A defined project, not an open-ended cleanup. The pilot produces the real number before anyone commits to the full run.
No logo wall. Here's what you can verify instead.
TechConnect Space is a new company, and we'd rather you heard that from us than worked it out on the third call. Everything below is checkable before you put us in front of a client.
We are a partner company of Metapercept, which has delivered DITA-XML, CCMS implementation and content migration for enterprise clients across manufacturing, aerospace, healthcare and defence. Metapercept holds ISO 9001:2015 and ISO 27001:2022 certification. The capability isn't new; the company presenting it to you is.
metR is a released migration platform in commercial use, not an internal prototype. You watch it convert your client's content during the pilot rather than taking a conversion rate on trust.
Each of the five stages terminates in a named artefact. You can stop at any gate and keep everything produced to that point. There is no stage where you wait and hope.
We don't quote a conversion accuracy figure up front, because it depends entirely on how consistently the source was authored. The pilot measures it on the client's real content, and the full-run price is built from that measurement.
Converted content, information model, custom DITA-OT plugins and documentation belong to the client. DITA is an OASIS standard, so nothing produced is locked to us or any vendor. The cost of us being wrong is bounded — that's the point.
Bring us a live opportunity, or a hypothetical one.
Send a CMS export, a few URLs, or one representative PDF — yours or a client's. We'll come back with a scoped assessment: what's there, what converts cleanly, what needs rework, and what it would cost you to resell.