* corrected package.json version numbers to match style.css (when lower)
* Returned Skatepark to correct version
* Corrected skatepark style.css version
Initially intended as a part-fix for #3134 to enable child themes to swap typefaces that get included more easily, this also extends that change across to many themes using the common patterns.
It explicitly does not change the following themes:
Spearhead (uses different endpoint and method)
And the following themes that have multiple functions that generate typeface includes so as to avoid confusion:
* canard
* gazette
* illustratr
* publication
* FSE - fix styling of footer separator and nav menu to match editor styling
* Fix margins for smaller screens
* Better align all types of block content in footer between front end and editor
* Some more css tweaks!
* Remove redundant selector
- Since we set the order of footer/header elements (like nav)
in Gutenberg, we don't want the stylesheet to override it.
- Use the `.fse-enabled` selector to disable the order property
- This was causing the footer nav menu in FSE to show up at
very bottom of the page, even if the user changed its order.
To avoid duplicating this file across all FSE themes
I'm moving it to the FSE plugin instead and providing
hooking to theme activation there. This is now viable
since we are no longer hardcoding the templates in
themes, but fetching them from the Dotcom API.
* Modern Business - Full Site Editing - Add `.fse-enabled` selectors to block css for header and footer if FSE is enabled in order to apply the correct front end block styles to the FSE header and footer content.
Previously, the block would jump around as the line height and size
were not consistent. This makes those consistent and makes
sure that they are also applied during block focus.
We disabled alignment settings for the blocks, but the template
content still has alignment in it. This produces a template
conflict warning in the editor.
Shows the default site info line after the footer template part
content. Also adds header and footer tags to corresponding template
parts to bring them closer to overall theme's structure.
FSE contant will always be defined due to the fact that this
plugin bundles other functionality (SPT). Because of that we
can't rely on it to determine if this feature has been activated.
