Create a new handbook page for curating the editor experience #42022
Conversation
This proposes a v1 of a new page that compiles various methods for curating the editor experience.
annezazu
requested review from
ajitbohra,
ryanwelcher,
juanmaguitar and
fabiankaegy
as code owners
|
Noting that I definitely added the visuals incorrectly (didn't see the assets folder). I'll try to figure this out now :) |
Had to speed this video up in order for it to be small enough to include.
I can't seem to figure out why the video won't properly render. When I look at the individual file, it seems the size is still too big to display. If I don't add it to the assets file and just drop it in, it works though.
|
I can't seem to figure out why the video won't properly render. When I look at the individual file, it seems the size is still too big to display. If I don't add it to the assets file and just drop it in, it works though. If anyone can help here, that would be rad :) |
|
|
||
| Beyond defining default values, using theme.json allows you to also remove options entirely and instead rely on what the theme has set in place. Below is a visual showing two extremes with the same paragraph block: | ||
|
|
||
|  |
There was a problem hiding this comment.
I think the URL of the image already needs to point to the path of the image once it has been merged to trunk.
There was a problem hiding this comment.
Ah! Okay. Let me update that :) I just was worried they wouldn't appear if I reference them in trunk without them being there first. Makes sense though.
There was a problem hiding this comment.
Updated but, as you can see now, the images don't show up. I guess that's what has to be done but I'm not sure what folks have done previously.
Not sure if this is the right way to resolve a conflict with trunk but this is my attempt :)
|
You need to run |
@annezazu I took the liberty of rebuilding the docs and pushing the changes up. |
Similar to #42022, this proposes a v1 of a new page that discusses how best to manage propagating updates to your site. The aim is for an initial version to be shared that can then evolve over time to be more comprehensive as needed.
* Create a new handbook page for propagating updates Similar to #42022, this proposes a v1 of a new page that discusses how best to manage propagating updates to your site. The aim is for an initial version to be shared that can then evolve over time to be more comprehensive as needed. Assistance from @justintadlock @gziolo @juanmaguitar @ryanwelcher. * Update manifest.json for new doc * Update toc.json for new handbook page * Text updates * Updating the blocks section Updating based on great feedback from @gziolo. * Updating bolding and headers Updating the structure of the doc in light of @juanmaguitar's feedback. * Updating title of page * Updating manifest.json with new title * Rebuild docs. Co-authored-by: Ryan Welcher <[email protected]>
What?
This proposes a v1 of a new page that compiles various methods for curating the editor experience. Thanks to @justintadlock @carolinan @bph for chiming in/reviewing! In the future, I'd love to see a section with specific recommendations for Agencies and Enterprise level folks. My hope is that an initial version can get out into the open and folks in those spaces can contribute back with use studies, feedback on what would be helpful, etc.
Why?
Right now, the information around how best to curate the experience/tailor it to your needs is spread across multiple different resources. This seeks to pull them into one place and explain how they each can be used.
Please help with this PR!
I still struggle at times to get things in place for new docs so, if you're game to help, it would be lovely for folks to contribute to this PR both to move it forward and suggest changes.