A static site is a useful constraint. The build has one job: turn content and components into files that can be served quickly.
The shape of the system
This test site keeps the moving parts visible. Markdown is the source of truth, Astro renders the pages, and Nginx serves the generated output. There is no application server waiting behind a request.
That makes the deployment boring in the best way. A push builds an image, the image contains dist/, and the web server does not need credentials or a database to render a page.
Why the constraint helps
Build-time validation moves mistakes earlier. A missing title or description fails before a visitor finds it. A link to a post is a regular file path, so a broken route is easy to inspect.
The trade-off is that publishing is a build operation. If content has a future date, a scheduler must trigger a new build when that date arrives. The system stays simple, but the boundary is explicit.
Make the smallest reliable system that leaves room for the next useful feature.
This is intentionally a small example, but the same shape works for a much larger collection of posts when the build is measured and the content pipeline stays disciplined.