feat: WC-274 serve footer markup (to Portal)

[wesleyboar]

Overview

Allow footer markup to be loaded from /cms/markup/footer.

Important

Is that what we want the path to be?

Why?

So WC-274 can also load footer content from CMS.

Related

• WC-274
• supports feat: WC-274 component can opt for CMS styles Core-Portal#1127

Changes

• moved footer to its own template
• deleted footer block
  ^{Unused. And footer can instead be replaced by overwriting template.}
• added url to access footer

Testing

1. Verify CMS with no custom footer content:
   • loads default footer on any page
   • serves default footer's markup at /cms/markup/footer
2. Verify CMS with any custom footer content:
   • loads custom footer on any page
   • serves custom footer's markup at /cms/markup/footer

UI

Before

markup

After

script content	network request

[rstijerina]

Just checking - is it a sticky footer?

[wesleyboar]

@rstijerina, N/A; this merely provides the footer markup, no styles.

The footer's position relative to the app that could load it (Portal) is to be defined by the app. Positioning the footer after being loaded from CMS is a remaining challenge (a checkbox task under "Status") in TACC/Core-Portal#1127.

[wesleyboar]

@rstijerina, @taoteg Any thoughts on the path name?

Existing such paths are:

• cms/nav/pages/markup/
• cms/header/branding/markup/
• cms/header/logo/markup/

But I propose:

• 🆕 cms/markup/footer
• cms/markup/nav
• cms/markup/branding
• cms/markup/logo

If a pattern change is acceptable, I will update the others.

[taoteg]

I like the clarity fo the proposed path updates with the markup prefix. Unless there is some technical reason to oppose it,I think it makes sense.