Skip to content

Query Panel Design / API (Latest Posts, Calendar, etc) #2662

@folletto

Description

@folletto

In #1594 we explored the idea of having a "universal" Query Panel that any block and plugin could reuse. The general idea is to provide an easy way to execute queries (WP Query) so any block that lists posts, pages, or other content type could use.

Benefits:

  1. Any developer that needs to get content in their block, can simply implement it, without having to program the UI from scratch.
  2. If WordPress updates and there are upgrades to the UI of the "Filter Content" panel, every block that makes use of it will get automatically upgraded too.

Cons:

  1. I can't see any cons to this approach, except deadlines: we might want something VERY simple to start with, so Core and new block plugins can use it, and then start upgrading it over time as it can blow up in a fairly complex UI.

Notably this means having a v1 added to Gutenberg soon, so blocks and plugin developers could use it, and with following iterations we can rely on the common API to upgrade it.

Metadata

Metadata

Labels

Needs DevReady for, and needs developer efforts[Type] EnhancementA suggestion for improvement.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions