Move to Astro & Keystatic
I rebuild your website in Astro with Keystatic, a Git-based CMS. Your team edits through an interface while content stays in files alongside the code.
From 3,000 USDexcl. VAT
- Information architecture and page planning before the build.
- An Astro website with Keystatic set up for your editors.
- Migration of agreed existing content and launch checks.
Astro & Keystatic
A CMS for the content in your repository
I set up Keystatic around your content files and build the Astro templates that use them. Editors get fields and collections to work with. Developers and coding agents can edit the same files through your Git workflow.
Content stays with the code
Keystatic stores content in files, including Markdown, JSON and YAML. I agree the file structure and content schema before migrating your existing pages.
An editor for your team
I configure the collections and fields your editors need using the Keystatic Astro integration. They can update content through the admin interface instead of editing source files.
Changes recorded in Git
With GitHub storage, edits are saved to the repository. I agree access, preview and publishing with your team, including how agent changes are reviewed.
Publishing through your website build
I configure Astro to read the content files. Publishing runs through the agreed build and deployment process, rather than a separate hosted content API. I check whether that workflow fits how often your team publishes.
Inside Keystatic
These screens use my site content in a local Keystatic demo. They show how an editor can change a page through a form while the content stays in files alongside the code.
Demo editing setup: open the Home page and find the fields that control its content.
Demo editing setup: change the heading and copy inside the Hero section.
Demo editing setup: update the search title and description stored with the page.
01 / 03
A migration with the planning included
I help you map your business onto a well thought out information architecture before the build starts.
Roadmap workshop
I agree the audience, pages and the job each page needs to do. You review the structure before I build. How roadmapping works.
Astro rebuild and CMS
I build the agreed site and editing setup, then migrate the existing content included in the scope.
Launch and handover
I check redirects and train your editors before launch. I agree who looks after the site.
Before moving to Astro & Keystatic
How is Keystatic different from an API-based CMS?
Keystatic keeps content in files in your codebase. In GitHub mode, edits are stored in Git. A service such as Contentful stores entries separately and makes them available through an API. I use the file-based approach when your team wants content changes to follow the website build and review process.
Do editors need to learn Git?
Editors can use the Keystatic admin interface to change content. I set up the fields and GitHub access, then show your team how to edit and publish. Developers can still work on the same content files in the repository.
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?
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.
Do you write the content?
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. A handover session is available on request.
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 agentPlan your move to Astro & Keystatic
Send me your brief
Share your current site and how your team wants to edit content.
Agree an action plan
I review your situation and propose the migration scope and billing.
Move to Astro
I workshop the structure with you, then rebuild the site and help your editors get started.