Astro consultancy

You are about to pick an SSR adapter, decide which components actually need a client:* directive, or find out why a content collection reference silently failed to resolve. Book the hours and I review that one decision with you.

Astro is the framework this site itself runs on, and one of the two I build production sites in at Bejamas, alongside Next.js - see Agentic coding consultancy for the general architecture and code review. This page is scoped narrower: islands, adapters, and content collections, hour by hour.

Book time

Custom quote

An islands audit - which client:* directives are pulling in JavaScript a static component could avoid.
An SSR adapter review for your actual deploy target, and what changes between Cloudflare Workers, Vercel, and Netlify runtime constraints.
A content collections schema review, including a check for dangling reference() ids that a green build will not catch on its own.

Experience

Islands and adapter calls, reviewed for your project by the hour.

FAQ

Questions, answered

What does this cover?

An islands audit when client:* directives are shipping more JavaScript than the page needs, an SSR adapter review when Cloudflare Workers, Vercel, or Netlify each behave differently against the same code, a content collections schema review, and a Core Web Vitals pass on a specific page or template, with fixes ordered by impact. Astro's content collections don't fail the build when a reference() field points at a document that doesn't exist - the loader logs an error and keeps going (astro#13268) - so I check for that explicitly instead of trusting a green build.

What does this not cover?

General architecture review, code review, or Core Web Vitals work that isn't Astro-specific. That's Agentic coding consultancy. And if you need an Astro site built from scratch, that's a fixed-price AI-editable website build, scoped separately.

In practice

How an Astro review runs

Send me the repo and the question
The adapter question, the islands you're not sure about, or the schema you want checked. One paragraph and read access to the project is enough to start.
I read the build before I quote
I go through the component islands, the adapter config, and the content collections schema, then give you a fixed hour estimate. No retainer running in the background.
You get it in writing
Which directives to drop or change, what the adapter actually supports at your deploy target, and where the schema has a gap a green build won't show you. Written down, so it survives the call.