askrobots / dbbasic-web-native
Public
100+ copy-paste UI components in plain HTML and CSS: no dependencies, no build step.
danq9
Add canonical.html v1.0 - The single source of truth for usability standards
fb6e650
1 year ago
History
BOOTSTRAP-REPLACEMENT-MVP.md · 4.7 KB · 160 lines
Bootstrap Replacement MVP
Goal: Stop Using Bootstrap
Target: Build the minimum set of components to replace Bootstrap in real projects
What Bootstrap Provides (Core Components)
Layout & Structure
- Container/Grid system
- Rows and columns
- Responsive utilities
Components We Already Have ✅
- ✅ Buttons (semantic-action)
- ✅ Cards (semantic-card)
- ✅ Forms/Inputs (semantic-input)
- ✅ Modals (semantic-modal)
- ✅ Alerts/Toasts (semantic-feedback)
- ✅ Dropdowns/Menus (semantic-menu)
- ✅ Navigation (semantic-navigator)
Components We Need to Build
- ❌ Tabs - Tab navigation (critical)
- ❌ Accordion/Collapse - Expandable sections (high priority)
- ❌ Spinner/Progress - Loading indicators (high priority)
- ❌ Badge - Notification counts (medium priority)
- ❌ Breadcrumb - Navigation breadcrumbs (medium priority)
- ❌ Pagination - Page navigation (medium priority)
- ❌ Tooltip - Hover information (medium priority)
- ❌ Popover - Click information (medium priority)
What We Can Use Tailwind For
- Container/Grid →
<div class="container mx-auto"> - Responsive utilities → Tailwind classes
- Spacing/Typography → Tailwind classes
MVP Strategy: 2-Week Sprint
Week 1: Critical Components (4 components)
Build the ones you absolutely cannot work without:
Day 1-2: semantic-tabs
- Tab navigation with panels
- Keyboard navigation (arrow keys)
- Grid test hover/active/focus states
- Priority: CRITICAL
Day 3-4: semantic-disclosure (Accordion/Collapse)
- Expandable/collapsible sections
- Multiple or single-open modes
- Smooth animations
- Priority: CRITICAL
Day 5: semantic-progress
- Spinner (indeterminate)
- Progress bar (determinate)
- Priority: CRITICAL
Week 2: High-Value Components (4 components)
Day 6-7: semantic-badge
- Notification indicators
- Counts on buttons/icons
- Priority: HIGH
Day 8-9: semantic-popover
- Contextual information
- Smart positioning (arrow points to trigger)
- Replaces both tooltip and popover
- Priority: HIGH
Day 10: semantic-breadcrumb
- Navigation hierarchy
- Auto-truncates on mobile
- Priority: MEDIUM
Optimization Pass (Week 2, remaining days)
Day 11-12: Optimize Existing Components
- Apply grid testing to semantic-card
- Apply grid testing to semantic-input
- Apply grid testing to semantic-modal
Day 13-14: Real-World Testing
- Build a complete page using only semantic components + Tailwind
- Identify gaps
- Polish rough edges
After 2 Weeks: Bootstrap Replacement Complete
You'll have:
- 13 semantic components (9 existing + 4 new critical)
- 6 additional high-value components
- Several existing components optimized
- Real-world validation
You can then:
- ❌ Remove Bootstrap from projects
- ✅ Use semantic components + Tailwind
- ✅ Focus on building features, not UI infrastructure
- ✅ Benefit from modality-agnostic design
- ✅ Get WCAG AAA accessibility automatically
Implementation Order (Prioritized)
Tier 1: Must-Have (Week 1)
- semantic-tabs - Can't build settings pages without this
- semantic-disclosure - FAQ sections, settings panels
- semantic-progress - Loading states are everywhere
- semantic-badge - Notification counts
Tier 2: Very Useful (Week 2)
- semantic-popover - Contextual help, info bubbles
- semantic-breadcrumb - Multi-level navigation
- Optimize semantic-card
- Optimize semantic-input
Tier 3: Nice to Have (Future)
- semantic-pagination (can use Tailwind temporarily)
- semantic-carousel (can defer)
- semantic-rating (can defer)
Success Criteria
After this 2-week sprint, you should be able to:
- ✅ Build a complete dashboard without Bootstrap
- ✅ Have all critical interactive patterns covered
- ✅ Navigation works (tabs, breadcrumbs, menus)
- ✅ Feedback works (badges, toasts, progress)
- ✅ Forms work (inputs, validation)
- ✅ Layouts work (cards, containers, grids via Tailwind)
- ✅ Everything is accessible (WCAG AAA)
- ✅ Everything is modality-agnostic (mouse, touch, keyboard, voice)
Let's Start NOW
Today's Goal: semantic-tabs
Let's build the first critical component right now and validate the workflow.
semantic-tabs requirements:
- Multiple tabs with associated panels
- Click to switch tabs
- Keyboard navigation (arrow keys, Home, End)
- ARIA roles (tablist, tab, tabpanel)
- Support for badges on tabs
- Disabled tabs
- Vertical or horizontal orientation
- Grid test all interactive states
Estimated time: 6-8 hours
- Design API: 1 hour
- Implement base functionality: 2-3 hours
- Grid test states: 1-2 hours
- Documentation: 1 hour
- Testing: 1 hour
Ready to start?