Next, we delved into the pains, tools, patterns, etc. used in the following ongoing efforts:
- Porting the media library and TinyMCE into the Customizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. with Media and Text widgets
- Creating new and revised UIs leveraging the REST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. like Quick Drafts and New List Table
@timmyc talked about his experiences developing the new Media Widgets, which are all built utilizing
wp.media. @westonruter has created a great summary of some of the bumps they had along the way.
@joemcgill added the overall architecture of wp.media is not well documented anywhere, so there’s a huge barrier to entry for anyone who wants to work on even minor bugs. It’s not simply understanding backbone, but you also have to understand how wp.media has implemented a custom frame/region/state model.
Discussion continued around the reason developers find working with media and other core JS so difficult. Is it the complexity? The lack of documentation? Or is the architecture itself the problem? Probably all of the above.
Discussion continued to backward compatibility, and the issue of “losing” PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher hooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. when we switch old functionality from wp-ajax to the REST API. Do we need to provide backward compatibility for all PHP hooks? Or can we offer new approaches for developers to extend WordPress, for example,
wp.hooks? @omar shared their experience at Yoast when they switched their content analysis from php to js.
As a reminder to contributors that there are over 300 open tickets in the JS focus that can use your help!
For a full transcript of the meeting, check the slack logs.