As a member of a VA dev team, I want to have one place to see the Storybook for both web and mobile components, so that I can use 1 resource instead of 2.
As part of this story we want to:
understand what it would take and if it's possible to combine our Storybook with VADS's
Acceptance Criteria
- [ ] Look into the feasibility of combining our Storybook instance with the VADS instance
- [ ] Document what it would take and what it would look like
**Accessibility Requirements**
- [ ] AC 1
- [ ] AC 2
- [ ] AC 3
## Notes & Open Questions
- Dependencies/Roadblocks:
- Any internal/external dependencies?
- Test accounts needed?
- Does this require QA?
- Dev Notes:
## Ticket Checklist
- [ ] Acceptance criteria defined
- [ ] Labels added (front-end, back-end, feature)
- [ ] Linked to an Epic
Description
As a member of a VA dev team, I want to have one place to see the Storybook for both web and mobile components, so that I can use 1 resource instead of 2.
As part of this story we want to:
Acceptance Criteria
- [ ] Look into the feasibility of combining our Storybook instance with the VADS instance - [ ] Document what it would take and what it would look like **Accessibility Requirements** - [ ] AC 1 - [ ] AC 2 - [ ] AC 3 ## Notes & Open Questions - Dependencies/Roadblocks: - Any internal/external dependencies? - Test accounts needed? - Does this require QA? - Dev Notes: ## Ticket Checklist - [ ] Acceptance criteria defined - [ ] Labels added (front-end, back-end, feature) - [ ] Linked to an Epic