A big consideration is "how much are you duplicating?"

There's a big divide between template-oriented tools and component-oriented tools.

Template-based tools are usually page focused — whether this is Rails or Jekyll or whatever — there's usually a view representing the current page, calls into partials or template helpers for items on that page, and some series of nested layouts that that page is rendered inside of.

Component-based tools focus on the composition of UI elements. Angular element directives, React components, Ember components — apps are build out of more-specific components consuming more general components atomically, until you have a page.

Traditionally the argument has been "well how much interactivity do you need?", but I think the question needs to start being "how much are your styles something you're duck-typing to from a hodgepodge of server side templating and client-side UI frameworks?"

The answer is always "it depends", but there's a lot of appeal to the self-contained component thing as a building block for web publishing, whether it's a static site or a rich app. React is especially suited to this, as a tree of React components can be rendered either to a live DOM, or as a big string.