Build Time

Build time is the phase where your source code, templates, and content get processed and transformed into the final files that browsers can actually display: optimized HTML, CSS, and JavaScript. For static site generators like Astro, this means every page is rendered, every image is optimized, and every content entry is validated before the site ever goes live. This all happens once, ahead of time, rather than on the fly each time a visitor loads a page.

The Simple Version

When you write code for a website, browsers can’t always read it directly. It needs to be compiled (translated) into plain HTML, CSS, and JavaScript. Build time is when that translation happens. You run a command, the build process churns through all your files, and out comes a folder of finished web pages ready to be served.

Think of it like cooking. Your source code is the recipe and raw ingredients. Build time is the actual cooking. The output is the finished dish that gets served to guests (visitors).

Why It Matters

With static sites, everything is built once, ahead of time, rather than being assembled on the fly every time someone visits. This means pages load faster because the server is just handing over pre-built files instead of doing work for each visitor.

Build time is also when errors get caught. If a blog post is missing a title or a link points to a page that doesn’t exist, the build process can flag it before the site goes live.

How It’s Used on This Site

Running npm run build triggers the build process for this site. Astro reads all the components, blog posts, and glossary entries, then outputs static HTML files. Vercel runs this same build automatically whenever code is pushed to GitHub.