Could you elaborate? I’m specifically interested in the comparison to alternative approaches. You need a tool to create a blog site anyway, so what makes a JavaScript framework more “over-engineery” than a server-side or build-step approach?
Blogs typically don't have complex state that's worth keeping and managing on the client.
SPAs have extra complexity to get all the things working properly that work on multiple pages by default. E.g. I have to immediately think of this recent thread about a SPA blogging platform: https://news.ycombinator.com/item?id=20494114 - and I see broken pages like that all the time.
I get that client-side rendering can be a problem if JavaScript is disabled or fails to load and execute, but that by itself does not mean that singe-page apps are over-engineered. On the contrary, I’d argue that a single-page app is the simplest (least complex) approach to creating a blog site with some interactivity.
With the server side rendering, it is able to detect browsers where javascript has been disabled and then render html-only pages.
So whether it means anything or not, server side rendering can service a wider audience than can client side renderers.