Industries / Public Sector
Public Sector
Residents did not choose your website, and they cannot go somewhere else. It has to work for everyone, in every language you publish in, across every department that has a page on it. We build accessible, bilingual Magnolia DXP setups that department teams can publish on safely, the same approach we used to bring Alameda County’s department sites onto one platform.
Clients include
Alameda County
Every Department Has A Website. Few Of Them Match
Public bodies rarely end up with one website. Public health, social services, transportation and emergency services each get their own, on their own timeline, often on low-cost tools that each cover part of the job. A few years later the sites look different, meet the accessibility rules to different degrees, and an update that matters to everyone has to be copied by hand onto each one.
The answer is not a new site for every department. It is one governed setup where the shared parts are built once and every department publishes inside the same guardrails. Magnolia is well suited to that, as long as it is set up that way from the start.
Four Things We Plan For In Every Public Sector Engagement
01
Accessibility Is A Duty, Not A Feature
Public websites are held to an accessibility standard, and complaints are public. We build to the standard you answer to, test against it, and protect it with permissions so one edit cannot quietly break it.
02
Two Languages, Same Day
In Canada, the English and French versions go live together. Translation belongs inside the publishing workflow, not in a spreadsheet beside it.
03
Editors Are Not Developers
Department staff publish alongside their real jobs. Templates and permissions let them publish safely without being able to break a layout.
04
Procurement Sets The Pace
Budgets, RFPs and approved tools are decided well in advance. We work with the tools you have chosen, build around their gaps, and plan the work in phases a budget cycle can carry.
Where We Spend Our Time In Public Sector Work
Multi-department Platforms
A parent and child structure. The central team publishes shared content and styles once, and they flow down to each department’s site automatically.
Accessible Templates & Guardrails
Standard templates and components built to and tested against the accessibility standard you are held to, with editing permissions that keep them that way.
Bilingual Publishing
English and French built into the content model from day one, with translation part of the approval workflow, so a page is not finished until both versions are.
Migrations Off Aging Systems
Content audits, URL mapping, redirects and a planned cutover, so a resident following an old link still lands on the right page.
What It Looks Like In Practice
Public Sector
10+ department websites governed from one Magnolia platform, with 1,000+ pages migrated
Alameda County
1,000+
Pages migrated into one component-based architecture
10+
Department sites under one governed Magnolia platform
Publish once
Parent-site content reaches every department site automatically
2008
Building enterprise platforms since
Numbers on this page are Solutions CTC’s own. Client business metrics appear only with written consent.
Questions Public Sector Teams Ask Us
Will you certify our website as accessible?
We do not issue certifications. We build to and test against the accessibility standard your organization is held to, whether that is WCAG 2.1 AA, Section 508 in the US or a provincial standard, and we set up templates and permissions so the site stays there as content changes.
Can you deliver the site in English and French?
Yes. We are based in Montreal and work in both languages every day. We set up the content model so French and English are managed together from the start, which is much easier than adding a second language after launch.
Can you work with the tools we have already procured?
Yes. At Alameda County we connected Magnolia to the public-sector tools the County had chosen for cost reasons, and built around their gaps so workflows still ran between departments. We would rather make your approved tools work than ask you to buy new ones.
Can each department keep control of its own content?
Yes, inside guardrails. Each department publishes its own pages, the shared parts come from the central site, and permissions decide who can change what. Departments get independence without drifting apart.
Do you respond to RFPs?
Yes. We respond to RFPs and RFIs for Magnolia work. Tell us when you get in touch that it is for an RFP, and we will make sure the right people see it quickly.
Where will our content be hosted?
That follows your rules. Magnolia runs self-hosted or on Magnolia PaaS, and we plan the setup around your data residency and security requirements before anything is built.
Reading For Public Sector Platform Teams
Article
Composable DXP In Regulated Industries
What composable actually changes for a team that answers to a regulator, and what it does not.
Article
Multilingual Content In Magnolia 6.4
Keeping translations, approvals and regional versions in step across a multilingual Magnolia setup.
Article
Why Enterprise Platforms Fail After Launch
Why platforms drift in the months after launch, and the governance that keeps them on track.
Bring Every Department Onto One Platform
Tell us how many sites you run, which languages you publish in and which accessibility standard you answer to. We will tell you honestly what a first phase looks like, and whether we are the right fit.