Government agencies running many department sites

The problem

A ministry runs a main portal plus separate sites for its statutory boards, programmes, and public campaigns. Each was built by a different vendor, in a different year, on a different CMS. Security review has to be repeated for every instance. Every one of them is a live application with a database behind it. Traffic spikes on announcement days: a budget release, a policy change, an exam result. Those are the days the site cannot go down. Nobody can say who approved a given page, or when.

The solution

Consolidate the portfolio onto one platform. Publishing produces static pages. Approval runs as a configured process inside the platform. Each site stays its own tenant.

How Visor handles it

- Each department or board is a site record holding its own content, configuration, theme, and deployment. A change to one site cannot reach another.

- Publishing compiles pages to static output. At request time there is no application stack running and no database to reach. Most of what a public-sector security review examines is absent from the published site.

- Workflow models the agency's approval chain as states and transitions: officer drafts, comms reviews, legal clears, director approves. Adjusting the chain is a configuration change.

- Publishing Delta and build history record what shipped and when. That is the artefact an audit asks for.

What changes

Security review happens once at the platform level and covers every site on it. Announcement-day traffic hits static files, so capacity planning stops being a per-event exercise. Approval moves out of email and into the platform, where it leaves a record. A new statutory board site gets provisioned in days.