Skip to content

Product

Shakewell Content Portal

A structured content publishing platform for regulators, standards bodies, and legislative and technical publishers — author once in the browser, publish everywhere, and deliver version-critical documents securely to exactly the right readers.

Whether you need a legislative publishing platform for regulatory instruments or a technical documentation portal for a global fleet of manuals, the Content Portal replaces forked PDFs and shared drives with one structured, searchable, always-current source of truth.

Talk to us about your documents

What the portal does

Structured authoring, no XML specialists

Legal, policy, and editorial teams author entirely in the browser. Underneath sits XML built on structured content standards — DITA, JATS, S1000D, XHTML — but your authors never touch a tag, and a reused clause or warning is updated once, everywhere.

One source, every format

Publishing is automatic and multi-format: PDF, DOCX, and clean accessible HTML generated from a single structured source, so the web portal, the print edition, and the download are never out of step.

Secure, watermarked delivery

Enterprise SSO sign-in, role-based access control down to individual document collections, and an in-browser viewer with configurable watermarking on viewing and download — sensitive publications stay protected wherever they travel.

AI-assisted markup and navigation

AI-generated tables of contents and structural markup take the drudgery out of preparing large documents, so structure and navigation keep pace with the content instead of lagging behind it.

Built for very large documents

The XML-to-PDF pipeline renders large, complex documents to press-ready output in under two minutes — thousand-page publications rebuild on demand rather than overnight.

Enterprise publishing workflows

Draft, review, approve, publish — with separate staging and production environments, full version history, and revision and supersession tracking. Nothing goes live without the right sign-off, and readers only ever see the current approved version.

A legislative, regulatory and technical publishing platform

Regulators & rule-makers

Legal and policy teams author regulatory instruments in the browser and publish PDF, DOCX and accessible HTML from one structured source — versions, amendments and commencement handled by the platform, not by filename conventions.How AEMC publishes.

Standards bodies

Standards live or die on versioning, licensing and structure. Our team built Standards Australia'sDigital Standards Web App— dynamic XML rendering with permissioned access — and that same discipline runs through the Content Portal.

Technical publishers

Manuals, supplements and revisions delivered to exactly the readers entitled to them — SSO, role-based access and watermarked viewing, as in theSES aviation portal. Part of our widertechnical publishing practice.

In production, in regulated industries

The Content Portal isn't a concept — it runs the publishing workflows of organisations where an out-of-date document is a genuine risk.

Common questions

What formats does the Content Portal publish to?

PDF, DOCX and clean, accessible HTML — generated automatically from a single structured source, so the web version, the print edition and the download are never out of step.

Do our authors need to know XML?

No. Authors work entirely in the browser. Underneath sits structured XML, but your legal, policy and editorial teams never touch a tag — at AEMC, regulatory documents are authored and published by the teams who own them, with no XML specialists involved.

Which structured content standards does it work with?

The XML underneath is built on structured content standards including DITA, JATS, S1000D and XHTML. If your organisation already has a schema — legislative, standards-driven or bespoke — the content model is built around it rather than forcing a migration to ours.

Is it a legislative publishing platform?

Yes — that is one of its two home grounds. Regulatory instruments, rules and codes are exactly the documents it was built for: versioned, amendment-aware, published to every format from one source, with the current version always unambiguous. The other home ground is technical documentation delivered securely to entitled readers, as in the SES aviation portal.

How is sensitive content protected?

Enterprise SSO sign-in, role-based access control down to individual document collections, and an in-browser viewer with configurable watermarking on viewing and download — so distribution stays within entitlement, and a leaked page carries its provenance.

Do you run it for us, or hand it over?

Either. It runs as a managed platform — we operate the infrastructure, upgrades and pipelines — or we implement it and hand it to your team with training. Most regulated-industry clients choose managed; the choice stays open.

Show us your worst document library

Bring us your most tangled documentation problem and we'll show you what it looks like structured, searchable, and current — delivered as a managed platform, or implemented and handed over to your team with training.

Enquire about Content Portal