There has been much written about the ~drama~ discussions surrounding the WordPress REST API and inclusion in core. Or exclusion, depending on who’s take you are reading. 1 Suffice to say, the gist I’ve gathered is that there are two competing perspectives, one side wants to incrementally add the API, the other wants a fully fleshed out, complete API before inclusion in core.
I guess my 2¢ on the matter is this—the core tenet of the WordPress Foundation is “to democratize publishing through Open Source, GPL software.” From what I’ve gathered reading on the subject, the REST API team have the publishing portion of the API covered and ready for inclusion in core. The parts that would come (much) later would be things like the customizer, file editing, more site management tools, less about actually publishing.
If democratized publishing is still the guiding principle for WordPress the project, then I don’t see how there is any debate. Opening up the methods to publish beyond what has been the only means available for basically the entire life of the project seems like a no brainer to this guy who’s been around it for 11 years this year. No one will truly know how much is opened up until it is in the hands of creative developers and then in the hands of content creators.
- I’m specifically not linking to any of the hot takes on the subject. ↩