Imagine someone creates an open-source, JavaScript admin interface for their WordPress site and names it after a greek demigod. You’re probably thinking wow, that’s so cool, I wonder if I can make it work on my site. But then you start thinking about all of the custom metaboxes and other types of custom forms that plugins add to the post, term, and user edit screens. There is no standard for metaboxes or for declaring what fields a plugin has to use. Making something that “just works” with everything is increasingly more complicated. Custom API-driven interfaces remain the territory of those who can afford to build and maintain bespoke solutions. Many people, including myself, have talked extensively about an API-driven future of WordPress. In the first article I wrote for Torque on the REST API, I reiterated what WordPress lead developer Andrew Nacin told the audience at WordCamp Milwaukee in 2014: the best projects for contributors to become a part of if they wanted to be a part of the future of WordPress were the REST API and what was then called the metadata project. Part of the REST API is now in core, and the metadata project, now known as the Fields API project, has made great
Share This