Custom theme

Marketing site rebuilt so the team ships pages without a developer

A US SaaS company's marketing team filed a developer ticket for every copy change. The rebuild moved them to a locked pattern library they publish from themselves — without letting the design drift.

3 days → 20 min

to publish a page

timed: new feature page from existing patterns

-92%

developer tickets for content

tracked, first quarter post-launch

+58%

organic sessions

GSC, 6 months post-launch vs. prior 6

reusable patterns shipped

pattern library at handover

Representative engagement. The client's identity is withheld under NDA, and the figures shown illustrate typical outcomes for this type of rebuild rather than one client's audited results. The methodology described below is exactly what I run on real projects.

Client

SaaS company

Identity withheld under NDA

Industry

B2B SaaS

Services

Custom theme development

Timeline

6 weeks

In short

A rigid marketing site was rebuilt as a block theme built around nine reusable, structure-locked patterns. Marketers now edit copy and assemble pages themselves in minutes rather than waiting on developer tickets, and the design system holds because layout is locked while content stays editable.

The challenge

Every headline tweak, pricing change and new landing page went through a developer, so marketing worked on a two-week lead time for edits that should have taken minutes. The underlying cause wasn't really the theme — it was that all 60-odd pages had been built as bespoke one-off layouts, so nothing could be reused and every new page started from scratch. The team had tried a page builder previously, which solved the speed problem and created a new one: within months no two pages shared spacing, type scale or button styles.

Starting point

Measured before the rebuild: 61 published pages sharing no common layout system, average 11 working days from copy request to live page, 3 competing button styles and 7 heading sizes in use across the site, and 100% of content changes routed through a developer.

The approach

The real problem wasn't the theme — it was that every page was a bespoke layout, so nothing could be reused. I modelled the content before writing any theme code, because a pattern library only works if the patterns match how the team actually thinks about pages.

✓Audited all 61 existing pages and found nine recurring section types doing effectively all of the work — the rest were one-off variations nobody needed

✓Built those nine as native block patterns with locked structure and editable content slots, so a marketer can change words and images but cannot break the grid

✓Defined the design system in theme.json — spacing scale, type ramp, colour palette — so patterns stay visually consistent without per-page custom CSS

✓Used block locking and template parts to protect global elements like headers, footers and CTA blocks from accidental edits

✓Ran a 90-minute handover session with the marketing team and left a one-page internal guide, because a system nobody understands gets abandoned inside a month

The results

The marketing team now assembles and ships pages from the pattern library without developer involvement, and the design system holds because structure is locked at the pattern level rather than relying on discipline. Cleaner semantic markup and a consistent heading hierarchy also improved crawlability, which contributed to the organic traffic figure — though I'd treat that number carefully, since the team also increased publishing volume over the same period.

What this didn't cover

Scope was the marketing site only — no paid-ads landing pages, no CRM or marketing-automation integration, no content writing and no ongoing SEO retainer. Blog post templates were explicitly out of scope and still use the previous layout. Analytics attribution wasn't rebuilt, so the traffic figure reflects total organic sessions rather than qualified conversions, and it overlaps with a period of increased publishing — the rebuild is one contributing factor, not the sole cause.

Services used on this project

Want the same for your site? Start here:

Custom WordPress theme development, hand-coded for speed WordPress theme customization

Common questions

Will my marketing team actually be able to use this?

That's the part most rebuilds get wrong. Patterns are locked at the structural level, so the worst a non-technical editor can do is write copy that's too long — they can't break the layout, delete the grid or introduce a fourth button style. I also run a live handover session rather than just sending documentation, because systems that aren't taught get abandoned.

Why a block theme instead of a page builder like Elementor?

Page builders solve the speed problem and create a consistency problem: they give editors unlimited freedom, so within a year you have a dozen spacing values and no design system. A block theme with locked patterns gives editors freedom exactly where it's useful (content) and removes it where it's harmful (structure). It's also considerably lighter, since there's no builder framework loading on every page.

What if we need a layout that isn't in the pattern library?

Then it becomes a new pattern, which is a small piece of work — usually a day. That's deliberate: the friction is a feature. If every new layout were free, you'd be back to 61 bespoke pages within a year.

Verified reviews

What clients say on Google

These are general reviews of working with me, not comments on this specific project.

★★★★★

“Fantastic Developer. Very knowledgeable. Very patient. Works extremely hard. Very good English Skills. Good communication skills. Takes the time to understand the project scope and the minor details in your project. I am very impressed.”

Silvia B

Google Reviews

★★★★★

“Great developers! All the team are professionally, it's a pleasure work with them :). I, sincerely, recommend it.”

Laura Ballart

Google Reviews

★★★★★

“Worked with them in several projects. They are always good and responsive. More projects will be coming.”

Anatano dev

Google Reviews

More results

WooCommerce Subscription store rebuilt to hold up through peak season Read case study → Migration Moving off Wix to WordPress without losing search rankings Read case study → Maintenance Twelve clinic sites brought under one care plan Read case study →

Want results like these?

Send me your site and goals — I'll tell you exactly what's worth doing.

Start a conversation