Skip to content

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.

Talk to us about your content

2018
building since
70+
designers, engineers and product people
5
regionsAustralia, Europe, the Philippines, the Middle East and the USA
6,500+
commits across six repositoriesthe three SES aviation platforms we build and still run

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.

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.

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.

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.

Engagement models

How we work

Four straightforward ways to engage us. Pick the one that fits, or mix them as your needs change.

Staff Augmentation

Add experienced Shakewell developers, designers or specialists directly to your own team. Engagements typically run three to twelve months, but can be as short or long as you need — you get the skills without the commitment and cost of hiring full-time.

About staff augmentation

Fixed-Scope Projects

Have a defined outcome in mind? We scope it, price it and deliver it as a project — a clear timeline, agreed milestones and a single point of accountability from kickoff to handover.

Embedded Delivery Teams

For larger or longer-running work, a cross-functional Shakewell team — development, design and delivery management — plugs in as your delivery arm, working to your priorities and your reporting cadence.

Support & Maintenance

Already live? We keep websites, stores and apps secure, updated and performing through ongoing retainers — business-hours support as standard, with 24/7 coverage available for critical issues.

About support & maintenance