Static site generators are bad for dynamic websites, but that does not mean you have to try and fit a whole dynamic platform into a static website. Different use cases, different tools.
And, that's false. Unless you make them run one of your restricted platforms that doesn't have the features they want and need for their business.
Wordpress runs 60% of CMS websites. 15% of the most viewed websites run Wordpress.
> You only need to worry about security issues if you build such a site on top of a dynamic platform.
Do you actually believe that there are no security issues with static websites?
Thank you for the conversation, but I'm going back to running my business.
Wordpress has 1 click install for all those things as plugins (or work out-of-the-box)
What most people want is to have something that works, where they can focus on their content and not on your tools. Wordpress works for people.
If they get a CI/CD pipeline maintained by someone, how do they create pages, get updates, fix those pesky security issues, write a blog post on their mac that when saved automatically gets posted? How easy is it to apply a theme to your CI/CD pipeline? Your tools work for you, but are you going to maintain them with the same level of features as Wordpress?
Oops, it's holiday time, will you write a greeting card plugin for your CI/CD pipeline for them to purchase cards on their website and send site-specific cards to their email list by Monday? No? Sorry, they just switched off of your CI/CD pipeline to Wordpress.
When moving to a different hosting provider, people want to conduct business not learn a to use a new CI/CD pipeline to match the tools at the new hosting company.
What about when you get tired of updating their site generator code for them? They will need to start over, and they won't pick another CI/CD tool that's unmaintained and is expected to get horribly outdated after a year.
People go into business in order to conduct business.