Three Astro tips for everyday use

Short and practical — three things that have proven themselves in day-to-day work with Astro.

1. The build as a test#

npm run build is the most important check here: broken frontmatter, broken images or type errors show up with precise messages.

2. Take content types seriously#

The Zod schema in src/content.config.ts is not bureaucracy — it is documentation with a backbone: what is not in the schema does not ship.

3. Stay calm about errors#

Astro’s error messages name file and line. Read first, act second — it saves half of the debugging.