WordPress Development for Public Health and Government
The easiest platform to build badly, and the cheapest to run well.
WordPress powers a large share of the web and most of what is written about it is aimed at people who want a site quickly. The version of this that matters for an institution is different — accessibility that holds under audit, translation that does not cost per page, and a theme a communications team can operate without a developer.
We rebuilt the Massachusetts Problem Gambling Helpline on a custom WordPress theme — accessible componentry, custom content types, and a translation architecture that runs to a few dollars a month.
WordPress is the most widely used CMS on the web: a block editor most communications staff already know, no licence cost, and an ecosystem deep enough that almost any requirement has a starting point. The argument against it in a regulated institution is usually made about security and plugins, and it is the wrong argument. What actually goes wrong is that a site gets assembled from a commercial theme and thirty plugins, each with its own markup, and accessibility becomes something no one can assert about the whole. Build the components yourself against the standard and that failure mode disappears, along with most of the plugin surface. What you are left with is a platform with the lowest operating cost of anything comparable, an editorial experience people already know, and no licence renewal — which for a public agency answering to a budget is not a minor point. The discipline is refusing the shortcuts that make it fast to stand up and expensive to own.
Our Work with WordPress
How the Work Splits
A mature open-source CMS with the largest editorial user base of any platform, a block editor most communications staff already know, no licence cost, and a plugin and hosting ecosystem deep enough that almost any requirement has a starting point.
The build discipline that decides whether the site is auditable — custom themes and content types instead of a commercial theme plus plugins, componentry written against WCAG so accessibility is a property of the system rather than a scan at the end, translation architecture that does not price per page, and analytics that measure the action the site exists to produce.
A site shaped like its audience rather than like a template. The Massachusetts Problem Gambling Helpline reaches most of its visitors on a phone, in a hard moment, for about fifteen seconds. Its rebuilt WordPress platform carries custom content types, accessible components, and a translation architecture pairing a front-end language switcher with a glossary-backed machine-translation service — so the site speaks Spanish from launch and its ongoing translation cost runs to a few dollars a month.
The work in practice
WordPress is the platform most likely to be dismissed in a procurement conversation and most likely to be the correct answer anyway. The dismissal is usually about security and plugin sprawl. Both are real, both are consequences of how a site was built rather than of the platform, and both are avoidable by the same decision.
The decision that determines everything else
Build the components, do not assemble them. A commercial theme plus thirty plugins produces a site whose markup no one controls, which means accessibility is something you can test but never assert. Custom theme, custom content types, componentry written against WCAG — and suddenly the standard is a property of the system rather than a report someone runs before launch and hopes about afterwards. It also collapses the plugin surface that the security objection is really about.
Translation is where the budget quietly goes. Most approaches price per page or per word, which means the cost of language access scales with the thing you want to grow. Pairing a front-end language switcher with a glossary-backed machine-translation service inverts that: institution-specific terminology is defined once, the stored result is reusable, and the running cost stops tracking the size of the site. On the Helpline that arrangement runs to a few dollars a month.
The editorial experience is already solved, and that is worth money. Communications staff at an agency or a health system have very likely used WordPress. A platform people already know is a platform that does not need a training budget, and it is the reason a custom theme beats a bespoke CMS for most institutional publishing.
And there is no licence. For a public agency that renews a budget annually and answers for it, the absence of a per-seat or per-environment fee is a structural argument, not a rounding error.
The Massachusetts Problem Gambling Helpline
The audience makes this build unusual. Analytics on the old site showed 88% of visitors arriving on a phone, three quarters never reaching a second page, and an average visit of about fifteen seconds — people arriving in a hard moment, under stigma, with the narrowed attention a crisis imposes. The site had that long to work.
So the platform was rebuilt around it: a custom theme replacing the legacy build, custom content types, accessible componentry to WCAG, and the translation architecture above, with Spanish live at launch. Call, text and live chat are surfaced in the content of every key page and stay visible on mobile with the menu closed. A confidential screener sits directly on the find-help page, one question at a time. Calls placed from the site were invisible to the old analytics; a custom event now tracks tel-link clicks, so the Helpline can see the site doing its one job.
Branding came from Argus; strategy, design and build from Pare. The engagement is written up as Fifteen Seconds to Help.
When the job is an application
The test is whether the hard part is publishing or logic. When the thing being built is an application — user accounts with real entitlements, transactions, scoring, workflow with teeth — the assumptions change with it, and we match that engagement to a purpose-built application on Drupal, which costs less over five years than publishing tools stretched past their shape.
Practice leadership
Matthew O’Bryant
Matthew O’Bryant has spent his career on audit-grade delivery, which is mostly a question of what a platform is like to operate in year three rather than at launch.