The core team works on improvements for the settings API. It should become easier for developers to use the API and the accessibility of the generated markup should be improved.
Improving the settings API
On January 2 and 16, the core team held meetings regarding the settings API. One aspect to tackle is improving the settings page’s accessibility — currently, table markup is used. The other aspect is that developers have to write an own callback function even for the most basic fields. The team wants to add support for various field types, so this will not be necessary anymore.
REST API sites endpoint for multisite
/sites/ endpoint should meet the following requirements (quoted from Jeremy Felts post):
/sites/endpoint should provide a useful set of data for each site without requiring the use of
- It should be possible to query
/sites/for something other than ID, domain, and path.
At this moment, the
/sites/ endpoint is limited to the fields from the
wp_blogs table. Things like the site’s name or description are stored in an own table for each site. Because the use of
switch_to_blog() would be inefficient, a new table was proposed to store several data of the sites. After some discussion, these are possible data for the table:
- »Customization Meeting Notes: January 23, 2017«.
- »WordPress 4.7.2 Security Release«.
- »Dev Chat Summary: January 25th (4.7.2 week 2)«.
What are little blocks made of?
In his post »What Are Little Blocks Made Of?«, Joen Asmussen showed two mockups. One shows paragraphs as blocks, the other the possibility to add other content. That and more should be discussed at the meeting on January 25.
At the meeting, it was determined to start with building prototypes as soon as possible, to answer further questions. Furthermore, it was discussed, how to add inline images inside paragraphs, over-blocking, and more. Ian Stewart’s comment provides a summary.