> Great, but we have entire essays demonstrating how WYSIWYG is garbage Markdown is great and all, I personally use it mostly for README docs and git tracking.

> Great, but we have entire essays demonstrating how WYSIWYG is garbage Markdown is great and all, I personally use it mostly for README docs and git tracking. But WYSIWYG is what most blog sites are embracing Examples (but not limited to) - Medium - Ghost → Ghost 2.0 - Webflow + Design tools - Notion + Notetaking tools - Premade website tools (WIX, squarespace, Shopify Page Builder, etc) are gaining ground over wordpress traditionally WYSIWYG has a learning curve associated with it, but it doesn't have to be complicated. Personally, I prefer GUI tools over non GUI counterparts anyhow. These include tools in atom/visual studio code for doing git commits / branching etc. People are more than willing to learn how to use a WYSIWYG interface if the value they get long term is worth it. Ideally, cost should be minimized (learning) and benefits maximized(building quick blog posts how they want). Blogs are exactly that though, you spend a little bit of time learning the framework, and spend a lot of time using it. The amount a user is willing to learn proportional depends how much they will use it long term. For a one off task, a user is not willing to spend as much time learning a WYSIWYG GUI tool, and would rather pick something more familiar like markdown or .txt. Examples include learning how to use a new video editing tool, with advanced feature sets (Adobe Premiere, etc) if you don't make videos often. Rather you would prefer learning a simpler tool instead (Adobe spark, etc) From research I've done the market is largely shifting towards WYISWYG and from a UX research standpoint, this makes sense. Getting exactly what you want lowers the barrier and confusion / expectations of what you receive. You can quote buzzfeed essays all day, but I always take research with a grain of salt unless (1) the author is reputable (2) it validates research and data I've observed from a number of various reputable sources / my own research. UX is just common sense at the end of the day ------------------------------------------------------------------ > The frontend needs complex information to be able to correctly produce a beautiful design Not necessarily true, just use a CSS framework and it simplifies a lot of the process. Take your pick with functional CSS like tailwinds, bootstrap, or just modify your own classes. WYISYWG just wraps things in classes as necessary I've looked at Gutenburg, it looks promising. I've spoken to a number of core devs from gutenburg. I don't really like the tinyMCE editor that much honestly, or the Jetpack installed wordpress.com instance. They both have issues. TinyMCE editor doesn't reflect proper nominal width for a blog at ~800px, so sometimes the results are skewed when previewed live Jetpack wordpress.com's editor is more closer to what optimal words per line / font-size / width to write should be. However, it has some serious flaws when using 3rd party plugins (such as adding prismJS code snippets) and its a pain to work with