• This is great!

    There are some possibly valid concerns from developers here, about things like backwards compatibility, plugin compatibility, custom fields, code efficiency, etc. I expect that some of those concerns will be addressed before this is ready for primetime, and that other things will be improved over time.

    Much of the panic I’ve seen in the one-star reviews, however, seems completely unfounded to me.

    There seems to be lots of work that still needs doing, but this is exactly the kind of thing WP needs.

    I also expect that theme and plugin developers will be able to add their own blocks, as well as disallow/turn off blocks that you wouldn’t want ordinary content creators to use. (If that’s not on the roadmap, it needs to be.) That should go a long way towards both assuaging people’s fears and allowing them to customize this to their needs.

    I would have preferred even more WYSIWYG than I’ve seen so far, though. (Maybe adding a simple option to use the same fonts, weights, and colors as the site itself. Or maybe even adding a way to switch to something like front-end editing mode. Or maybe just rethinking how previews are done.) But that’s a small point in such a big project.

    All in all, this is very promising. Keep it up.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Tammie Lister

    (@karmatosed)

    Thanks for leaving a review and it’s great to see you are so excited by Gutenberg. You are right, we are working to address all concerns. It’s a learning process as a team but we are trying. Thank you for testing Gutenberg.

    The WYSIWYG and more ‘page building’ elements will come in once the editor shifts to the customization focus. That will happen after 5.0. It’s going to be exciting to see what the team focusing on that do.

    “Much of the panic I’ve seen in the one-star reviews, however, seems completely unfounded to me.” it depend for what you use wordpress. if it is for blogs and small web site, it is not a problem…

    if you must apply many style CSS to many object and many pages, a visual builder is not a good thing…. the CSS/LESS/HTML/PHP teehncologies are conceveid in order to render web site easy to modify. you cant with gutenberg.
    try to change 10 element per page with inline style in a web site of 30 pages. good luck. the problem is that gutenberg inactives the page property ‘template’ and it’s so more diifficult to do that.

    also, if this plug-in hide funtionnality like options of the screen , custom fields, metaboxes, plug-ins like ACF, etc.. if you page don’t contain more than 4 columns…
    what sort of site do you build ? i dont understand

    my customers need all that things and with gutenberg today, i can’t provide that. maybe tomorow ? if this issues will be corrected. a lot of issues

    Thread Starter Chris

    (@nordtomme)

    Hi, @lcazprof.

    I haven’t been much of a developer in more than a decade, but as a marketer I use WP as a CMS for multiple clients, as a project manager I ask others to develop themes and customize WP sites, and –?yes – as a writer I use WP for blogging as well. I also work with a handful of other CMSes. Comparing WP with them, I still think the change Gutenberg represents is (over)due.

    To address your comments briefly:
    Maybe I have misunderstood, but I don’t think this is intended to be a “visual builder” as much as a content editor. I.e. it’s not Elementor or Squarespace (which I agree would be terrible), just the old post edit screen evolved beyond TinyMCE and the most clunky metaboxes.

    As far as I can see, Gutenberg really doesn’t add or remove very much functionality. Screen options and some meta boxes are gone, but all the functionality seems to still be there. It looks most like an upgrade in how to add and work with things like headings and blockquotes –?which will make it easier for my clients (and yours?) to work with those things without tinkering too much with the formatting, juggling custom TinyMCE styles, having to go into the code view, use a bloated plugin with poor UI, or do other things that make content production complicated to do or easy to screw up.

    I can not see where ?Gutenberg inactivates the page property ‘template’?. I’m not entirely sure what you mean, but as far as I can tell, you can still use page templates and post formats to wrap, style and present the content like before. Maybe you are confused by a demo, like the one I saw, without sidebars or other distracting content.

    But at least on my test site the page templates still work as expected, and all the relevant classes were added to the body tag – so you should be able to use all the same css and js you’re using.

    As for the styling: Why are you using inline styles?

    Most blocks added by Gutenberg have easily understandable standard classes added to them (.wp-block-verse, .wp-block-quote and .blocks-quote-style-1, .wp-block-column, etc.). Also, the interface makes it easy to add custom classes to any block you want to style specifically. Combine that with body classes and templates (ref. above), custom blocks and options (ref. below), etc. for full ability to customize.

    After all that, it seems like Gutenberg outputs exactly the kind of clean, semantic code you’d expect from a great CMS (which is head and shoulders above many/most crappy WYSIWYG page builders with their bloated code and randomly named classes and IDs). But it does not try to replace the role of the theme.

    I haven’t tested Gutenberg with ACF, but Gutenberg seems to allow developers to create their own custom blocks, with all kinds of custom functionality, options, and fields. This seems like a great opportunity for Elliot Condon and ACF, as well as other plugin and theme developers, to create even better things than before.

    In the hands of a good developer, I suppose Gutenberg might become and be used as a good, custom-built page builder –?but only if that’s the purpose. And it would still let you style all elements (or none, if you wish) according to the theme.

    And while this is admittedly a big change to the post edit UI, I don’t expect that WordPress will allow much of anything into the core unless it is, to a certain degree at least, backward compatible with earlier versions of WP and the most popular plugins used by millions of sites around the world.

    I am sure they are very aware that for years to come, a huge percentage of all content on the Internet will have been composed in the old WP UI, and they won’t want all those pages and posts to stop working when people upgrade.

    Your fears seem based on an assumption that Gutenberg is being developed by isolated shut-ins who don’t understand what WordPress is being used for. I don’t think that’s true. In fact, it seems the team leads all work for Automattic. While they might not know everything that everyone is doing with WP, I think it is fair to say that they’re not completely in the dark, not entirely new to this, and not oblivious to the billions of dollars Automattic and their clients have riding on this being done right.

    Who knows, maybe they’ve even made a few custom-built sites for clients themselves in their time? ??

    But I might, of course, be mistaken about all of this, and about how Gutenberg is intended to work when it is finished…

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘The right direction for WP’ is closed to new replies.