Move to Astro & Sanity

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.

Yes. I map the old content to the agreed Sanity model, then test a sample import before moving the agreed volume. I check references and rich text in the Astro templates, and your team reviews the result before launch.

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.

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.

If both you and I build the website with Claude, who do you think will get a better result? I bring the decisions and review that come from building production websites, including the content model and what happens when the site goes live. Claude helps me do the work. I remain responsible for checking it.

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.

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.

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.

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.

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.

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. A handover session is available on request.

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.