As we dig deeper into what the Fields API can and should be, we’ve touched on some intriguing topics. From datastores to CRUD functionalities, our discussions are aimed at ensuring that the API is not just powerful today, but remains relevant and adaptable for the long term. Your feedback and input are invaluable in shaping the future of this project.

I started working on a very rough PoC earlier this week, and it helped me form an opinion on how I think the fields API could work. I think there’s some pretty good ideas here that would allow us to implement the fields API without disrupting WordPress backcompat.

This is a very early look at a potential solution to the fields API. This is not ready for actual review. I’m pushing early mostly so we can talk about some of the things in the PR and see if there’s significant problems. Approach The idea here is that there is a central singleton registry […]

This PR introduces a new document to the fields API that illustrates how to build a sidebar in the post settings section sidebar in the block editor. The goal of this PR is to help add visibility on one of the many ways in which a field is used inside WordPress.