Move to Astro & DatoCMS
I rebuild your marketing website in Astro with DatoCMS. Your team gets reusable content blocks and a preview of the pages they edit.
From 3,000 USDexcl. VAT
- Information architecture and page planning before the build.
- An Astro website with DatoCMS set up for your editors.
- Migration of agreed existing content and launch checks.
Astro & DatoCMS
Reusable content with a preview of the actual page
I build the DatoCMS models around your content and connect them to Astro. I set up the editing choices your team needs, with draft previews to check changes before publishing.
Blocks that match your page layouts
I define the blocks your editors can add and map them to Astro components. I keep the field names and choices close to how your team describes the content.
Rich text that fits the design
I render DatoCMS Structured Text in Astro, including the agreed embedded blocks. Your team can edit the copy without changing the layout code.
Preview before the page goes live
I configure DatoCMS visual editing for Astro and test the draft workflow with your page templates.
Content queries your team can maintain
I write the GraphQL queries the site needs and document where content enters the build. I agree publishing and deployment with your team.
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.
Check how the title and description appear in the search preview.
Source: official documentation
Change the hero copy and check it against the page preview.
Source: official documentation
Describe what an image shows in its alternative text field.
Source: official documentation
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 & 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?
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 & DatoCMS
Send me your brief
Share your current site and what your team needs from DatoCMS.
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.