Kelly Dwan

Is it expected that the openverse API response returns broken URLs, or are we doing something wrong in [the w.org proxy layer](https://github.com/WordPress/pattern-directory/blob/trunk/public_html/wp-content/plugins/pattern-creator/includes/openverse-rest-controller.php)?

As mentioned, this is coming from the Spotify embed block. Future patterns might use embeds from other 3rd party services. I tried some values for `sandbox`, but I would need...

Currently, the patterns sent to WordPress sites are those with the internal keyword "Core", or the category "Featured". Grabbing both should be good for an "official" set. But there are...

I un-checklisted the assumption list since they're not actions. From here, I see the action(s) as - [x] Create a wp.org endpoint that will serve patterns (#6) - [x] Import...

I think that's the right assumption - the only "style" options we should provide are the ones that have block support (global styles). I don't know offhand if there are...

For the pattern validation task, we shouldn't need a faux-browser environment (or even a WordPress site), just a JS env for Jest should be enough. I was thinking something like...

We can't really track installs, since patterns are more ephemeral - you don't really install them. We could track: - Number of favorites - Number of times (and reasons) reported...

Does that mean that the method of using a pattern will change in core? Whether it's copied from wp.org or added from the inserter in the editor, it's only content...

Try looking at [`postcss-discard-duplicates`](https://github.com/cssnano/cssnano/tree/master/packages/postcss-discard-duplicates) for inspiration on how to do this.

The flip side to this could be checking for repeated selectors - so this would return `[ .foo ]`. ```css .foo { border: 1px solid red; } .foo { display:...