Parent issue: #77628

Currently, it's complicated for consumers to add sticky footers to pages and dashboards using Page component because it basically requires overwriting various pre-existing container styles in WP Admin and Page.

Sometimes implementation requires guestimating header+tabs implementation height, like is done at WP Fonts page.

It's also possible to get it wrong, and a longer navigation sidebar with modified container styles can affect how sidebar dropdowns are positioned (example).

Here's how the Fonts page footer implementation looks:

That page might not need footer, but it's typical for plugin developers to add consistent footer in their plugin pages.

WordPress itself even has a footer, but currently, any WP Built page does not support the regular WP Admin footer, which may or may not be by design. :-) (cc @jasmussen you might know?)

Solutions

• At minimum, a canonical footer component which just allows inserting any content to the footer, which then behaves correctly with Page padding, tabs, header sizes and so on.
• A core footer, injected into WP Build pages in WordPress
• A footer component, which is our visual recommendation of how the footer should look. Includes background color, padding, and border matching the header and thus getting updated when we change the header design.

<Page>
    Content
    <Page.Footer>
        Footer content
    </Page.Footer>
</Page>