3 Comments

  1. Peter Knight

    The widgets API, the shortcode API and now Gutenberg all overlap and all have similar objectives. All of these efforts ideally would have sprung from work around the fields API. I do hope that all the different efforts come together so that in the end we get both a modern UI and a more consistent, easier and more powerful way to create and register components.

    In an ideal world it should be fairly easy to create a component that can be adapted to work as a shortcode, block, widgets or meta field on any type of page, without having to use very different APIs.

    Report

    • Anh Tran

      Totally agree. WordPress has so many APIs for similar things. Wherever a form and fields, there is an API: meta box, comments, widgets, shortcodes, terms, settings pages and even customizer. Each of them was implemented with different purposes and thus, APIs. Not only the API, the way WordPress handles the data is different, too. It’s not only add extra works to developers, but also waste a lot of time for users to just learn to use.

      I hope Fields API can resolve this problem by providing an abstract layer between what really happens with the data and what users see.

      Report

    • Matías

      Well said. Gutenberg is not trying to change how data is stored—quite the contrary. WordPress flexibility and power is something we should preserve and expand. The main goal, and the spirit behind content “blocks”, is to raise the user experience side of what WordPress is already capable of to the modern expectations of visual manipulation of content, and to overcome issues generated from fragmentation of input at an interface level.

      Blocks don’t make fields obsolete, it should make them easier to use down the road. The next steps are indeed what you described, since a block could store data in meta fields, in separate post types, in the content, in site settings, etc; it just becomes a visual implementation of a meta-box that gives richer manipulation capabilities, while retaining the flexibility and power.

      I’d consider Gutenberg an attempt at systematizing how users can interact with their data in a visual way, wherever it may be.

      Report

Comments are closed.

%d bloggers like this: