- most formatting is based on
styleattribute which destroys website presentation style consistency - there is no easy way to customize editor toolbar and inspector
- it is impossible to add more than one class to a custom toolbar button
Now think how all of those hardcoded colors and font sizes in pages content match up with accessibility when you allow visitors to switch to alternative hi-contrast stylesheet or to resize website font with a button. And what about implementing inline Bootstrap button link that needs at least two classes? Forget about it.
You can easily avoid all of the problems above with TinyMCE but with Gutenberg it is now impossible by the design.
Every WYSWIG editor that uses anything else for formatting than predefined tags and class attributes is not modern but obsolete because it is based on bad coding paradigms that should be avoided to keep website Kosher.
Top comments (5)
True, Gutenberg has its flaws, but still it is better than Theme builders. With right setup Gutenberg can be a really useful for designing simple websites.
It is impossible to achieve what is critical: a proper HTML code without hardcoded styles and possibility to define custom elements with multiple classes. This makes it completely unusable for anyone who cares about coding standards. Gutenberg is like page builder from 90' – if it won't be redesigned it will die like those builders, because it's not generating simple pages, but just simple-looking pages with messed up code.
It's not gonna die. The WP community apparently loves it.
Personally, i stick with Advanced Custom Fields and create my own custom components. It's more restrictive on the user, but still has a Wysiwyg component they can use if i add it to a block for them.
Restricting your clients from screwing up a nice design is the hardest thing to do.
As far as accessibility and "coding standards", that's up to you since ACF means you can build a custom theme any way you want to.
Dude you are clueless. ACF is not a builder per se, and has nothing to do with this article. ACF is for building custom fields, and now in 2013 they have been bought and sold again, but now ACF finally supports building custom post types. Gutenberg is and will continue to be overshadowed by the current page builder market which continues to advance at a much more rapid pace and has a far larger community of programmers , website developers and content writers behind them. Gutenberg is written in very poor and bulky code. And it generates even worse code. It will have to change drastically or it will fade away eventually, and if you look at the history of the WP dev team, they will only take it so far then forget about it.
Could not agree more. but its clear your readers dont understand the importance of correct semantic html or styling things with CSS and the difference between Id and level elements etc. Gutenberg is pure garbage.