Publishing investor-relations disclosures without a CMS built for it

A listed company's investor-relations section has requirements a general-purpose CMS doesn't anticipate: filings must be timestamped and immutable once published, categorised by disclosure type in a way that matches the exchange's own taxonomy, and retrievable by shareholders and analysts years later without a single broken link. Most page builders assume content that gets edited, not content that becomes a permanent public record.

We built exactly this for a listed contract chemical manufacturer with three decades of operating history - a full IR hub covering board composition, audit committee details, annual and quarterly reports, and exchange release filings, alongside a standard corporate site and product catalog.

1. Treat disclosures as records, not editable pages

The single biggest structural decision: once a filing is published, it is never edited in place. A correction becomes a new record referencing the original, exactly the way the exchange itself expects amendments to work. This isn't a technical constraint we imposed for its own sake - it's what makes the site defensible as an accurate historical record rather than a page that quietly changed after the fact.

2. Structure the taxonomy around the regulator, not the sitemap

Categorising filings the way a marketing site organises pages - by audience, by topic, by whatever feels intuitive - actively hurts an IR hub. Analysts and compliance-conscious shareholders look for a specific disclosure type first (board resolutions, related-party transactions, financial results) and a date second. We mirrored the exchange's own disclosure categories directly in the data structure, so the site's filter options match the mental model of someone who already knows what kind of filing they're looking for.

3. Make every filing a permanent, stable URL

A filing referenced in an analyst report or an email from three years ago needs to still resolve. We generate a stable, permanent URL for every disclosure at publish time, independent of any later reorganisation of the site's navigation - the record's address doesn't move even if the menu structure around it does. Redirects exist as a safety net, not as the primary mechanism, because a redirect chain is one more thing that can eventually break.

1. Assign each filing a permanent slug derived from its disclosure type and date at creation, never regenerated later.
2. Store the original document (PDF) alongside structured metadata (type, date, board committee, financial period), so the page can be rebuilt from data even if the template changes.
3. Provide both a browsable listing and a direct-download document link for every filing - some visitors want the page, some just want the PDF.
4. Version any correction as a new linked record, with the original left untouched and clearly marked as superseded.

4. Build for the compliance team's workflow, not a marketer's

The people publishing to an IR hub are usually company secretaries and compliance staff working against exchange deadlines, not content editors optimising copy. The admin flow we built prioritises speed and correctness over flexibility: upload the document, select the disclosure type from a fixed list matching the regulator's categories, confirm the date, publish - with the structured page, PDF link, and listing entry generated automatically from that single action, rather than requiring a separate manual step for each.

An investor-relations page isn't marketing content with a serious tone. It's a compliance record that happens to be a webpage - design the publishing workflow around getting it right once, not iterating on it later.

How do you structure a stock-exchange-compliant investor-relations page?

Treat every filing as an immutable record with a permanent URL assigned at publish time, never edited in place - corrections become new, linked records instead. Organise the taxonomy around the exchange's own disclosure categories rather than a marketing sitemap, and store structured metadata alongside the source PDF so the page can always be rebuilt exactly as originally published.