I build marketing sites in Astro with Sanity for the editors. After launch, a change starts as a request and ends as a preview you approve. The same person designs it, builds it and ships the hundredth edit.
A sample site with invented data. Pick a request: a fix, a new section, or a new page. On a real site each one arrives as a preview, and nothing goes live until someone approves it.
Five stages, in this order. Each one ends with something you can open and check, so you know where the project stands without asking.
Every page, form, integration and person who edits the site, written down before anything is designed. The stack is Astro, with Sanity and Cloudflare.
4 in hand so far
The pages become document types and fields in Sanity: what repeats, what references what, and which fields search engines read.
7 in hand so far
Color, type and spacing as tokens, then the sections built from them. New pages are assembled from these parts, so they match the old ones without anyone checking.
10 in hand so far
Templates wired to Sanity, forms posting to wherever leads actually live, analytics behind consent, and a preview of every draft before it publishes.
14 in hand so far
Redirects, sitemap and a speed check, then the domain moves early in the week so problems surface while I am watching.
18 things handed over, all yours
Marketing edits pages and posts in Sanity Studio, served from your own domain. Layout stays in code, so a busy week of publishing cannot break the design.
Pages are rendered ahead of time. JavaScript loads only for the parts that move or respond, like a calculator or a demo, not for every heading and paragraph.
Titles, canonicals, the sitemap, structured data and an llms.txt are generated from the content, so a new page cannot ship without them.
The site is plain files in your GitHub account, hosted in your Cloudflare account. If you stop working with me, nothing has to be exported.
After launch a request arrives through the Console or the channel agreed at kickoff, and comes back as a preview. Nothing goes live until you approve it.
Documented components and tokens mean a coding agent builds a new page from the same parts I would, and the change still arrives for review.
Better to hear it before the build than after it.
Changes
Where your team asks for something
Site
What visitors load
Content
Where editors write and publish
Hosting
Where it runs, in your accounts
Most marketing pages are the same for every visitor, so they can be built once and served as HTML. Astro does that by default and adds JavaScript only to the components that need it, which keeps pages light without anyone having to fight the framework.
If it's a better fit for your site, I do that too.
Yes, in Sanity. Editors change copy, images, posts and page sections there, and publishing rebuilds the site. What they cannot do is invent a new layout, which is the point: the design system holds.
On a static build, publishing in Sanity triggers a rebuild, which usually takes a minute or two. Pages that genuinely need to change instantly can be rendered on request instead; that gets decided page by page during scoping.
A move from another platform is fixed price from $5,000, quoted once after the inventory. A new build is scoped the same way. Ongoing work afterwards is $2,500 a month with no minimum term. The cost page breaks the bands down.
I do, all of it: scope, content model, design system, build, launch and the changes after. There is no handoff to a junior and no second team. The trade is capacity: there is no second team to absorb a rush, so scope and cost are agreed in writing before work starts. More on that.
On Cloudflare, in your account. A mostly static marketing site often fits in the free tier. Sanity has its own plans, which depend on your team size and usage, and I check them against your editors during scoping.
Then the content is already structured in Sanity and the site is a normal repository, so a new front end can read the same content. Nothing is locked inside a builder.
I can scope a migration. Send a brief and I will reply by email with next steps.