# A content system that let marketing ship without engineering

Client: Fielding Health
Industry: Healthcare services
Published: 2026-02-18

A six-week rebuild replaced a CMS that required a developer for every blog post with a version-controlled content system marketing could run on its own.

---
Fielding Health's marketing team was stuck routing every blog post and landing-page edit through a developer queue, on a CMS that hadn't been upgraded in three years. Publishing cadence had slowed to roughly one post a month — not because the team lacked ideas, but because every change meant waiting on an engineering ticket.

## What we did

- Migrated the site to a static-first architecture with content stored as version-controlled Markdown, so schema validation catches mistakes at build time instead of in production.
- Trained the marketing team on a Git-based editing workflow with a preview environment, removing the developer handoff entirely.
- Rebuilt the information architecture around three core service lines instead of the eleven overlapping categories the old site had accumulated.

## Outcome

Within the first quarter after launch, organic traffic was up 34%, and the marketing team was publishing on the same day an idea was ready instead of waiting weeks for a developer slot. Site load times also improved enough to register as a secondary factor in the search visibility gain.

---

## Results

- **Time to publish a post:** 6 weeks → same day
- **Organic traffic, first quarter:** +34%
- **Pages requiring a developer to edit:** 0

---

## Client quote

> They rebuilt our marketing site in six weeks and our organic traffic was up double digits within the first quarter. The content system means our team ships blog posts without ever pinging engineering.

— Elena Marsh, VP Marketing, Fielding Health