When the repo is already React
React when the public HTML has to be the product
Stackologists builds in React when the team already owns JavaScript, and we treat how the pages get published as its own decision, so the answer is already in the HTML document when it ships.
We use React and Vite for product UI and for public sites that have to be readable on the first request. When search is part of the job, we pick the render plan before the first component: prerender, static HTML, or a deliberately client-only surface that stays out of the sitemap.
When we pick React
- The team will keep the product UI in JavaScript.
- A marketing or research surface can be prerendered.
- You’re migrating off a client-only shell that search can’t see.
What “HTML is the product” means here
A React shell with an empty document isn’t done as far as search is concerned. Public routes need the answer in the first response, and signed-in chrome can stay on the client. It’s the same split we use on Angular and Blazor: different runtime, same rule.
When we pick something else
A C# team with no JavaScript owners should use Blazor — Blazor vs React is the decision note. A long-lived enterprise app on Angular should stay on Angular unless you have a reason that isn’t boredom. And a Microsoft estate that only needs an API should hire .NET developers on that page.
If you already run React, we’ll staff or build inside that repo. We aren’t going to invent a rewrite to win the work.