Astro best practices
Source-linked guidance on Astro fundamentals: islands architecture, components, pages and routing, content collections, and shipping less JavaScript. Scoped to current Astro; not a general static-site corpus.
Documents
| Document | Version |
|---|---|
Astro components and frontmatterAstro components are the basic building blocks of any Astro project: HTML-only templating components with no client-side runtime, using the .astro file extension. A component can… | |
Content collectionsUse content collections to manage structured content like blog posts or recipes, enabling organization, querying, and editor Intellisense with automatic TypeScript type-safety.… | |
Islands architecture and client directivesImplement Islands Architecture to convert most pages into fast static HTML, loading JavaScript only for specific interactive or personalized regions like image carousels. Avoid… | |
Pages and file-based routingPages are files in the src/pages/ subdirectory, responsible for routing, data loading, and page layout. Supported types: .astro, .md, .mdx (with the MDX integration), .html, and… | |
Why Astro: content-driven and less JavaScriptFor content-driven websites like blogs, marketing, or e-commerce, adopt Astro’s server-first architecture to render HTML on the server, moving expensive rendering off visitors’… |
Source, review, and usage
- Published on Koskamo by
- Koskamo editorial
- Version
- 1
- Documents
- 5 documents
- Reviewed
- 2026-10-04
- Agent lookups
- 0 in the last 90 days
- Reuse
- Original summaries; linked sources retain their own terms.
- Review status
- Maintained with the application; source links supplied
Use this dataset from an agent
Agents can query it without an account. POST to /api/v1/retrieve, or connect an MCP client and call koskamo_retrieve with dataset: "astro-best-practices".
curl --fail-with-body 'https://koskamo.com/api/v1/retrieve' -H 'Content-Type: application/json' --data-raw '{"query":"astro-best-practices","dataset":"astro-best-practices","top_k":3}'