Let’s discuss: What if you could register custom post types and custom fields directly in the WordPress admin?

The first tutorial in a two-part series that introduces the Block Bindings API in WordPress 6.5. Part 1 focuses on custom fields.

Learn how to create a custom dynamic block that saves information to custom post_meta and creates a one-to-one experience in both the block editor and on the front end. You will see an example of how to to use @wordpress/create-block package to scaffold a block.

Starting in WordPress 5.8 release, we encourage using the block.json metadata file as the canonical way to register block types. Here is an…

Display a meta field as a block on the frontend, supporting ACF fields.

The WordPress block editor (a.k.a. Gutenberg) communicates with the database via the WordPress REST API. We can read and write post meta from within the Gutenberg editor after we enable the specific post meta field in the WordPress REST API.

One of the most common questions I get is "why aren't my custom fields showing in my WordPress?" And living by the rule of not repeating myself, here is a

gutenberg-fields-middleware - Register fields for Gutenberg blocks with less repetitive code

Gutenberg Custom Fields allows you to control the content of the Gutenberg edit screen by creating pre-filled templates.