- Remove text-color initial rules from background-color utility classes to allow color options to work more explicitly
- Fix outline button default text color and bg-color
- Strengthen background-color and text-color selectors to better deal with nesting
- Remove text-color initial rules from background-color utility classes to allow color options to work more explicitly
- Strengthen background-color and text-color selectors to better deal with nesting
- Fix background-dim Gutenberg default bg-color issue
- Remove text-color initial rules from background-color utility classes to allow color options to work more explicitly
- Strengthen background-color and text-color selectors to better deal with nesting
- Fix background-dim Gutenberg default bg-color issue
This PR should remove all Headstart Annotations from themes in this repo.
Why? Headstart annotations stored in WP.com themes are generated, tested, and sent for translation via WP-CLI scripts running on subversion-ed WordPress sandboxes. I recently updated Headstart annotations for our 20+ recent themes in order to correct some issues in our FSE Plugin and Page Layout feature. When discussing how to get these annotations updated in this themes repo @michaeldcain and came up with two options.
1. Copy-paste back into the affected themes in this repo.
2. Just remove all the Headstart annotations from this repo.
The second option seemed the simplest. It leaves **all** Headstart annotations on WP.com "ignore-able" for this GH repo and reduces the chance of Headstart annotations becoming out of date in this GH repo, potentially reducing future errors.
* Added FSE support to Alves.
* Note: the theme `#masthead` style were preventing the FSE header to be full width as intended. Instead of needlessly overriding the whole `header.php`, I've opted to add a simpler `body:not( .fse-enabled ) #masthead`.
* Update Varia (and the other FSE themes) with FSE improvements:
* Hide the (+) icons when rendering the Template Part block inside the Page editor (especially useful for the Columns block).
* Remove the top margin if the Site Title block is the first child of an editor layout.
* Make sure each column in a Columns block is max width, so that nested FSE blocks can behave as expected.
