All case studies
WordPressHealthcareMulti-sprint

NHS Inform health information platform

Content-rich health information site with custom Gutenberg blocks, flexible layouts, and a CMS the internal team owns.

This case study covers how we built the NHS Inform platform so editors could publish health pages without a developer ticket.

10+

Page templates

100%

Gutenberg

ACF

Structured content

NHS Inform health information platform

The problem

The client needed a flexible, content-heavy health platform maintainable by non-developers — multiple layout patterns, strong accessibility, and SEO without sacrificing editor experience.

The solution

Custom Gutenberg blocks and ACF-driven templates gave the content team modular pages, responsive design, and full control over updates without developer intervention.

What we built

  • →WordPress build on Gutenberg Block Editor (no page-builder lock-in)
  • →8–10 unique page templates with modular SCSS architecture
  • →Custom reusable blocks tailored to editorial workflow
  • →ACF for structured content and flexible layouts
  • →Responsive, accessible, SEO-friendly front-end
  • →Documentation and handoff for internal content team

Outcomes

  • ✓100% Gutenberg-powered editorial experience
  • ✓Custom blocks designed for long-term scalability
  • ✓Client-owned content updates without dev tickets
  • ✓Reusable components across page types

How it shipped

Health pages are long, and the people updating them are editors, not developers. The build stayed in WordPress and Gutenberg so a page is a stack of blocks the team already understands. Advanced Custom Fields holds the structured bits, such as a warning or a related link, without a page builder that would own the content. Templates cover the layouts they actually publish. SCSS stays modular so a new block does not restyle the archive.

Accessibility and on-page structure were part of the templates, not a pass at the end. The handoff was documentation the content team could follow. After that, a new page does not need a developer ticket. The CMS, the blocks, and the content belong to the client.

Stack:WordPressGutenbergACFSCSSPHP

Want results like this?

Book a call. Fixed-price quote if we are a fit.

Book a call

More case studies