Move to Astro & Sanity

I rebuild your marketing website in Astro with Sanity. A speaker, a price or an address is edited once and updates on every page that uses it, with a preview before publishing.

From 3,000 USDexcl. VAT

for a small site, scope and billing agreed before work starts

  • A site structure agreed with you before the build.
  • An Astro website with Sanity set up for your editors.
  • Your existing content migrated and every changed address redirected.

Astro & Sanity

Change it once, it updates on every page

After a price change or a new speaker, someone usually has to find every page that mentions it. Sanity stores each of those as one document the pages reference, so your editors change it in one place.

  • Shared content, edited once

    On the ECCA platform, a speaker's bio is one document. Change it there and every session that lists the speaker shows the new bio.

  • A Studio with your words in it

    Document types and fields named the way your team talks about the content, with required fields enforced and a preview of the Astro page while editing a draft.

  • Old content mapped field by field

    Imported posts and pages land in the new documents with their links, images and rich text intact. I test a sample import first and your team reviews it before the full run.

  • Claude edits the same content

    Your team can ask Claude to update a document through the Sanity connector or MCP server, with the access you grant. I set it up so changes land as drafts for review.

Inside Sanity

In Sanity, editors work with documents and fields set up for your content. These examples show how a field change relates to the page preview and where longer text is edited.

Image credits and licences

Structure first, then the build

We agree what the site is for and which pages it needs before I build anything.

  1. Roadmap workshop

    In one workshop we settle who the site is for, which pages it needs and what each page has to do. You sign off the structure before I build. How roadmapping works.

  2. Astro rebuild and CMS

    I rebuild the site in Astro, set up the CMS for your editors and move the content we agreed. You follow along on a preview link.

  3. Launch and handover

    Every changed address gets a redirect, your editors get trained, and we agree who looks after the site after the 14 days of support.

Before moving to Astro & Sanity

Can I keep my existing Sanity content?

Yes. I review the existing document types, references and queries before deciding what needs to change. If the model already fits your team, I build the Astro frontend around it. I scope any dataset changes separately before work starts.

Can you move content from another CMS into Sanity?

Yes. The old content is mapped to the agreed Sanity model and moved at the volume agreed in the scope, with your team reviewing a sample import first.

Can I start with an audit?

Yes. An audit is optional and helps when you want to understand what is wrong before deciding to rebuild. Roadmapping is included in the migration, so I agree the site's purpose and structure before building it.

Why Astro rather than Next.js?

I've built projects with both. For a marketing site, I usually choose Astro because it sends HTML and CSS by default, with JavaScript added for interactive parts. Visitors can read about your company without loading React for the page. I use Next.js when application features justify it, such as a customer dashboard.

Why hire you if I can build it with Claude?

I build with Claude too. It writes the import scripts, templates and redirect lists faster than I would by hand. I decide which pages stay, how the content is modelled and when a page is ready, then test the site before launch. You hire me for those decisions.

Do you write the content?

No, your team supplies the copy and images. I can migrate your existing content, with the sources and volume agreed before work starts. Copywriting and adding new copy are outside the migration scope.

What happens to my existing URLs?

I inventory the current addresses and plan a redirect for each one that changes. I check the agreed redirects at launch. A migration can affect search traffic, so I do not promise unchanged rankings.

Who owns the code and where does it live?

Your team owns the repository, code and content model. The project work transfers to you once the invoices for that engagement are paid. Existing tools and open-source dependencies keep their own licences. I work in a Git repository your team can access, and hosting and CMS accounts belong to you. I offer a handover session for whoever continues the work.

What happens if you get sick for two weeks?

I work with trusted subcontractors who can stand in for me. I sign a subcontracting agreement with them before they start, and agree any access to your code and content with you.

Can I see a website you built that is still live?

Yes. My work page links to live projects and explains my contribution to each one. The ECCA conference platform is a site I designed and built myself. I describe my role when a project was a team effort.

How do I get my website back if we stop working together?

The repository and service accounts stay accessible to your team. I document how to build and deploy the site, what it connects to and any unfinished work. I agree the final work and invoices with you under our contract, then remove my access when the handover is complete.

What is not included in the migration price?

Your team supplies new copy and images. Copywriting, a new brand identity and ongoing maintenance are outside the build price. I agree the content migration volume and any integrations in the scope before work starts. CMS subscriptions, hosting and usage charges are paid through your accounts.

Something else on your mind? The chatbot answers questions about my work from this site. Ask in English, Polish or your own language.

Ask the agent

Plan your move to Astro & Sanity

  1. Send me your brief

    Share your current site and what your team needs from Sanity.

  2. Agree scope and price

    I reply with what the migration covers, how long it takes and what it costs, before any work starts.

  3. Launch on Astro

    We agree the structure in a workshop, I rebuild the site, and your editors publish from launch day.

Augustyn's chatbot

Ask me about my services, projects or how I work.

For questions about my work, this assistant uses the site and its FAQs. Its answers may be limited. AI can be wrong. Avoid personal details. Privacy