|
|
|
|
|
|
by noahtallen
2098 days ago
|
|
|
I think this is an easy misconception to get from the article. But react is just used for instances of the editor inside of WordPress admin because editors are extraordinarily dynamic and interactive. I would suggest that editors are one of the best examples of things that should be SPAs! Any “front end” HTML is generated via PHP. No relation to react :) indeed, most of the accessibility issues with WordPress are in gutenberg itself, not the front end content. (When I say front end, I mean stuff you would see browsing the site as a normal user.) > are they being disenfranchised by the modern frameworks? Though this isn’t exactly your point, this is brought up a lot in relation to gutenberg. The reason gutenberg needs something like react is because it needs to be a lot more powerful than a simple text form. And it needs to be a lot more powerful because many WordPress users struggled to accomplish anything other than basic text formatting in the classic editor. Gutenberg is moving a lot of disparate concepts under the same roof now, and it provides / will provide a uniform, standard way for editing many parts of your site. While yes, this is a technology shift for developers (you need to be a lot more comfortable with JS to build tools for the editor), it’s still a big win for users who aren’t developers as they can accomplish much more with less effort and knowledge. Sure, some things might be a little more effort now than they were previously due to rough spots in the experience, but overall it unlocks a lot more functionality in the long run. |
|
|
yeah, and i hope it'll make the myriad mutually-incompatible page builder plugins die out. yuck. [1]
i'm a bit torn about GB... the goal of allowing tree-ish structures that map to nested DOM elements is great (and something TinyMCE, the old editor, didn't really allow). but the editor needs work. right now, it simultaneously goes too far (everything is a block => editing simple linear text is annoying) and not far enough (editing nodes and moving them around still feels clunky).
and i wish they'd gone with "everything is a node" instead. right now, inline elements are very much second-class citizens – they have to be "formats" within a RichText, a separate non-block thing [2]. they work fine for bold, italics and even links, but they're much more limited than blocks (can't remember specifics now though)
---
[1] if i sound bitter... i am, having had to untangle messes people made with some weird page builder thingy and work with themes that come with their own bespoke page builders (!)
[2] seriously, npmjs.com/@wordpress/rich-text is a package independent from Gutenberg (though it lives in the same monorepo)