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

1. File issues for upcoming work

• Jiratron automatically files prototype issues.
• Issues are filed by engineering in meetings as work arises
• Issues filed by community

1. Formalize prototype plan

• Filter issues from Jiratron
• Backlog grooming/sprint planning

1. Prototype

• Codepen
• Leverage existing packages

1. Vet prototype with Design

• Design workshop is ideal
• Qotd/Slack as needed

1. Vet with implementations

• React Spectrum engineering sync

1. DNA issue for tokens

• Start conversation with DNA on CSS token needs

1. GitHub pull request

• Expected final CSS/Markup/Metadata

1. 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

1. Visual regression test

• Automated
• Generates link for review in browser

1. Request accessibility audit

• Use GitHub pull request code review

1. Update pull request with DNA tokens

• When DNA is released with updated tokens
• Lint embedded tokens

1. Engineering review

• Not full browser qa check
• Sanity check
• Naming check
• Check visual regression testing

1. Release

• Semver
• NPM packages

1. Update/release docs

• Automatically triggered with GitHub tag

1. Notify consumers

• Slack channels