The static generator is completely hidden to the end user. They log in, click add new post, add some text, style it in Markdown or HTML, upload a few images, ad

The static generator is completely hidden to the end user. They log in, click add new post, add some text, style it in Markdown or HTML, upload a few images, add a few tags and click publish. Forestry commits the changes and Netlify runs a build. All the user sees of this is that their new post is now published. When I first started using static sites I would have agreed with you: there's no way I'd hand a normal user a markdown editor and a git repo and expect them to get on with it. But these new services do, in my opinion, solve the experience problem. However Wordpress is really good if you want to leverage the module ecosystem and do more complex stuff further down the line. Having used Wordpress for years I get excited about static sites' speed, simplicity and lack of constant security updates but it's not a one size fits all situation.