Nik Tsekouras

>Quick question — does any of the work related to this issue require a dev note? For locking new APIs that never made it into core, we don't need any...

>When we stabilize an existing API and rename it by removing the __experimental prefix, would that be considered as an introduction of a new API? That's a good question. I'd...

@jasmussen I think the best way to check would be to just disable `Gutenberg` in a `6.1` installation. Since we tagged them as `core` patterns with `6.1` version, they should...

>Rather than trying to use a specific Gutenberg plugin for this PR, I followed what you said above and just disabled Gutenberg on a 6.1.1 install. At first, everything was...

>Looks like the pattern from the directory includes a ref, while the patterns deleted from this PR omit that. The ref'd menu 80 doesn't exist on your site, so it...

>This has been fixed in the pattern directory, so it should be good to go 👍🏻 (there might still be old patterns in cache for a few hours, in case...

>P.S. I noticed that some patterns like "Header with hero image" are rendered broken because the image fails to load. It seems we have the [same issue](https://github.com/WordPress/pattern-directory/issues/443) for Cover blocks,...

I'm going to merge this for now and handle [separately the link issue](https://github.com/WordPress/gutenberg/issues/47636) for `Cover` blocks, since these patterns are not even shown since the `core` keyword` has been added...

There are some nuances with block examples that are used in previews and I don't have strong opinion on this one, but some of the comments are also true for...

I'll merge this and we can create a different issue to discuss if we should change what BlockPreview shows - like reflecting the selected block. Thanks for the feedback all!