Ensure HTML Head, Site Header, and Site Footer are reflected site-wide

[TimidRobot]

Problem

The creativecommons.org website is made up of various components. The navigation elements fall out of sync, degrading the user experience.

While the legalcode currently uses HTML snippets, the other components are less modular.

Description

Ensure HTML Head, Site Header, and Site Footer are reflected site-wide (ex. pull from new WordPress endpoint and apply).

• [x] Document API within creativecommons/wp-theme-creativecommons.org repository
• [x] Create tool to build includes
  • creativecommons/primary-site-includes
  • Initial includes are for legalcode (creativecommons/creativecommons.org)
  • Live example on staging: Creative Commons — Attribution 4.0 International — CC BY 4.0
• Write/adapt update tool for legacy ccEngine (cc/engine/templates/includes/)
  • Write/adapt update tool for legacy ccEngine component · Issue #1 · creativecommons/primary-site-includes
• Write/adapt update tool for FAQ (creativecommons/faq/)
  • Write/adapt update tool for FAQ component · Issue #2 · creativecommons/primary-site-includes
• Write/adapt update tool for Platform Toolkit (creativecommons/mp/)
  • Write/adapt update tool for Platform Toolkit component · Issue #3 · creativecommons/primary-site-includes

Additional context

• Provider
  • creativecommons/wp-theme-creativecommons.org
  • Add WP-API endpoint to get main and footer navigation items · Issue #2 · creativecommons/wp-theme-creativecommons.org
    • Add WP-API endpoint to header & footer navigation by hugosolar · Pull Request #3 · creativecommons/wp-theme-creativecommons.org
• Consumers
  • creativecommons/creativecommons.org
  • tools/legalcode-includes/
    • tools/legalcode-includes/html-head.html
    • tools/legalcode-includes/site-header.html
    • tools/legalcode-includes/site-footer.html
  • creativecommons/cc.engine
  • cc/engine/templates/includes/
  • creativecommons/mp/
  • creativecommons/faq/