The first version of a public research site benefits from a thin server. It keeps the feedback loop fast while leaving room for richer data, auth, and agent surfaces later.
The tradeoff is that routing, metadata, assets, and caching become explicit. That is acceptable here because those choices are part of the product language: small, legible, and easy to change.