Move to Astro & DatoCMS
I rebuild your marketing website in Astro with DatoCMS. Editors build pages from blocks that match your design and see the Astro page update beside the fields as they type.
From 3,000 USDexcl. VAT
- A site structure agreed with you before the build.
- An Astro website with DatoCMS set up for your editors.
- Your existing content migrated and every changed address redirected.
Astro & DatoCMS
Pages built from blocks, checked against the live preview
A page in DatoCMS is a record made of blocks. I define one block per section in your design, with field names in your team's words, so an editor only ever adds sections the layout already supports.
Blocks that match your page layouts
Each block your editors can add matches one section of the design, so a page built in DatoCMS looks like the page that was designed.
Long copy without layout breakage
Structured Text lets editors write long copy with headings, links and embedded blocks, and it renders in the design's styles every time.
Preview before the page goes live
Visual editing shows the draft on the real Astro template, so editors see the page before publishing.
Search and image fields built in
Search title, description and image alt text are fields on the record, with a preview of the search result while editing.
Inside DatoCMS
The page copy and its search preview need to describe the same thing. These examples show where editors check that relationship and maintain the images used on the page.
01 / 03
Structure first, then the build
We agree what the site is for and which pages it needs before I build anything.
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.
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.
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 & DatoCMS
Can I keep my existing DatoCMS project?
Yes. I review its models and records, then agree what can stay. The frontend can move to Astro without replacing the CMS or rewriting every record.
Can editors preview their DatoCMS changes?
Yes. I include draft preview in the agreed build and test it against the Astro templates. I show your editors how to review a change before publishing.
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 agentPlan your move to Astro & DatoCMS
Send me your brief
Share your current site and what your team needs from DatoCMS.
Agree scope and price
I reply with what the migration covers, how long it takes and what it costs, before any work starts.
Launch on Astro
We agree the structure in a workshop, I rebuild the site, and your editors publish from launch day.


