SPIKE: Context API for Pages

[wijohnst]

Should we leverage context API to DRY out non-Atom components?

What's the problem?

Currently we use an Atomic Design based taxonomy for describing components:

• Atoms - the smallest unit
• Molecules - components that are a combination of Atoms
• Pages - components that are a combination of Molecules

At the Molecule and Pages levels there are often nested components:

Pictured, ProfilePage nested components

Even with efforts to separate concerns there are often circumstances that require passing the same data and methods between nested components.

How might we leverage React's Context API to simplify data passing between nested components?

Subtasks

• Create POC of ProfilePageContext that implements context API in ProfilePage
• Create documentation of the process in the DOCS repo
• Include pros and cons of the approach
• If approach is adopted, create tech debt stories associated with this new pattern