The public site now uses an application-owned delivery layer. The useful question is not whether the idea sounds persuasive. It is whether it helps someone understand the work, make a decision, or complete a task with less friction.
What is happening
A generic file server can display pages, but it does not provide a strong boundary for future APIs, database content, or application behavior.
This tends to become visible at the boundary between the organization and the person encountering it for the first time. Internal familiarity hides effort that remains obvious to a customer, reader, applicant, or collaborator.
A practical response
FastAPI now owns the route manifest, page assembly, cache policy, health checks, and the extension point for future data-backed features.
The aim is a smaller, clearer system: one source for the record, one visible hierarchy, and one next action that behaves as expected. That approach improves the immediate page and makes later application or database work easier to add without rebuilding the public surface.