Things break in production; we write about why. Incident analysis, infrastructure automation, CI/CD, observability, and open-source SRE tooling.
├── public/
├── src/
│ ├── assets/
│ │ └── fonts/
│ ├── components/
│ ├── content/
│ ├── layouts/
│ ├── pages/
│ └── styles/
├── astro.config.mjs
├── README.md
├── package.json
└── tsconfig.json
Astro looks for .astro or .md files in the src/pages/ directory. Each page is exposed as a route based on its file name.
There's nothing special about src/components/, but that's where we like to put any Astro/React/Vue/Svelte/Preact components.
The src/content/ directory contains "collections" of related Markdown and MDX documents. Use getCollection() to retrieve posts from src/content/blog/, and type-check your frontmatter using an optional schema. See Astro's Content Collections docs to learn more.
Static assets like images and fonts are stored in src/assets/ so Astro can optimize and bundle them at build time. Images are processed by Sharp and converted to WebP. Fonts are managed via the Astro Fonts API with optimized fallbacks to minimize layout shift. Only favicons belong in public/.
| Command | Action |
|---|---|
bun install |
Installs dependencies |
bun run dev |
Starts local dev server at localhost:4321 |
bun run build |
Build your production site to ./dist/ |
bun run preview |
Preview your build locally, before deploying |
bun run astro ... |
Run CLI commands like astro add, astro check |
bun run astro -- --help |
Get help using the Astro CLI |
The project includes a .vscode/launch.json with pre-configured debug profiles. Open the Run and Debug panel (Ctrl+Shift+D) and select a configuration:
- Dev: starts
bun run devwith the VS Code debugger attached. Set breakpoints in.astroand.tsfiles and hitF5. - Build: runs
bun run buildunder the debugger, useful for diagnosing build-time issues in content collections or image processing.
HotFix.Day © 2016–present by Rishav Dhar · Code: Apache 2.0 · Content: CC BY 4.0.