A clear, reliable way to stay up-to-date and track component changes and status

[thisisdano]

This epic addresses the need to be clear about how the system is changing from release to release — to know how components have changed from release to release, either in style or in markup — so developers can evaluate when and how they may wish to upgrade their version of the system.

Issues relevant to this epic

• Create a component status page
• Develop a way to see all issues and PRs connected to a component
• Develop a way to see the version history of a component
• Institute clear development pathways for experimental features and beta releases