Docs: Create a Full Site Editing overview document #31065
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Size Change: 0 B Total Size: 1.49 MB ℹ️ View Unchanged
|
|
I am not convinced that the navigation and widget screens are best included here. |
carolinan
reviewed
Apr 22, 2021
carolinan
reviewed
Apr 22, 2021
carolinan
reviewed
Apr 22, 2021
carolinan
reviewed
Apr 22, 2021
carolinan
reviewed
Apr 22, 2021
carolinan
reviewed
Apr 22, 2021
carolinan
reviewed
Apr 22, 2021
|
It might be out of scope but I think this page should be removed https://developer.wordpress.org/block-editor/how-to-guides/block-based-theme/block-based-themes-2-adding-blocks/ |
|
There is also this page about templates that could be moved to an easier to find place: |
|
@carolinan I also noticed that one of the block theme pages isn't showing up in the directory. I'll try to get this cleaned up but I might do in a couple of different PRs to focus the work. |
|
I removed the adding blocks page, which I think will fix the currently unlinkable block theme overview, which I also added a link to in the overview document. The tutorial can use updating, please the block theme overview, but I think we can leave those for other PRs. So this should be ready to ship 🚢 |
Yes, I think we should! Great snag. Reviewing the rest of the doc now. |
mkaz
force-pushed
the
docs/add-fse-overview
branch
from
399c9a7
to
4706d66
Compare
Creates a new getting started document for full site editng. There are numerous sections and sub-projects for FSE, this document will gather together these resources and link off so people can find what they need. Closes #30637
Thank you for fixing my embarrassing typos :-) Co-authored-by: Carolina Nymark <myazalea@hotmail.com>
- Cleaned up some of the phrasing - Added in a few more links - Made it clear to test with a test site - Added context around nav/widgets + the vision for FSE
carolinan
approved these changes
Apr 24, 2021
There was a problem hiding this comment.
I am not sure how to test the link changes, but I think the content is ready.
But I wonder if there really needs to be both a theme and block theme section under how-to guides, or if this could be combined under Themes.
I am not that found of the "Theming for the Block Editor" heading.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Creates a new getting started document for full site editng. There are numerous sections and sub-projects for FSE, this document will gather together these resources and link off so people can find what they need.
@annezazu, I've stubbed out the start to this page and included a user portion to the outreach program.
I would welcome any additional links, sections, comments, details, or anything else you think we can add here.
Open Question: I updated "block-based theme" to just "block theme" - from usage I believe this is the direction we want. Do we need to be explict about this? It is easier to not change if we are fine with both.
This addressed concerns and closes #30637
How has this been tested?
View rendered document on branch here
Documentation:
Types of changes
If we rename, we will want to submit a redirect update to meta trac.