I don’t have much to add to the discussion but wanted to voice my dissatisfaction with Gutenberg and how it disrupts my recently discovered IndieWeb power (Webmentions). I considered switching to Jekyll, Hugo or Grav but ran into challenges migrating over 15 years of content and several thousand posts.

Reply to Blog Engines and Indieweb Controlling Upstream by Brad Enslen by Chris AldrichChris Aldrich (Boffo Socko)
I’m aware of the disruption of the Gutenberg Editor within WordPress v5.0 and how it applies to those using IndieWeb technology on WordPress. I’m sure it will eventually get sorted out in a reasonable fashion. Sadly, throwing out the baby out with the bathwater as it comes to WordPress and IndieWeb may not be the best solution for many people and may actually be a painful detriment to several hundreds.

Same. Manual until it hurts meant that the the process, time and effort of posing content often took longer than the creation of the content.

Indie WYSIWYG: How I Fixed My Instagram Problem by Alex Kearney
There's a saying in the indieweb community: manual until it hurts. Don't automate what you're doing until it's so painful that you're compelled to automate. It'll take time to maintain the code that's replacing your manual--software rots.

 

This is a very subjective principle. What hurts one person is painless to someone else. The problem with this ideology for me: I'm lazy. If it's not easy, it's agony.