2018-06-08 Bootstrap / Design System Sync
George Babey, Adam Stankiewicz, Alyssa Boehm (Deactivated), Darren Domingos (Deactivated), Edward Zarecor (Do Not Use) (Deactivated), Ari Rizzitano (Deactivated)
The Problem(s)
- Gaps between UX designs/implementation fidelity
- Nothing reusable
- Inconsistency between designs
- Inconsistency between implementations
- Little value in fixing what we have today
- Is it better to reimplement using reusable things?
- Unclear what "Bootstrap" means – gaps between stock Bootstrap and our implementation?
- Inconsistent language around components, areas of focus, etc.
- How do we know if something should be a component?
- Who makes the call – eng or UX?
- Eng doesn't know the "right" questions to ask
Steps towards solutions?
- Components we maybe need:
- Latency/network issues
- Pagination
- Headers
- Footers
- Forms
- Validation
- Hints
- Buttons
- Let's do some work ahead of time
- Inventory: what do we need?
- Process: how should we handle future components?
- Gaps: what are the differences between Bootstrap and our stuff?
- Flexibility: how extensible should components be?
- Scope: what do we need to implement up front?
Goals
- Buttons: single button, supports all UX use cases, future buttons only use the Paragon button
- Can we solve the 80% all at once, handle the 20% as it comes?
- Eng and UX will both be explicit about calling out exceptions/desired changes
The 80%
- List from eng, list from UX
- Criteria: What are things that would be useful as basic components?
- UX
- What is the button
- Eng
- feedback to UX by EOD Tuesday
- FedX "what do we need" survey