We build the systems that structured content runs on

Component content management

We implement and operate CCMS platforms — principally Quark Publishing Platform — as the source of truth for organisations with serious publishing obligations. That means content modelling, schema design, workflow and gating, permissions, audit trails and full version history, built around how your organisation actually reviews and releases content. Documents stop being files. They become components with independent lifecycles, tracked reuse, and the ability to be assembled differently for different audiences and outputs.

Structured authoring and XML standards

Our team works natively across the specification landscape, and where clients need to move between formats we build transposition rather than forcing a single-standard decision.

• —S1000D — full feature surface including applicability, across multiple issues
• —ATA iSpec 2200 — air transport technical publications
• —DITA and DocBook — topic-based and general technical documentation
• —SGML and bespoke XML schemas — including legislative and standards-driven models
• —S-Series logistics specifications — S2000M (provisioning and parts), S4000P (preventive maintenance), S5000F (in-service feedback)

Branching and merging

Version control for documents, built by Shakewell and unique to our implementations. Concurrent authoring is where most publishing processes break down: four people work on the same document, each takes a copy, and someone spends a week threading the needle back together in Word. We applied the model software engineering has used for thirty years — authors branch from a point in time, work independently, and merge back with automatic conflict detection. It works at document and component level, so a heavy structural edit can run in parallel with next month's release without either putting the other at risk.

Migration off legacy tooling

We migrate organisations off MadCap Flare, Word-based processes, file-share estates and end-of-life systems into structured, componentised content. The approach is deliberately staged: discovery and documentation of the current estate, a migration plan, a pilot on documents you nominate, testing and UAT, then systematic migration. We carry existing identifiers and version history across rather than resetting everyone to version one — your content arrives with its provenance intact.

Content services platforms

Publishing to a fixed output format is a solved problem that has stopped being the right problem. We build API-driven content layers that release approved content once and serve it to everything downstream — public websites, embedded views, mobile, participant systems, service platforms and AI. Consumers request what they need, including differences between any two versions, and receive structured data rather than a document to parse. This is also what makes content genuinely accessible: a REST API can be consumed by assistive technology and rendered appropriately for the reader, where a PDF is a flat image with text trapped inside it.

AI-ready content

Content now has two audiences: people and machines. If your published content cannot be ingested and reasoned over reliably, it will be worked around rather than used. We help organisations get their content into a state where language models can consume it accurately and with the right authority signals — released versions only, correct applicability, defined terms resolving in context. This is upstream work on the content itself, not a chatbot bolted onto a website.

Publishing pipelines and output

PDF, Word, HTML5, full HTML sites, XML, JSON, YAML and packaged deliverables to a downstream specification. Publishing targets are configured to whatever the destination requires, including direct integration with existing distribution channels and scheduled release automation.

PLM and the engineering toolchain

Technical publications do not sit on their own. We work with PTC Windchill as the product lifecycle system alongside the publishing platform — exporting ACT and PCT XML compatible with Windchill, and synchronising product and document metadata with the Oracle Agile database — so the publication record and the engineering record stay in step rather than drifting apart between releases. Where the two systems disagree, that is usually the defect nobody has found yet.

Integration

We connect publishing platforms to the systems around them: SSO through Okta, Entra ID and equivalents with group and permission inheritance; service management platforms such as ServiceNow; PLM and engineering systems including PTC Windchill and Oracle Agile; collaboration and version control tooling; and BI and analytics layers including Power BI.

Hosting, security and compliance

We architect, build and operate the infrastructure — predominantly AWS, with Azure and GCP equally supported, and a per-client account structure that keeps environments properly isolated. We work with clients whose security review processes are genuinely demanding, including Australian banks and government agencies, and we handle that process alongside you: assurance documentation, government-assessed regions, penetration and compliance requirements, and sitting in the room with your security team when that is what it takes.

Managed service and support

Implementation is the beginning. We run platforms long-term — infrastructure management, platform upgrades, publishing pipeline maintenance, and support from level one end-user assistance through to deep platform engineering.

Energy and regulatory

Legislative and rules publishing, participant-facing technical specifications, market documentation — the work behind our legislative and regulatory publishing platform.

Defence and aerospace

Technical publications to military and industry specification, including work in secure and air-gapped environments.

Standards bodies

Standards development, publication and licensing workflows, including Standards Australia's Digital Standards Web App.

Satellite and telecommunications

Technical documentation and portal integration.

Scholarly and scientific publishing

High-volume structured content with complex production requirements.