Refactor universal and global headers and universal footer

[nrsa222]

Issue

The headers and footer are implemented using the UKL_HeaderFooter implementation, which is clunky and not easily maintainable since there are several manual steps required for updates that involved both a different repo and different production server than ExploreUK/Finding Aid Viewer.

Needs

We need to tie this code to version control, make updates to the global header and iterate updates in development that do not affect the production environment and in general have addition control over dependency management.

However, it currently provides these mostly appropriately branded components/molecules which need to be retained in the refactor:

• Universal breadcrumb
• myUK link
• UK lockup
• Site identity
• configurable menu variant
• Utility links
• static footer links
• University level emergency alerts block
• Global (EUK/FAV) alerts block

Decisions to be made

• Stick with layout variant of menu items from UKL_HeaderFooter, or use the menu layout of the official UK Global header?
• Continue using UKL_HeaderFooter?
  • If yes:
    • Can we refactor that project to be more dynamic and/or package it up some way so that we can manage it as a dependency?
    • Should we include the option to add a configurable global footer? See Limestone's global footer variants
  • If no:
    • Tie into either or both campus UKAlerts or into the UKL_HeaderFooter alerts for campus and library wide alerts. Global (EUK/FAV specific) alerts can potentially be managed by EUK or FAV.
• Pull in/utilize campus's CDN for Limestone specific styles?

Success Criteria

• Fully brand compliant universal header
• Fully WCAG 2.1 AA compliant universal header
• Fully brand compliant global header
• Fully WCAG 2.1 AA compliant global header
• Fully brand compliant universal footer
• Fully WCAG 2.1 AA compliant universal footer
• UKAlert implementation maintained as a dependency