Industry, Regulatory & technical publishing
Publishing without the XML specialists
Regulators, standards bodies and technical publishers all hit the same wall: the content is highly structured, the output has to be exact, and the people who write it are lawyers and engineers rather than XML operators. We build the platforms that close that gap.
What structured publishing requires
Authoring for subject-matter experts
A browser-based editor your legal and policy teams can actually use, producing correctly structured content underneath without asking the author to understand the structure. That is exactly what the Australian Energy Market Commission’s workflow does.
One source, every format
Automatic PDF, DOCX and HTML output from a single source, so a determination or standard is published across formats without anyone reformatting it three times, and without the three versions drifting apart. This is what our legislative and regulatory publishing platform does in production.
Versioning and audit trail
Regulatory content has to prove what it said and when. Versioned documents, tracked amendments and a defensible history of change, which matters as much for internal review as for the public record.
Built for legislative bodies
A custom extension we built for Quark Publishing Platform NextGen, specifically for legislative agencies and legislative bodies: Git-style branching for document management, so parallel drafts and amendments branch, then merge back with automatic conflict detection. As a Quark partner for Australia and the USA, we license, implement and support QPP, and the extension with it.
Secure, controlled distribution
Where documents cannot simply be public: watermarked, per-organisation distribution with access controlled by entitlement, the model behind the aircraft technical publications portal we built for SES.
The proof
Work we have shipped, not a capability deck.
- Australian Energy Market Commission A browser-based structured content workflow giving legal and policy teams automatic PDF, DOCX and HTML publishing, no XML specialists required. Read the case study
- SES (formerly Intelsat) A secure portal delivering versioned, watermarked aircraft technical publications to airline organisations worldwide. Read the case study
- GPSL Turning an enterprise content-management provider’s website into a lead engine, for a business serving aerospace and defence. Read the case study
- Standards Australia The Digital Standards Web App, dynamic XML rendering on the NISO STS framework, with permissioned access, bookmarks and annotations. Read the case study
- SES, entitlement-based content portal Purchase-driven entitlement and role-based views separating technical content from marketing material, at operator scale. Read the case study
Common questions
How do you handle versioning and audit trails?
As a first-class requirement rather than a feature bolted on. Documents carry revisions, states and a full record of who changed what and when. In regulated publishing, being able to prove which version was current on a given date matters as much as the document itself.
Can you control who sees which documents?
Yes, and enforced at the data layer rather than in the interface. For SES we build entitlement so a query can only ever return documents that operator is entitled to see, the safest place for that rule is as far from the UI as possible.
Can it integrate with our existing publishing workflow?
Yes. Structured authoring, controlled review and approval steps, and delivery to the channels your audience already uses. We have built exactly this for aviation technical publications and for regulatory bodies, where the workflow is the product, see technical publications and structured content.
Trusted by
Start a conversation
Start a conversation
Tell us what you want to build, fix or scale, we’ll come back with a clear way forward.