Depends on what youre using to host the html files, but you can probably deploy in two commands.

1. generate your files

2. copy these files to your host

Put these in a script, and your workflow becomes: update your content, then run your script.

My experience with Hugo through v0.17 was that it takes ~1ms per post to generate. IIRc that was one of the major reasons why the author wrote, vastly increase the speed of regenerating the site.

Right. But I can update my Wordpress site from my phone in China without a laptop running Hugo...

Maybe things are getting better these days (?), but at various points throughout its history, anyone could update your WordPress site from their phone in China.

Right, and that's a truly killer feature if you happen to need it.

Hugo doesn't address that problem at all, nor do Jekyll, which I currently use, and the other similar tools I've looked at.

However, the missing step there (of rendering the static site and publishing it) seems well suited to being done "in the cloud" then on the client device where the posting/editing/typo.

If you have a machine or VM on the Internet to use, this is not difficult to set up for yourself (any computer-proficient user with a little time can do it).

But doing that is also nowhere near as trivial as WordPress makes it (any person at all can do it).

That seems like exactly the gap Netlify wants to fill with their Netlify CMS (and a bunch of other options, depending on your exact needs).

Interesting; thanks. I just signed up for forestry.io (which I also learned of in this HN thread), I will check out Netlify also.

Some hosts like Gitlab Pages or Netlify will run hugo for you. So you can use an online git editor, save, and it'll deploy automatically.

Not Wordpress wysiwyg but still pretty nice.