Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Full Site Editing Breakdown #20791

Closed
41 of 53 tasks
youknowriad opened this issue Mar 11, 2020 · 6 comments
Closed
41 of 53 tasks

Full Site Editing Breakdown #20791

youknowriad opened this issue Mar 11, 2020 · 6 comments
Labels
[Type] Overview Comprehensive, high level view of an area of focus often with multiple tracking issues

Comments

@youknowriad
Copy link
Contributor

youknowriad commented Mar 11, 2020

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

Part 1

Framework (Infrastructure)

Edit Site Interface

Small Enhancements

Site and Post Blocks

Part 2

Framework (Infrastructure)

Interface

Blocks


Global Styles

Refer to this issue instead #20331

@mtias
Copy link
Member

mtias commented Mar 24, 2020

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

@Addison-Stavlo
Copy link
Contributor

@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.

@mtias
Copy link
Member

mtias commented Mar 30, 2020

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.

@epiqueras
Copy link
Contributor

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

@epiqueras
Copy link
Contributor

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.

@youknowriad
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Overview Comprehensive, high level view of an area of focus often with multiple tracking issues
Projects
No open projects
Development

No branches or pull requests

5 participants
@youknowriad @mtias @epiqueras @Addison-Stavlo and others