Spectrum CSS Engineering Workflow

Points 9-13 are asynchronous.

1. Attend Design Workshop
   • One engineer
   • Rotate each sprint
   • Ping other engineers as needed to join
2. File issues for upcoming work
   • Jiratron automatically files prototype issues.
   • Issues are filed by engineering in meetings as work arises
   • Issues filed by community
3. Formalize prototype plan
   • Filter issues from Jiratron
   • Backlog grooming/sprint planning
4. Prototype
   • Codepen
   • Leverage existing packages
5. Vet prototype with Design
   • Design workshop is ideal
   • Qotd/Slack as needed
6. Vet with implementations
   • React Spectrum engineering sync
7. DNA issue for tokens
   • Start conversation with DNA on CSS token needs
8. GitHub pull request
   • Expected final CSS/Markup/Metadata
9. File Jira issue for design review
   • Use Jira issues to notify Design and track work
   • Discuss in Design Workshop
   • Use generated link from visual regression testing
10. Visual regression test
    • Automated
    • Generates link for review in browser
11. Request accessibility audit
    • Use GitHub pull request code review
12. Update pull request with DNA tokens
    • When DNA is released with updated tokens
    • Lint embedded tokens
13. Engineering review
    • Not full browser qa check
    • Sanity check
    • Naming check
    • Check visual regression testing
14. Release
    • Semver
    • NPM packages
15. Update/release docs
    • Automatically triggered with GitHub tag
16. Notify consumers
    • Slack channels