K Adam White
K Adam White
This guide will address one of our top FAQ, and should explain how easy it is to query for specific sets of posts, including - [ ] How to filter...
http://v2.wp-api.org/extending/internal-classes/ and https://developer.wordpress.org/rest-api/extending-the-rest-api/controller-classes/ should be merged -- there is overlap in the content, and it is unclear how the current handbook page is useful to an API developer.
Referenced issue: `slug` field is saved HTML-encoded WP-API/WP-API#2243, others are not. This can be counterintuitive and should be called out in the documentation.
See WP-API/WP-API#2657 for the relating discussion: One of the conventions of the WordPress REST API is that if a value is undefined for a specific key that should be part...
This is a common issue (WP-API/WP-API#2432 WP-API/WP-API#2497), and the snippet here https://gist.github.com/danielbachhuber/8f92af4c6a8db784771c (copied below) should be provided within the documentation site itself. ``` php
As noted in #47, not all resources for which we generate the docs using a template are really comparable. Some require authentication, others require contextual overrides for things like the...
The layout of the handbook makes our generated documentation minimally-useful. mrMark in Slack proposes summarizing some pieces of information for each endpoint in the start of each reference page: 
apedog proposes, > Perhaps a small tutorial. Saying archives.php template translates to endpoint /rest/?my_archives=whatever/. And offer the non-dev wp user some common endpoints he might want to have a look...
Proposals from docs-focused API team meeting on Jan 2, 2020: - Move **Key Concepts** into its own page - Add some API basics: - The API exposes information about your...
Per discussion in [core slack](https://wordpress.slack.com/archives/C02RQC26G/p1573221259119600), it's not obvious how to take advantage of the selective inclusion field logic. This should be documented in "extending the API" under writing your own...