amp

Bug Description

On an AMP-first site I ran across the following amp-img:

<!--noscript-->
<amp-img height="1" width="1" alt="fbpx" src="https://www.facebook.com/tr?id=413752866132374&amp;ev=PageView&amp;noscript=1" class="amp-wp-enforced-sizes amp-wp-6a19fc1 i-amphtml-layout-intrinsic i-amphtml-layout-size-defined" layout="intrinsic" data-amp-

Describe the bug
When a user chooses a background color or image on gutenberg the default color for the font is white. I would like for this functionality to be a bit smarter so if I was to pick white background overlay then the default font color is a dark color other than the white along with the pre registered background colors that make sense;

To Reproduce
Steps to reproduce the b

Feature Description

Inspired by this tweet from @Siddhart I was considering whether we could do something similar when selecting font color or text background color where we highlight recommended colors for a proper text c

When optimizer used in conjuction together with optimizer-express it's not possible to pass params to optimizer's transformHtml method, only configuration to the optimizer constructor.

And while some transformers honor those configurations:
https://github.com/ampproject/amp-toolbox/blob/efe5775c5ff93ebacd6f7bd336ba02d829eca579/packages/optimizer/lib/transformers/AmpBoilerplateTransformer.js#

Description:

Let's review the current HTML component to see if we can allow wysiwig instead of the textarea.

The challenges that I see:

• We need to keep the dynamic tags compatibility using the dropdown that we have right now.
• We need to load/instantiate the editor only when the component is viewed, not on customizer load or something.
• enable this for all grid bu