astro

Astro best practices enforce a server-first design using Islands architecture, applying client directives selectively for optimal hydration and performance. This approach minimizes client-side JavaScript by rendering components on the server and only hydrating interactive islands when needed.

To validate content collections in Astro, use Zod schema validation to enforce proper data loading patterns and structured content types. This ensures your markdown and data entries are strictly typed and safely queried during the build process.

The best way to manage Astro environment variables securely is using astro:env/server to distinguish between client and server contexts. This future-proofs sensitive data handling by ensuring secrets are only exposed during server-side build-time or runtime operations.

You should use client directives in Astro Islands only when a component requires client-side interactivity. Relying on server-first architecture by default, you add hydration directives solely to interactive elements to minimize JavaScript payload and maximize web performance.

Handle Astro framework build-time and runtime variables by adhering to specific patterns for variable handling using astro:env/server. This separates static build configurations from dynamic runtime secrets, ensuring secure management and preventing sensitive data exposure on the client.