Understand
Business goals, publishing workflow, content inventory, integrations, and what's constraining the current site.
Astro development for marketing sites that need to be fast.
A modern frontend with a visual CMS on top, so the site is genuinely fast and your marketing team can still publish without a developer.
Why Astro
Why we build marketing sites in Astro.
Astro is the default recommendation for content-heavy marketing sites where performance matters and the content model is more than a flat list of pages.
Zero JavaScript by default
Pages ship as HTML and CSS. Interactivity is added deliberately as islands rather than hydrating the whole page.
Content as typed collections
Content collections give you schema validation and reuse, so the same content can serve multiple pages and channels.
A visual CMS on top
Editors get a visual editing experience with live preview, so a modern stack doesn't cost you publishing autonomy.
Git-based and reviewable
Branches, preview deploys, code review, and rollback, which is what makes changing a site safe.
Framework-agnostic islands
React, Svelte, or Vue components can coexist where they're genuinely needed, without committing the whole site to one.
Cheap and calm to operate
Static output on a CDN. No PHP runtime, no origin database, no caching plugin stack to maintain.
What's included
What an Astro build includes.
- Information architecture
- Component library
- Editor training and documentation
- Forms and lead routing
- Technical and on-page SEO
- Hosting, CI/CD, and preview deploys
- Content modelling and schema design
- Astro build and templating
- Headless CMS integration
- Search implementation
- Accessibility (WCAG 2.2 AA)
- Visual design and design system
- Visual CMS setup and configuration
- CRM and marketing automation
- Analytics and consent management
- Performance budgets and monitoring
Process
How a build runs.
Architect
IA, content model, CMS choice, integration plan, and hosting architecture agreed before design starts.
Design
A component-based visual system built around real content, not placeholder copy.
Build
Astro components, content collections, CMS wiring, and integrations, with preview deploys from day one.
Validate
Accessibility audit, Core Web Vitals, analytics verification, content QA, and editorial UAT.
Launch
Deployment, DNS, redirects, analytics verification, then post-launch monitoring and training.
Honest assessment
When Astro is, and isn't, the right choice.
We recommend Astro often, but not universally. Here's the line we draw.
Astro is a good fit when
- The site is primarily content and marketing pages
- Performance matters commercially
- Content needs structure and reuse
- You want a visual editor without a monolith
- Integrations need real control
- You publish frequently
Astro is the wrong choice when
- You need heavy authenticated application UI
- The site is a React app with a marketing skin
- Nobody wants a build step or Git workflow
- A simpler visual platform would genuinely suffice
- You need ecommerce at platform scale
The stack around Astro.
Astro · Sanity · Contentful · React · Tailwind · Vercel · Cloudflare · HubSpot · GA4
Tools: Astro, Sanity, Contentful, React, Vercel, HubSpot
Migrating in
Coming from another platform?
WordPress → Astro
Move from a plugin-heavy monolith to a fast, modern frontend and flexible visual CMS.
View migration pathWebflow → Astro
Keep marketing autonomy while moving beyond the limitations of an all-in-one platform.
View migration pathNext.js → Astro
Get marketing pages out of the product repo and off the product release cycle.
View migration path
Relevant work
Recent projects.
FAQs
Astro development questions.
Can our marketing team edit an Astro site?
Yes. A visual CMS layer sits on top so editors compose pages from approved components with live preview. Publishing autonomy is a requirement of the build, not an add-on.
How do you choose between Astro and Next.js?
If the site is content and marketing, Astro. If it's an application with a marketing surface attached, Next.js. Most companies have both, and the mistake is running the marketing site on the app's architecture.
Which CMS do you recommend?
It depends on your content model, team size, and governance needs. Sanity for flexible structured content, Contentful where enterprise workflow matters, and a visual CMS layer for page composition.
Can we keep using React components?
Yes, as islands where interactivity is genuinely needed. The rest renders as static HTML, which is the whole point.
How long does an Astro build take?
A marketing site is typically eight to fourteen weeks including design. Migrating an existing site without a redesign can be as quick as six.
Who hosts it?
Usually Vercel or Cloudflare. If you need it inside your own infrastructure, static output makes that straightforward.