Step 01
Structure
Define routes, content collections and where content lives.
Content sites that load almost instantly.
Astro development for content-led sites - near-zero JavaScript by default, excellent Core Web Vitals, and any CMS you like behind it.
Astro ships no JavaScript unless a component genuinely needs it. For content-led sites - marketing, documentation, blogs, portfolios - that produces pages that load dramatically faster than the equivalent React build.
This site is built in Astro with Payload behind it, so the approach is one I use rather than only recommend.
A typical React marketing site ships a framework runtime, a router and the component tree to every visitor, to power a page that is mostly text and images and barely interactive.
Astro renders to HTML at build time and sends only the JavaScript that specific interactive components require. Visitors get the content sooner, Core Web Vitals improve, and search engines see fully-rendered HTML with nothing to wait for.
Astro's islands architecture lets individual components hydrate while the rest of the page stays static HTML. A page can carry a React-powered filter or carousel without shipping React for the entire page.
You can also mix frameworks - React, Svelte, Vue - in one project, which is occasionally very useful when reusing existing components.
Server-rendered HTML is the most reliably indexable thing you can serve, and that matters more now than it did a few years ago: AI answer engines crawl and quote pages, and they are considerably less patient with client-rendered content than Google has become.
Astro also makes structured data, canonical URLs, sitemaps and files like llms.txt straightforward to generate from the same content source, so metadata stays correct automatically rather than by discipline.
Design and build of the page templates, content integration with your chosen CMS or Markdown, structured data and metadata generation, a sitemap, image optimisation, and deployment to static hosting or an edge platform.
Where a project needs server-side behaviour later, Astro supports server rendering and API routes, so starting static does not corner you.
Content-led sites where load speed matters: marketing sites, blogs, documentation, portfolios and ecommerce front ends. It ships almost no JavaScript by default, so pages load faster than an equivalent React build.
Yes. Astro's islands architecture lets you drop React, Svelte or Vue components into a page and hydrate only those, while the rest stays static HTML. You can even mix frameworks in one project.
Very. It outputs fully server-rendered HTML, which is the most reliably indexable format for both search engines and AI answer engines, and it makes structured data, sitemaps and metadata easy to generate from the same content source.
How a astro development engagement actually runs, start to finish.
Define routes, content collections and where content lives.
Develop templates that ship static HTML with islands only where needed.
Images, metadata, structured data and Core Web Vitals.
Ship to static or edge hosting with rebuilds wired to content changes.
Full Time Contract Available. Tell me about your project, your timeline and your budget, and I’ll reply with an approach and a rate.
Start a project
