The decision to use Next.js was not driven by trends, but by practical constraints that became clear early in the project. The application needed to serve both marketing content and interactive user experiences, which made rendering strategy an important consideration.

A traditional client-side React setup would have required additional tooling to support SEO and performance goals. Next.js provided these capabilities out of the box, allowing rendering decisions to be made per page rather than globally.

File-based routing simplified navigation structure and reduced onboarding time for new developers. Pages, layouts, and components were easier to reason about, which improved overall maintainability.

export async function getServerSideProps() {
  return { props: {} }
}

Over time, the project benefited from clearer boundaries, better performance, and a codebase that encouraged deliberate decisions instead of workarounds.