This is clearly not the problem that Gutenberg aimed to solve.
The problem it solves is more what your second paragraph mentions: “how do I insert custom content that isn't just text in a way that looks consistent on the front and back end”?
Adding complex content in a visual way is a real problem in pre-Gutenberg WordPress, to the extent that a thriving cottage industry of page builders now exists, each with their own take on how to add and edit content.
Gutenberg hopes to remove the need for such page builders in many cases, (and eventually) unify the WordPress (and Drupal) community so they can offer custom content types as native blocks under a common API.
For relational content, there are still custom post types and taxonomies.
> IMO Wordpress could do a lot more for itself long term by improving the flexibility and power of its core, rather than its WYSIWYG.
It's doing that too, with the REST API, with WP-CLI becoming a “blessed” project, and with future plans for Gutenberg as a means to control widgets and other site areas, rather than just post content.
> Adding complex content in a visual way is a real problem in pre-Gutenberg WordPress
It's not an actual problem though, is it? That cottage industry already fulfills the needs of those the subset of users that need more than what the tinymce implementation WordPress offers out of the box.
It's better to understand Gutenberg not as a problem solving project but as a reaction to two things that the project leader has trained his focus on.
First, there's this premise that everything is moving to javascript and php is legacy, so WordPress should evolve to run on javascript while casting aside PHP somehow. Fail that and the project could go under is an anxiety that exists.
Second, there's the itch for WordPress.com to compete on more level terms with the state of hosted solutions like WIX, Weebly, Squarespace who offer increasingly simple visual building experiences. This is where wp.com wants to compete and win new users choosing between other hosted providers. Mullenweg wants to have WP be an even bigger monopoly. These are two anxieties driving Gutenberg.
Gutenberg channels energy toward accomplishing a conversion from a PHP-centric project to a Javascript one, while making a play for new users who are choosing between the hosted version of WP and other hosted solutions.
On a technical level, Gutenberg doesn't really convincingly solve technical problems. It makes it easier for developers to tack on GUI driven content elements, which was possible before, but something that many developers didn't get right or didn't know how to do.
It doesn't provide a better WYSIWYG experience. The editor screen and the front-end are going to look and feel very different. The biggest new obstacle to arriving at a better WYSIWYG is the fact that in Gutenberg the interface markup is a first class citizen, with the content merely existing deeply nested inside its components in editing mode.
While editing, every paragraph, every image, every element is surrounded by endless amounts of divs and scaffolding. When designing a document's CSS you style according to the markup that is shown to users, now with Gutenberg you have to take into account the fact that while editing elements are nested deep inside a convoluted set of divs. So we're still storing messy blobs, but now we're going to split up those blobs and add more mess while in editing mode.
Sure it is.
If the first thing thousands of users do after installing WordPress is to pay for a page builder plugin to be able to work with their content in the way they want, that's a problem — it's a sign that the existing editor does not meet their expectations for how a modern CMS/blog platform should let them work, which makes it a good candidate to be solved in the platform itself.
And if completely new users struggle to format content without frustration (I have watched many people trip with the “Classic” editor in new user orientations on simple things like adding and positioning an image or video), that is also a problem, because it affects their first impressions and gets in the way of whatever their personal or business goals are.
Gutenberg is aimed at solving both of those real problems; I think on the whole it does it well, and it's enlightening to see how positively some people react to it:
https://twitter.com/antpb/status/1052996833264455680
> The editor screen and the front-end are going to look and feel very different.
You can style the editor with CSS, and re-use much of your front-end theme styles in the editor stylesheet via Sass. This is how the upcoming new default WordPress theme (Twenty Nineteen) already works: https://github.com/WordPress/twentynineteen
> So we're still storing messy blobs, but now we're going to split up those blobs and add more mess while in editing mode.
The “mess” in editing mode is needed to help people style their content more intuitively; you can't have a WYSYIWYG web UI without adapting the page content with scaffolding to enable styling controls.
There are some big and entirely valid criticisms around Gutenberg (accessibility support, general PR issues, release delays), but “not being designed to address a real user problem” isn't one of them.
It will take a lot of time to address all issues and turn the community around to it, and this is just the start.
Or, it's an opportunity. Look at Shopify - is it a problem that the first thing a new Shopify user does is to head to the Shopify app store to buy and install a handful of plugins?
Also worth noting there is no official WordPress.org paid plugin store and paid plugins are typically not hosted services as with Shopify.
The average experience WordPress users get when shopping for, maintaining, and getting support for plugins is much less smooth than a hosted platform like Shopify. (There are great WP plugin developers and terrible Shopify ones too, but fewer of the former than the latter.)
Understanding the priorities in play explains in part why Gutenberg is causing friction better than saying it exists because it is trying to solve technical problems for users. That would lead you to think that the technical problems were thought about really hard and that is some primary goal. It's not. It's just WordPress trying to modernise an interface.
> You can style the editor with CSS, and re-use much of your front-end theme styles in the editor stylesheet via Sass.
The reason I bring up the editor and WYSIWYG is that it shows the disconnect between some lauded goal of providing a more seamless experience and the thought that went into the technical solution. My feeling is that we ended up where we are not because we were trying to solve a problem in the best way, but because we were just trying to cram in a new JS way of doing things. It explains better how we arrive at the following mess. Let me show you it through the lens of styling a post:
> The “mess” in editing mode is needed to help people style their content more intuitively; you can't have a WYSYIWYG web UI without adapting the page content with scaffolding to enable styling controls.
Look at the gallery I posted and tell me honestly, are you really saying this is the only way to provide 'intuitive editing'? Of course that is not true, it's simply how Gutenberg decided to implement it. Of course, you can compose your CSS workflow to fit around how Gutenberg's editor functions and you'll get fairly good results if you do. But this is a workaround, it's made the UI a first class citizen at the expense of the rest. So theme developers have to think in terms of the UI, not just what the markup looks like on the front-end. And content creators are forced to think in terms of blocks. It's an UI that is altering how people interact with it, for its own sake.
To me they reveal a couple of misconceptions:
1. That a WYSIWYG should provide a pixel perfect like-for-like view of the front end on the back end.
As you mention, the theme you chose doesn't have full Gutenberg styling, so front and back end differences are more pronounced. But even themes that have good integration will display differences, because the back-end cannot perfectly model the front if users are going to do more than manipulate data inside it (i.e. change styling).
I do agree that there are other ways to provide more intuitive editing (like in-place editing), but they are not without downsides too. In-browser editing is a compromise and balancing act.
2. That the structural blocks around visual elements on the back end designed to enable UI elements and controls interfere with styling by theme developers in some way.
That was definitely my experience at first (I've just spent three months updating several themes for use with Gutenberg), but it isn't now that Gutenberg has evolved and I better understand how editor styling works. In short:
- You enqueue your editor styles after calling add_theme_support( 'editor-styles' ); with add_editor_style( 'style-editor.css' );
- You can then copy the bulk of your styles from the front end to that stylesheet (with a few exceptions, such as the post title, which do need editor-specific wraps at present).
- Gutenberg/WP 5.0 prepends those styles with a block-specific selector when you view the Gutenberg editor so that you don't need to worry about the “soup of UI markup”, as you put it.
- You can automate much of the CSS re-use using Sass, like the Twenty Nineteen theme is doing.
Theme developers need not think about the extra wraps unless they are developing custom blocks, and even then it's largely abstracted away for them by the JS API.
I would much rather have editor styling handled automatically by Gutenberg, and I think it will get there, but for the moment this is a small stepping stone on that path.
You bring up how Gutenberg solves some of the issues it creates, i.e. how theme developers supply editor styles to match what is seen in the front-end. Until recently Gutenberg didn't even prepend block specific selectors, it was even more broken than now. Why did it even start out that way? How is that even possible to have Gutenberg develop that far without properly thinking about how to style for it? Why is it this solution patched on? (same can be said for meta fields, accessibility and so forth). Because the project didn't start with a clear idea of the technical problems it wasn't going to have to solve, it wasn't a priority.
So, for theme developers Gutenberg is more labour intensive (though it can be rewarding). It wouldn't need to be more labour intensive had it started with the full breadth of priorities in mind at the very start. You say 'you don't need to worry about the soup of UI markup, but you do. You have to work around the quirks of the editor or constrain yourself. Say you want to target every 2nd heading, or the paragraph after a blockquote, you can't do that elegantly, because the markup is different in the editor as it is in the front-end and it's not solved by prepending block selectors. Gutenbergs editor styles solution isn't elegant either. It is not a complete disaster, but it's indicative of the fact that the project is imposing its own paradigm over the problems its trying to solve. It's literally creating new problems to solve.
> they are not without downsides too. In-browser editing is a compromise and balancing act.
I'm not convinced at all that a different approach to how the UI manifests itself in the DOM would have entailed any meaningful trade offs at all. I've been working with this prosemirror implementation recently and the basic example pretty much matches my demo posted earlier: https://tiptap.scrumpy.io/
WordPress has always been a project where user happiness outweighs developer happiness, though, as much as I'd love for it to at least bring developer happiness inline. It will be interesting to see what the overall reaction is when 5.0 lands and the editor starts to become more widely used and accepted.
And Gutenberg's development is precisely characterised by developers/designers prioritising their own happiness. It's a small group of people working mostly at agencies and companies doing enterprise level work who took Matt's idea around blocks and feverishly adopted the tools they personally wanted to use while developing and making decisions at a pace more rapid than other contributors could cope with. That is in part why we lost the accessibility lead.
What's the difference between "compete on more level terms with the state of hosted solutions like WIX, Weebly, Squarespace who offer increasingly simple visual building experiences" and "solve problems for users". If there is something that is making people choose WIX/Weebly/Squarespace, isn't that something precisely: a problem that those things solve and default wordpress (currently) doesn't?
I've long emphasised the symbiotic relationship .org has with Automattic in positive terms. Up until fairly recently I would say this relationship was almost wholly to the benefit of the overall project. My impression is that WP.com under your leadership is now behaving more like other conventional tech companies - it's preoccupied with growth. That preoccupation with growth by implication operates in the context of wp.com competing with other commercial companies who compete for the same customers.
When I look at the success of WordPress through the years, I'm seeing growth arriving as a side effect, not as a specific end unto itself. Decisions were made because wrong or right, they seemed like a better, more powerful way to do things. When it becomes about growth, other things become a little less important. Through the lens of the need for growth, options are judged to the degree to which they are vehicles for further growth. Unfortunately this also leads to relaxing other principles that should be central to WordPress.
Before React changed its license, it had already heavily adopted for Gutenberg and Calypso and you had been poised to bless it had there not been so much turbulence. It was adopted because it had been the fastest way to move forward. The same militant zeal that was applied to 3rd party developers using non-GPL licenses was not applied to the adoption of React, because React was a useful tool in the pursuit of growth. Of course, you can say, but it's now a success story because I've no doubt that FB's change of license was influenced by WP. Community consensus was however a second order issue, as was the original licensing, what matters was what would make the people working for you happiest and most productive in the short term. (Credit to you, you were willing to abandon React at one point, that must be noted)
WordPress will soon be adopting AMP in core, given your support. Again, immediate growth will be the primary reason this happens, because AMP is the fastest way to cut down on bloat that is holding back performance for mobile users and users on slow connections. It's a shortcut, it's a shiny looking vehicle to continued growth, delivered on a plate by some of the worlds best engineers. This decision won't be made based on community consensus or a discerning look at whether it's good for the open web, or what other options there are. It will be stressed that AMP is developing web standards and is an open source initiative with many other players that have bought in, saving the web and helping poor users.
Because growth is the imperative, things that hinder growth are treated with the same baseline hostility as red tape is to businesses. Accessibility and privacy are inconvenient obstacles that ultimately need to take a backseat to building forward momentum, rather then the very means with which to democratise publishing and development.
Because growth is front and center, artificial time pressure needs to be created with which to force the issues. And like a conventional tech company that has grown into a monopoly, it starts to take advantage of its privileged position. It becomes aware of its own latitude, like now the ability to introduce a degree of breakage and concentrate all core development on the delivery of a flagship feature.
I'm seeing this and I'm thinking, many of the decisions that are being made are at best following the letter of stated principles, but not the spirit. Each decision can be somewhat rationalised and the pretense can be offered that it's in the interest of increasing the pie for everyone, or to reaching more users, general survival and for spreading OSS practices even further.
What I'm seeing is a web of monopolies that are interacting in such a way that their influence continues to grow. To have the web shaped by a few select players is not good at all, and I certainly haven't worked with WordPress all these years because I care about market share. I was motivated by the degree to which WordPress empowers people, how it brings people together and champions freedoms as well as its role in keeping the web open and independent. Now it's a slave to growth, nakedly pursuing monopoly status, boosting the role of problematic monopolies elsewhere while selectively applying its stated principles.
I have enormous, genuine respect for people working on WordPress, including you and the many people that work at Automattic and elsewhere. I believe strongly that every single person involved is working with the best intentions in mind. But the prioritisation of growth has corrupted the character of the project, and I can't express in words just how sad that makes me.
Thank you for recognizing we were willing to walk away from React because of the license. It was chosen because of technical merit originally, but was a day or two away from delaying the entire project 6+ months to refactor.
AMP is interesting but no decision has been made there yet.
Thank you for sharing your thoughts and a generally excellent comment.
So free users don't want the features that paying users want? Whyever not? Surely the fact that some people are willing to pay for a particular feature indicates just how important that feature is to a lot of users.
From what I understand, it's better WYSIWYG. Great, but we have entire essays demonstrating how WYSIWYG is garbage. Alright but people want WYSIWYG!
To me, this seems like a manifestation of the limits inherent to the simplification of UI. The frontend needs complex information to be able to correctly produce a beautiful design. Ultimately, the user needs to be aware of the concepts (too complex, apparently), or the design needs to be automated and therefore simplistic. WYSIWYG is the unhappy compromise demonstrating that consistency begets complexity.
If this dilemma really is unsolvable, then Wordpress is but one of iteration in a grand cycle of its victims. I worked mainly with Drupal, and the situation there isn't much better, they've simply opted for sophistication over usability.
I would dispute all of those essays.
Explain to me what we do instead of WYSIWIG and if your answer is anything like Markdown then you've never observed real users.
Hell - I hate markdown and I'm a developer. I do not understand the desire to trash WYSIWIG other than reverse Ludditism.
You can find an essay demonstrating everything you care for is bad.
Engineering requires measurement and proof, not essays.
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
Oh boy would you be surprised. The whole reason we do research is because users consistently break our expectations, in the most uncommon ways.
I can tell you why I do it. I host a couple of WP instances on my server. One for a non-profit sports organisation I am involved in and one for my mom. In both cases I look after the WP install itself (config, updates etc) and they deal with all the content. WP provides a UI that is easy enough for them to use to do so. I am certainly not interested in building anything “custom” for them.
I think you need to think beyond personal and marketing blogs. WordPress is much much more...
Quartz (qz.com) is built on WP. So was Wired (wired.com) and The New Yorker (www.newyorker.com). I had a hand in both The New Yorker and Wired and may other large media companies are built on WP.
To characterize it as a "simple blog engine" is mis-leading.
Gutenberg, while having its teething problems, is a big change. Big changes will cause upheaval. It will cause both petty and important disputes to rise to the surface.
I think this is no different.
agreeing with sibling, WordPress _is_ a blog engine that has been twisted and squeezed to support other things. BuddyPress is probably the ugliest manifestation of this, one of the slowest, sluggiest, buggiest things I've ever touched.
I praise the extreme simplicity of the WordPress database structure, but that is also a very serious limitation.
Examples if issues:
- WP is ridiculously rigid when you want to scale it - that is due to having it's file storage as and actual file storage, without any abstraction.
- The media library is an utter mess since the backbone.js mockery added in 3.5, with inconsistent use of filter and hooks on backend vs frontend.
- It's forcing compatibility with long dead PHP versions. (5.2. That is before namespaces.)
- I only supports MySQL but maintains MyISAM compatibility, so no foreign innodb keys, no cascade delete, no nothing.
It should never have wished to become other, than a blog/small website engine without first making long, long overdue backend fixes.
But instead, for many years now, I'm seeing the community being neglected; features that are questionable, pushed through (emojis, REST API, Gutenberg); WP.org without a clear focus, and without answering decades old threads, like a database abstraction layer.
All that said, WordPress is easy to use - but I'd welcome an extremely simple, WYSIWYG, small, static site builder instead, with proper support for media, portfolios, galleries, with a WordPress importer, which could easily take over the mess, that WordPress, my once loved CMS had become.
</rant-ish content>
I guess my point is... how would you break down the functionality of those sites by Wordpress core, themes or plugins, and custom code? How much of what makes those sites great comes "out of the box" from Wordpress, vs being bolted on or written from scratch?
We used off-the-shelf plugins for for curation/features: ACF, EditFlow, Yoast (SEO).
We also used custom Plugins for building out curation and full content feeds for our iOS app, managing podcasts, and AB testing.
Quartz was different. We only relied on the WP editorial UI (with EditFlow plugin) and simplified the templates to just deliver JSON (this was before they had the JSON-API in core).We built an independent web app on top of that.
Hope that helps answer your questions.
The very idea that people try to host e-commerce on the platform is an embarrassment and a shame to security and safety.
It encourages the pattern of hiring non-technical staff to manage the blog-store-landing-page-franken-whatever site, who are in turn encouraged to install reams of untrusted code via plugins.
It is built on a frankly bizarre pattern of page and route management. It uses broken versions of a fairly broken language. It is enormously resource-hungry.
I could go on, but to sum up, my experience working with WordPress has been nothing but a repeated nightmare.
1. Static is secure. Wordpress is a notorious target for hackers and I see constant attacks even against my empty, worthless Wordpress site. But you can't attack a site that doesn't take any input or perform any logic besides choosing which page to display.
2. Markdown is simple and does the job. I don't need anything fancy to write my thoughts and link to resources I find useful.
3. I find Jekyll to be more flexible than Wordpress. Technically both can be used to make any kind of static site, but I find the customization friction to be lower with Jekyll.
4. I like the built-in version control I get with git/Github.
5. I like editing my site with an IDE where all files from content to style are intuitively accessible rather than navigating Wordpress' interface.
6. Github pages includes HTTPS and DDOS protection that I don't need to think about (or even know about). It's just built in.
7. It's in keeping with the open source spirit to have my personal site open source. Anyone can go in and look at what I'm doing, how I'm doing it, and even the history of how the site evolves. They could even fork it if they really wanted to for some reason.
- Have a user friendly administration section that anyone can use regardless of technical expertise (by user friendly, I mean have WYSIWYG editor for all posts and make it extremely simple to manage content via a UI -- not CLI)
- Have roles for users with restrictable access
- Have a plugin ecosystem that allow just about any customization to be easy enough to implement that paying a freelancer to do so is quite affordable
- Have an entire theming eco-system that is very alive, with plenty of free or paid options to make a site look professional
I doubt we will ever see backend changes, like allowing postgresql database though.
Plugins: https://github.com/planetjekyll/awesome-jekyll-plugins
Themes: http://jekyllthemes.org/
But I do see your point.
Not the same market.
2. I personally prefer using WYISYWG, especially when I add images and code snippets. Having to view a markdown renderer means I have to look at two things, unless your using a partial markdown renderer instead on input side (stackedit.io, inkdrop are some examples).
3. Installing plugins in wordpress is easy. The way I do most things is fork entire repos, test it out, and see if its worth learning. This is how I approach wordpress as well, try X plugins disable them all see which works best. With jekyll you have to do install plugins / libraries yourself, I just want to get straight to writing though
4. Wordpress is just bandaid solutions everywhere for me, I only git track changes I make from a base theme (its all just CSS)
5. Wordpress's interface is awful to look at when using the editor in admin panel. But you get used to it. I'm debating in writing a quick javascript extension / userscript that I can toggle to disable all the clutter while writing
6. Had issues with wordpress HTTPS issues that sitegrounds had to fix the otherday, I still have no idea why I didn't have my SSL certificate installed
7. As much as I like opensource, I do a lot of things closedsource.
Wordpress is great for me b/c I can customize it very quickly, do bandaid solution plugins and backups everywhere, and just focus on writing. I don't like reinventing the wheel or building my own tooling if I can avoid it.
Jekyll has always given me build errors in a windows OS environment since its based on ruby. What I had previously is using github-pages and deploying it live to see changes. Still learning netlify. Commits were extraordinarily messy for me actually, I would have 1000+ commits and 990 of them were just minor changes to draft posts. I could probably use seperate branches but out of the box, everything went to master branch
It separates the CMS from the front-end and has a very good API to get the data from the CMS.
Grav is cool, if you need PHP you’re good with flat file.
Off topic, but my most fav CMS of all time is definitely Umbraco. It’s built on .NET, but it’s insanely fun to work on.
Between all three if these CMSes, I cringe when I hear “Wordpress.”
If you've ever had to deal with out fo date, page builder generated shortcode messes, that is actually a problem that people would like to solve :D
Like, a standardized way of creating a mess is much better than 10 unstandardized ways to make a mess, right? But that's most of modern JS and PHP work anyhow :D
Because for whatever reason, people are failing to realize that Blogger is vastly better.
This is good for bloggers and wordpress.com but adds nothing for anyone that used WordPress as a base platform for something different.
It's the something different that differentiates it from SquareSpace.
https://www.manton.org/2018/10/23/wordpresss-gutenberg-vs.ht...
There are as many sites still on Magento 1 as 2 which they would want to avoid.
And I suspect this is the case with quite a few recent WordPress changes to be honest. The people behind it don't want to be seen as the folks making the 'beginner' or 'amateur' CMS, they want to be up with the 'cool' kids working for Google/Facebook/Netflix/Airbnb/whatever with React and Vue and Angular and what not. For them, stuff like Gutenberg (and arguably even the REST API) feel like attempts to move WordPress away from the 'CRUD sites for small businesses and non programmers' market to the 'professional' one.
Yet that's exactly where the market is for WordPress, and that ease of use that attracted beginners and lower end agencies is why WordPress got so popular in the first place. You didn't need a lot of experience with frameworks and build processes and MVC structures and what not to get started, you could just copy or hack together some simple code to get things the way you wanted, and use third party themes/plugins to do the rest.
Trying to make things more complicated or move the core of the system over to a JavaScript framework basis (as some suspect Automattic may be trying to do) will just kill a large part of the WordPress community, and remove the ease of use aspect that makes it so popular at all.
That's not a problem, Wordpress is literally a blogging platform.
> This is good for bloggers and wordpress.com but adds nothing for anyone that used WordPress as a base platform for something different.
If your application's scope is outside of a blog, Wordpress is the wrong tool for the job. There exists multitudes of frameworks written in any given language that follow the MVC design pattern (some better than others of course) to choose from.
Why does someone select Wordpress in 2018? Why even host a website at all? Because they want to build something custom. But because Wordpress core continues to be basically a simple blog engine, anything fancy has to get implemented as custom code and/or super powerful themes and plugins that are almost like mini CMSs unto themselves. This is where a lot of the security problems in Wordpress sites often come from, BTW.
IMO Wordpress could do a lot more for itself long term by improving the flexibility and power of its core, rather than its WYSIWYG.