Rendering strategy decided by the page, not the project
Different pages have different obligations. A marketing or catalogue page has to be indexable and fast on first load, which argues for rendering on the server and caching aggressively. An authenticated dashboard has neither obligation and can favour interactivity. Treating this as one project-wide decision produces either a slow marketing site or an over-engineered application. We choose per surface, use incremental regeneration where content changes without user input, and keep the client-side payload under review, since it is the most common cause of a fast site becoming slow over a year.