@kadamwhite mentioned this issue on a Trac ticket I created, #28093: Widgets JS API:

If I can ask a question to clarify the intent here: it sounds like what is being proposed is (1) a Backbone re-write of the widget management UI, and (2) the addition of some endpoints for getting widget information via AJAX. The former seems to be the goal here, making it easier to add widgets to the customizer, etc, but this would require the latter in order to get and update information appropriately, correct? If so, I think it's important to be explicit about both components of the problem—the idea of a widget endpoint is also an open to-do for the json api project, #19, and in that project Ryan calls out that a widget endpoint also makes assumptions about a sidebar endpoint, sidebars relationships to themes, etc.

I'd like to see this happen, I just want to make sure the scope of the project is clear.

This makes a whole lot of sense. Any JS API for widget management would require an endpoint such as described in this WP-API ticket. The Backbone rewrite should then hook its models up to the widget and sidebar REST endpoints exposed by the WP-API. So yes, the Widgets WP-API is a prerequisite for #28093.

By the way, I worked with @danielbachhuber on a data model for Widgets for management via WP-CLI: wp-cli/wp-cli#728

Add widget endpoints #19

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions