Footer Component - Discovery - Build Process

[micahchiang]

Description

One of our goals is to componentize the current footer used on va.gov and abstract it out of vets-website and content-build. In order to do this we first need to understand the build process for the footer; where it gets data from, how that data is transformed, and finally the way in which it's consumed in vets-website and content-build. Understanding this will inform us on how we might be able to build a flexible and reliable footer component that isn't prone to breaking.

Considerations

• Existing documentation on footer data
• Current va-footer application

Tasks

• [ ] Evaluate the current va-footer application and its data pipeline
• [ ] Provide a write up that proposes how it might be translated into a web component that consumes drupal data in the same structure it currently does. Propose whether or not there's validity in providing a footer that comes pre-built with menus already hydrated

Acceptance Criteria

• [ ] Above tasks have been completed

[caw310]

Hey team! Please add your planning poker estimate with Zenhub @Andrew565 @ataker @harshil1793 @it-harrison @jamigibbs @micahchiang @powellkerry @rsmithadhoc

[jamigibbs]

Confluence document with discovery notes. The team will discuss in our weekly engineering meeting.