Ship on-brand pages at the speed of marketing.
I build marketing sites on Sanity, backed by a real design system and reusable blocks. Your team publishes new pages without joining a developer queue.
What I do
From content chaos to a system that scales
I connect content models, reusable page blocks, migration, and handoff into one working system.
Content models built around real workflows
Sanity schemas are shaped around the pages your team publishes, who edits them, and how content moves from draft to live. Localization is planned into the model when the project needs it.
Reusable page blocks that stay on brand
A component library with deliberate layout and content guardrails. Editors can assemble new pages from reusable blocks, with UX and conversion thinking built into the patterns.
Controlled migration and launch
Content is mapped, migrated, and checked in stages. Redirects, launch testing, and an agreed rollback plan reduce risk without promising unchanged rankings.
A handoff the team can own
Editors and developers get training, documentation, and access to the code and content they need. I can stay involved, but the setup is designed not to depend on me.
Content models built around real workflows
Sanity schemas are shaped around the pages your team publishes, who edits them, and how content moves from draft to live. Localization is planned into the model when the project needs it.
Reusable page blocks that stay on brand
A component library with deliberate layout and content guardrails. Editors can assemble new pages from reusable blocks, with UX and conversion thinking built into the patterns.
Controlled migration and launch
Content is mapped, migrated, and checked in stages. Redirects, launch testing, and an agreed rollback plan reduce risk without promising unchanged rankings.
A handoff the team can own
Editors and developers get training, documentation, and access to the code and content they need. I can stay involved, but the setup is designed not to depend on me.
I'm a front-end engineer who builds marketing sites and content systems for companies that outgrew their old setup. I care about two things: a CMS your team can run without me, and a front-end that stays fast and on-brand as it grows. I've built design systems, reusable component libraries, and Sanity Studios that marketing teams actually like using. The unglamorous parts, like schemas, migrations, and handoff docs, are what decide whether a site still works in two years. So I sweat them.
We map your content and your team
We map your content and your team
We start with how your team actually works. What pages you ship, who edits them, and where the current setup slows you down. Then we model the content and agree on scope.
- Content modeled around real pages
- Editors involved early
- Scope and milestones up front
I build the system. You watch it take shape.
I build the system. You watch it take shape.
No going dark for weeks. You get regular updates, working previews in Sanity, and room to adjust before anything is locked in.
- Frequent check-ins
- Live previews, not slide decks
- Room to iterate
We launch carefully, with a rollback plan
We launch carefully, with a rollback plan
I handle the technical side: migration, redirects, hosting, and tracking. We test everything, fix what needs fixing, then go live with confidence.
- Migration and redirects handled
- Analytics wired up
- SEO checks before and after launch
Your team runs it. I'm here if you need me.
Your team runs it. I'm here if you need me.
You own everything. I train your editors and devs, leave clear docs, and stay available for whatever comes next.
- You own the code and content
- Training and docs included
- Ongoing support available
Ways to work together
One project, scoped around what your site needs.
After a short call, I turn the problem into a clear plan with the right deliverables, timeline, and support.
Build what your team needs. Leave them with a system they can run.
That could mean a new Sanity site, a controlled migration from your current CMS, or focused work inside an existing system. The scope follows the outcome, not a preset package.
- Project types
- New sites, CMS migrations, and system improvements
- Typical timeline
- 3–10 weeks
Need ongoing help instead? Embedded support is scoped around your team's priorities and cadence.
A typical project includes
- Discovery, workflow, and content mapping
- Sanity content model and editor experience
- Reusable page system with live previews
- QA, launch planning, documentation, and handoff
Get in touch
Site can't scale? Team stuck waiting on devs? Let's fix that.
Tell me where your CMS or site is holding you back. I'll tell you how I'd fix it.