> I can't think of any reason why more tooling can't develop to address that concern. This is what a dynamic CMS basically is. Tooling to work around the deplo

> I can't think of any reason why more tooling can't develop to address that concern. This is what a dynamic CMS basically is. Tooling to work around the deployment process of a static site. WordPress became the norm because of its plugin system and its ability to scale. Creating a static site works well if you are a developer capable of writing the code or a single person writing nothing more than a small blog. A system like this would not scale, for example if you wanted to add some dynamic content such as comments or an e-store. At that point your static site simply falls apart. For a non-developer, writing or getting someone else to write all that code is an expensive proposition. WordPress, even with paid plugins, is way much more cheaper and hassle free for the job. And the WordPress admin page is a website accessible from any device with a web browser and does not require a setup of development tools on said device.