[smoe]

If your website/blog is primarily a website/blog I think Wordpress is a perfectly fine choice (maybe overkill for personal use, solid for teams of authors). For me the problem starts once one wants to start adding more web application like features to it. Obviously you can build everything on top of it, but you pretty much need specialized developers. WP development is just too foreign and unattractive for most fullstack developers I know. Also its database model can be a pain to deal with.

Don't know what the best solution is. I'm currently testing Strapi CMS on the backend with a NextJS frontend which should give me hybrid between pre-rendered/ssr as well as dynamic parts while having a consistent development experience across all of them that is very familiar to developers. Definitely not as quick to launch experience as slapping together landing pages in website builders and Wordpress with pre-made templates, but I'll see how it goes.

[ridings]

From the comments I’m learning the obvious. There isn’t one approach because there isn’t one problem.

This was a success because I really understood what I was solving for.

Each scenario will change and the solution will too.

TLDR of the article; what do you want?