以下の詳しいガイドと説明用の事例は英語です。例に含まれる業務データは架空のものです。
Where Astro fits
A content-led website with selected interactive areas, such as a calculator or enquiry form.
When to choose another approach
A continuously interactive app may suit an application framework. No perfect performance, search or security score is implied.
Worked example and evidence
Fictional services business: editors publish pages through an agreed content workflow and a calculator sends an enquiry to an API. This owned Nodesify website uses Astro, but its results do not predict another site’s results.
What you need to supply
Page inventory, editing requirements, languages, form workflow and third-party scripts.
What acceptance should demonstrate
Confirm editing and form delivery. Record performance with device, network, page, build and measurement date.
Running costs and responsibilities
Own content review, deployment, dependencies, form handling and any editor subscription.
Technical scope to confirm
Astro islands let selected components hydrate independently. Added scripts still affect the visitor experience.
A proposal should identify the systems and data, direction of sync, access feasibility, failure handling, named owners and included deliverables. Listing this technology does not imply a prebuilt connector, vendor partnership or included feature.
When is Astro a poor fit?
When most of the experience is a persistent application with extensive shared client state, compare implementation and maintenance costs with an app-oriented stack.