A public page that is black, empty, or stuck loading forever is not just a UI bug. It is a trust bug. Readers do not care whether the cause is an API error, cache, routing, D1, CDN, or deployment to the wrong project. To them, the site failed its basic promise: opening a readable page.
DSTS therefore needs a strict rule: no public page may remain in a loading state forever. Every surface must produce one of four clear outcomes: render real content, render static fallback, render a clearly explained pending state, or return a proper 404 when content does not exist.
Fallback is not secondary content
In a public system, fallback is part of the product. If an API fails, D1 has no data, or dynamic content is not ready, users must still be able to read foundational content. Fallback should not be a few casual lines. It should be complete enough to protect user experience, SEO, and trust.
Routes must tell the truth about their state
Not every route should be indexed. Some routes have enough content and can be indexed. Others should remain noindex when decisions are pending. The important point is that the route tells the truth: live, read-only, pending, or not found.
Smoke testing is the minimum contract
Smoke testing does not replace deep QA, but it is the minimum contract before calling a deploy safe. It must check status codes, content markers, real 404s, sitemap/RSS/robots, and noindex routes staying out of sitemap.
No black pages is the lowest standard, but it cannot be negotiated. A project that speaks about human development, integrity, and transparency must begin by not leaving readers in front of an empty screen.