The quick inserter has a standard border (outset) that is #ccc.

With the addition of the 'browse all' button in black at the bottom it creates an unfortunate fuzz between the black button, the gray border, and the black box shadow:

We should instead use an inset border like `borde

Describe the bug:

Using the provided serialized block content, the block fails validation when it previously did not.

To reproduce:

<!-- wp:coblocks/map {"address":"Scottsdale Arizona","pinned":true,"height":534,"align":"full"} -->
<div style="min-height:534px" data-map-attr="/qaddress/q:/scottsdale arizona/q||/qlat/q:/qundefined/q||/qlng/q:/qundefined/q||/qskin/q:/qstandard/q||

It would be cool to have an additional parameter when creating a BlockStory to allow to create stories for Mobile as well as Desktop.

I'm not sure wether we should just have a Boolean to toggle between mobile & Desktop, have an array of different possible screen sizes or just pass through the viewportWidth to the BlockPreview component.

I could see a need for an admin alert when Gutenberg is turned off for all post types just so a user is aware. It could be set to be dismissible forever. I think some feedback on activation of the plugin would be nice.

The text could be something like:
`Notice: The Gutenberg ramp plugin has disabled Gutenberg on the post, pages, ______, _______, etc. post types. If you would like to activate

We want to have our interface for gutenberg project in Portuguese.
File with strings to translate in json is here https://github.com/openzim/gutenberg/blob/master/gutenbergtozim/l10n.py and you should add you locale here : https://github.com/openzim/gutenberg/blob/master/gutenbergtozim/export.py#L40