Gutenberg: Full Site Editing Breakdown

Created on 11 Mar 2020  路  6Comments  路  Source: WordPress/gutenberg

This is an overview of the concrete tasks needed to proceed with the project scope of Full Site Editing (FSE).

Part 1

Framework (Infrastructure)

  • [x] Replace EntityProvider鈥檚 and useEntity* hooks with the Block Context API. https://github.com/WordPress/gutenberg/issues/19685 @aduth
  • [ ] Theme local assets #20966
  • [x] Fix template parts saving behavior #21512 @epiqueras #21766
  • [x] Support separate entity "block controllers" in the block-editor @noahtallen #21368. (Fixes various issues with undo & dirty state caused by the block-editor store thinking that everything belongs to the same entity.)

Edit Site Interface

Small Enhancements

Site and Post Blocks

Part 2

Framework (Infrastructure)

  • [x] Load the appropriate FSE template on the post / page editor #21086

Interface

  • [ ] Rethinking the "Current Document" display and settings #20877
  • [ ] Mosaic View of Theme Templates #20477
  • [ ] Add link to templates and template parts listing in site editor #21246

Blocks


Global Styles

Refer to this issue instead https://github.com/WordPress/gutenberg/issues/20331

[Feature] Full Site Editing [Type] Overview

Most helpful comment

This is an excellent prioritization of tasks. I am excited to start drilling through!

All 6 comments

Moved the _Grid_ block to the second wave so we can focus a bit better on the initial pass.

@youknowriad @mtias - has anything related to #21218 / #21219 been discussed / triaged towards work here yet? I have noticed these problems and they seem important, but I hadn't noticed anything discussed about them yet so I opened the issues noted above.

It was meant to be covered by #19254, though that issue took a spin towards the grid block that wasn't the intention. It's useful to break it apart anyways.

This is an excellent prioritization of tasks. I am excited to start drilling through!

Two issues/tasks stand out to me the most here because they are very foundational and require material framework changes.

Theme local assets #20966

The scope here is a lot broader than it first seems. Things like localization will have the same issue that dynamic URLs have, that our level of granularity for defining dynamic content areas is too coarse, it's entire blocks. I wrote about a possible solution here, inline "blocks". Ideally, we arrive at a solution that paves the ground for the next phases of Gutenberg.

Add a Query block #20106

The Query block will be the block editor counterpart of writing a WP_Query and rendering "the loop" in PHP. This is a foundational part of the majority of layouts and especially important because all templates should essentially be rendered under an implicit Query block computed from the current URL.

We also need to pay a lot of attention to pagination as it should be easy to separate sibling Query blocks by static content and have one continue the other's loop.

This issue served us well to implement the first iterations of Full Site Editing. We're trying to split this work into well-defined milestones in #24551. So I'm going to close this issue in favor of that one.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

aaronjorbin picture aaronjorbin  路  3Comments

cr101 picture cr101  路  3Comments

spocke picture spocke  路  3Comments

wpalchemist picture wpalchemist  路  3Comments

ellatrix picture ellatrix  路  3Comments