Support » Plugin: Gutenberg » Great for bloggers, but concerned for the CMS (Updated)

  • First of all, kudos to the team for the work they’ve done, this was never going to be easy.

    The interface definitely feels more modern than TinyMCE and for your average blogger, the added flexibility added by the blocks will be great. No doubt WordPress.com users will see the greatest benefits here.

    As a developer who creates sites for companies, however, I have major concerns about the impact this will have. For many people, myself included, the post content is only a minor part of the editor. Metaboxes and custom fields are far more important, and these seem to have been relegated to an afterthought.

    In addition, while the block editor is great fit lone bloggers, in general I would like to be able to restrict client access to the layout and design elements of their site.

    All in all an interesting project, but metaboxes need to be prioritised before this goes anywhere near core.

    UPDATE:

    I’ve spent some time with the latest version and I’m very impressed with the progress made. The templates option (https://wordpress.org/gutenberg/handbook/templates/), particularly the option to lock a template for a post type, are very useful for allowing clients to edit content but not order. If this is expanded to page templates, and Gutenberg is updated to include easy developer support for allowed/disallowed blocks (again per post type and page template), most of my worries about its use as a CMS are sorted.

    I think there is still a high barrier of entry into developing blocks, compared to the comparatively easy page/post templates and shortcodes API, but I’m not sure if anything can be done to mitigate that save clear and helpful resources. Guess I’ll just need to git gud at JS rather than clinging to PHP.

    EDIT 2:

    Development is unfeasibly complicated to do the simplest things. Creating a shortcode takes one minute, creating a custom block requires an occult ritual and multiple tears. Especially if you’re trying to save meta.

    • This topic was modified 12 months ago by  Joe Bailey-Roberts. Reason: Impressions of the latest version (3.1.1)
    • This topic was modified 11 months, 3 weeks ago by  Joe Bailey-Roberts. Reason: Block development makes me cry
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Tammie Lister

    (@karmatosed)

    @sephsekla first thanks for posting a review. It’s important to get feedback about Gutenberg. Metaboxes have a solution today – although that’s being iterated on also. I’m glad to see you see this as an important project.

    @karmatosed while there is metabox support, it’s definitely spotty at best.

    Metaboxes are arguably the most important backend component of professional level WP development.

    They need to be integrated well, not just tacked on to the end as a concession to legacy support.

    Again, no slight on the cool editor work, but it’s not the_content() that makes WP such a powerful CMS.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Great for bloggers, but concerned for the CMS (Updated)’ is closed to new replies.