Rich Tabor

> What I'd deem important is to show the yellow notice below the justified text option when selected, I'm assuming that's still present? Sure, I had missed that.

I say we include them all, even without legibility notices. Sure, it may not be ideal, but I can see it working in some cases. And I'm hesitant to have...

> As this PR won't address the above need and the alternative approach would also solve the may concern this PR addresses (i.e. finer control over opacity). I'd like to...

> Ideally, we'd reuse the background color support as is, if possible. From the UI side, I think the difficulty would be labelling the "background" control as "overlay" so its...

> Trying to unstick this, I want to ask a possibly obvious question: why would you ever untoggle "keep custom CSS"? Is there any use case for not keeping it...

I agree, this is pretty funky: Front of site:  Editor: 

How do we move this forward? I think we need to be more intentional about letting themes decide what patterns are feature, especially as we lean into the next default...

Yes, I think that will work too. I still think we audit what patterns we're serving (#587)—but notably, none will be featured in the Inserter.

I've found this to be funky all around. You can't open/close it without clicking first on the canvas between. May be related. https://github.com/WordPress/pattern-directory/assets/1813435/e2179fac-106a-446c-a87d-7471bd80eefc

> It is definitely not ideal— it worked when the directory launched, but as Gutenberg has evolved it's not kept up. What's the worse that can happen if we removed...