Astro best practices

Use when building or reviewing Astro sites and apps, including .astro components, content collections, file-based routing, integrations, and islands.

Mental model

• Astro is server-first and content-focused. Default to shipping less client-side JavaScript, not more.
• Use Astro components and HTML-first templates for pages that do not need a fully hydrated client framework.
• Reach for islands only where interactivity is actually needed.

Rendering and islands

• Keep the default rendering strategy as light as possible.
• Hydrate interactive components deliberately; every island should justify its client-side cost.
• Avoid turning an Astro site into a fully client-rendered app unless the product truly needs that shape.

Project structure