Description
Several destructive actions (delete draft, remove from blacklist, archive offering) should be reversible. Design an undo-banner pattern with countdown to permanence, primary "Undo" CTA, and consistent placement above the page footer.
Requirements and context
- Must be accessible (WCAG 2.1 AA), responsive, and documented in the design system
- Should be consistent with existing patterns and easy to review
- Relevant code:
src/components/Notifications
- Banner must use a polite live region and respect reduced-motion
Suggested execution
- Fork the repo and create a branch
git checkout -b uiux/undo-banner-pattern
- Implement changes
- Design the banner with countdown ring and Undo CTA
- Define stacking and dismiss behavior
- Document the action contract for engineers
- Validate accessibility and responsive assumptions
Test and commit
- Run checks
npm run lint and component/visual tests
- Cover edge cases
- Multiple stacked undo banners, mobile placement, reduced-motion, focus return after undo
- Include screenshots/before-after and accessibility (axe) notes
Example commit message
design: undo banner pattern for reversible actions
Guidelines
- Minimum 95 percent test coverage
- Clear documentation
- Timeframe: 96 hours
Description
Several destructive actions (delete draft, remove from blacklist, archive offering) should be reversible. Design an undo-banner pattern with countdown to permanence, primary "Undo" CTA, and consistent placement above the page footer.
Requirements and context
src/components/NotificationsSuggested execution
git checkout -b uiux/undo-banner-patternTest and commit
npm run lintand component/visual testsExample commit message
design: undo banner pattern for reversible actionsGuidelines