The assumption that Wordpress means a client can edit their own site has been very wrong, for many users. Unless the site is built in Microsoft Word (and I've seen that done..) they are going to be using a professional for edits, and hence I refer back to static builders.
We're solving the CMS issue for our users. Just import your Jekyll/Hugo repo. Forestry will automatically generate an index.html file (it's a CMS in a React.js file) and deploys it to your static site. Now, non-technical users can log into your static site at site.com/admin/ and see a powerful CMS.
I definitely have some regrets from this approach instead of just picking a CMS that already exists, and if I were in a similar situation in the future I'd probably start comparing preexisting CMS options.