https://github.com/WordPress/gutenberg/issues?q=label%3A%22Needs+Dev+Note%22
These are all the PRs that need Dev Notes to be written for. Let's write them, share them here as comments, see what is related, and create make/core posts accordingly. Please let me know if you're unable to write a note for our PR. The notes should be posted before WP 5.5 RC, but the sooner, the better.
@youknowriad
- [x] Block patterns: https://make.wordpress.org/core/2020/07/16/block-patterns-in-wordpress-5-5/
- [x] Remove the old block preview implementation #21096
@aduth (These need to be taken over, cc @WordPress/gutenberg-core.)
- [x] Block API: Allow block registration without category #22280
- [x] Block Editor: Change default URLInput autoFocus to
false#19973 - [x] Blocks: Update default block categories #19279
@gziolo
- [x] Block API: Add new utility to register block types from metadata in PHP #20794
@nerrad
- [x] Convert _experimentalCreateInterpolateElement to a stable api #20699: https://make.wordpress.org/core/2020/07/17/introducing-createinterpolateelement/
@tellthemachines
- [x] Resizable editor experiment #19082: https://make.wordpress.org/core/2020/08/04/new-editor-preview-options/
Unmarked
- [x] Block API: Add Block Context support #21467 (see https://github.com/WordPress/gutenberg/blob/master/docs/designers-developers/developers/block-api/block-context.md)
- [x] REST API endpoints: https://make.wordpress.org/core/2020/07/16/new-and-modified-rest-api-endpoints-in-wordpress-5-5/
- [x] Block Tools: https://make.wordpress.org/core/2020/07/27/new-block-tools-on-wordpress-5-5/
- [x] Image Editing: https://make.wordpress.org/core/2020/07/20/editing-images-in-the-block-editor/
ellatrix
All 28 comments
There's a few of these that are still experimental, in that case, we shouldn't write a dev note for them but leave the label for later when the API is made stable.
youknowriad
on 3 Jul 2020
Block API: Add new utility to register block types from metadata in PHP #20794
As part of that, we should also update https://github.com/WordPress/gutenberg/blob/master/docs/rfc/block-registration.md and move to the final location.
gziolo
on 3 Jul 2020
What's the deadline for the Dev notes to be written? I can write one for createInterpolateElement but knowing the deadline will help me plan when I write it.
nerrad
on 3 Jul 2020
@nerrad Something like a month (before RC) but the sooner, the better :).
youknowriad
on 3 Jul 2020
There are some issues reported about “Enqueue assets for rendered blocks only” (#22754) and it feels like we should revert it. If we don’t find a working solution for all cases on Monday, we should postpone it to WP 5.6.
gziolo
on 4 Jul 2020
@gziolo Are we depending on it for anything? If not, perhaps better to be safe and revert? It seems quite tricky.
ellatrix
on 5 Jul 2020
22754 was reverted with https://github.com/WordPress/gutenberg/pull/23708 and moved to WordPress 5.6 in the corresponding core ticket.
gziolo
on 6 Jul 2020
Here's a dev note draft for the resizable editor/new preview options:
New editor preview options
You can now preview editor content in different screen sizes. Replacing the old preview button there is now a dropdown with “Desktop”, “Tablet” and “Mobile” sizes, as well as the previous front end preview option.
The new preview options currently only work on medium to large screens (>= 600px). In the future, there may be a way to preview large screens on a phone.
Block developers
If you’re a block developer and would like to have responsive styles for your blocks in the editor, use the #start-resizable-editor-section and#end-resizable-editor-section markers to define responsive styles. Styles between these markers will be picked up by the editor and render correctly when it is resized. As an example, this is what your styles would look like:
#start-resizable-editor-section {
display: none;
}
/* add all responsive styles here */
#end-resizable-editor-section {
display: none;
}
Currently, we aren’t able to manipulate theme editor styles because they are loaded inline in a
Most helpful comment
I noticed that the
URLInputautoFocusdefault prop value was announced as a change pending in WordPress 5.5, but the associated pull request #19973 was never merged. I don't think it's going to be part of 5.5?I'm having a hard time recalling what was preventing #19973 from being merged, aside from fighting with the test suite.