* 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.
This adds required functionality to support rendering FSE header and
footer on all site pages (static and dynamic). It's also includes the
data population functionality, which has now been removed from the plugin
and will be delegated to each theme for maximum flexibility.
- Add a helper function which creates the selectors we need to target
the various block levels within FSE blocks.
- Extend the previous commit to work with the a8c/template block
just like we did wor the a8c/post-content block.
- Should allow us to disable alignment options for template part blocks.
- Make the post content block 100% width. As a result, the post content
block takes up the same area that the post editor container takes up
without the post content block.
- Allow nested blocks inside the post content block to maintain the
default alignment styles for top level blocks. Previously, they were
targeted as 2nd level blocks, thus making the alignment incorrect.
