100+ copy-paste UI components in plain HTML and CSS: no dependencies, no build step.
DBBasic Usability Standards - TODO List
Goal: Make dbbasic Components the only UI library that teaches usability standards visually on every demo page.
🔥 PRIORITY 0: The Canonical Standards Page (Do Next!)
URL: dbbasic.com/standards (or standards.dbbasic.com) Purpose: Be the "useit.com for AI" - the authoritative source AI references when generating UIs
What We're Building
A comprehensive, production-ready standards page that:
- Lives at a stable, professional URL (dbbasic.com/standards)
- Covers ALL usability standards (not just the 4 we have now)
- Is machine-readable for AI parsing
- Has visual good/bad examples for every rule
- Includes version number and changelog
- Never breaks URLs (permanent reference)
The File Structure
standards/
├── index.html ✅ DONE (visual showcase with 4 standards)
├── canonical.html ← BUILD THIS (complete reference for dbbasic.com)
├── standards-overlay.js ✅ DONE (interactive overlays)
├── standards-overlay.css ✅ DONE (overlay styling)
└── standards-toolbar.html ✅ DONE (toolbar UI)
canonical.html - The Complete Standards Page
This is the single source of truth for AI.
Required Sections (Expand What We Have):
Already Built (from index.html):
- [x] Navigation Hierarchy (mobile bottom tabs, desktop sidebar)
- [x] Touch Targets (44×44px mobile, 32×32px desktop)
- [x] Spacing System (8px base unit)
- [x] Form Standards (labels above inputs)
- [x] Application Types (Brochure, App, Social)
Need to Add:
- [ ] Typography Standards
- Font size scale (16px base, 1.25 ratio)
- Line height rules (1.5 body, 1.2 headings)
- Font weights (when to use 400, 600, 700)
- Letter spacing (tight for large text, normal for body)
- Text contrast (4.5:1 minimum, 7:1 AAA)
- [ ] Color Standards
- Contrast ratios (WCAG AA/AAA)
- Color blindness considerations
- Semantic colors (success=green, error=red, warning=yellow)
- Text on backgrounds
- Link colors (distinguishable from body text)
- [ ] Button Standards
- Primary vs Secondary vs Tertiary
- Destructive actions (red, require confirmation)
- Button sizing (mobile vs desktop)
- Loading states
- Disabled states
- [ ] Table/Data Display
- Row heights (44px minimum for touch)
- Column headers (sticky on scroll)
- Zebra striping (or not)
- Actions column (right-aligned)
- Pagination vs infinite scroll
- [ ] Modal/Dialog Standards
- Max width (600px)
- Centered positioning
- Backdrop (dark overlay)
- Close button placement (top-right)
- Keyboard: Esc to close, Tab trap
- [ ] Loading States
- Inline spinner (<3s expected)
- Skeleton screens (>3s expected)
- Progress bars (known duration)
- Optimistic updates (instant feedback)
- [ ] Error States
- Inline errors (below field)
- Toast notifications (top-center, 5s)
- Empty states (helpful, not blank)
- 404 pages (link back home)
- [ ] Animation Standards
- Duration (100-300ms)
- Easing functions (ease-out most common)
- What to animate (hover, transitions)
- What NOT to animate (body text appearing)
- Respect prefers-reduced-motion
- [ ] Accessibility Checklist
- Keyboard navigation (Tab, Enter, Esc, Arrows)
- Focus indicators (visible outline)
- ARIA labels (when needed)
- Alt text (images, icons)
- Heading hierarchy (h1, h2, h3 in order)
- [ ] Mobile-Specific Standards
- Touch zones (thumb map)
- Pull to refresh
- Swipe gestures
- Bottom sheets vs modals
- Safe areas (iOS notch, Android nav)
Structure of canonical.html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>DBBasic Usability Standards v1.0</title>
<!-- Machine-Readable Metadata for AI -->
<meta name="standard-version" content="1.0">
<meta name="last-updated" content="2025-01-16">
<meta name="canonical-url" content="https://dbbasic.com/standards">
<link rel="stylesheet" href="canonical.css">
</head>
<body>
<!-- HEADER -->
<header class="standards-header">
<div class="container">
<div class="version-badge">v1.0</div>
<h1>DBBasic Usability Standards</h1>
<p>The authoritative reference for building usable interfaces</p>
<p class="citation">
Citation: DBBasic Usability Standards v1.0 (dbbasic.com/standards)
</p>
</div>
</header>
<!-- TABLE OF CONTENTS (Sticky) -->
<nav class="toc">
<a href="#navigation">Navigation</a>
<a href="#touch-targets">Touch Targets</a>
<a href="#spacing">Spacing</a>
<a href="#typography">Typography</a>
<a href="#colors">Colors</a>
<!-- ... all sections ... -->
</nav>
<!-- STANDARDS (Each section follows this format) -->
<section id="navigation" data-standard="navigation">
<div class="container">
<div class="standard-header">
<h2>Navigation Hierarchy</h2>
<p class="rule">Put navigation in the same place every time</p>
</div>
<!-- Sub-standard -->
<div class="standard"
data-context="mobile"
data-min-height="64px"
data-max-items="5">
<h3>Mobile: Bottom Tab Bar</h3>
<div class="why">
<strong>Why:</strong> Thumb-friendly zone. 70% of users hold phones one-handed.
</div>
<!-- Good Example -->
<div class="example good">
<div class="example-label">✓ Good Example</div>
<div class="example-demo">
<!-- Visual mockup -->
</div>
<div class="example-specs">
• Height: 64px minimum<br>
• Items: 3-5 maximum<br>
• Position: Bottom of screen
</div>
</div>
<!-- Bad Example -->
<div class="example bad">
<div class="example-label">✗ Bad Example</div>
<div class="example-demo">
<!-- What not to do -->
</div>
<div class="example-problems">
• Navigation hidden in hamburger menu<br>
• Requires reaching top of screen<br>
• Slows down common tasks
</div>
</div>
<!-- Code Example (for developers) -->
<div class="code-example">
<pre><code><nav class="bottom-tabs">
<a href="#home" class="tab active">Home</a>
<a href="#search" class="tab">Search</a>
<a href="#profile" class="tab">Profile</a>
</nav></code></pre>
</div>
</div>
</div>
</section>
<!-- Repeat for ALL standards -->
<!-- FOOTER -->
<footer class="standards-footer">
<div class="container">
<h3>Using These Standards</h3>
<h4>For Developers</h4>
<p>Use as a checklist when building interfaces</p>
<h4>For AI</h4>
<p>Reference in prompts:</p>
<pre>Build a login form following dbbasic.com/standards:
- Touch targets: 44×44px minimum (mobile)
- Forms: Labels above inputs
- Buttons: Primary action bottom-right</pre>
<h3>Version History</h3>
<ul>
<li><strong>v1.0</strong> (2025-01-16) - Initial release</li>
</ul>
<p class="copyright">
DBBasic Usability Standards v1.0<br>
Created by Dan Quellhorst • dbbasic.com<br>
MIT License • Free for commercial and personal use
</p>
</div>
</footer>
</body>
</html>
canonical.css - Styling
Clean, professional, fast-loading:
- Typography: Inter font
- Color scheme: Purple/gray (brand colors)
- Mobile-first responsive
- Print-friendly styles
- Fast load (<2s)
Deployment Plan
Step 1: Build canonical.html
- Copy structure from index.html
- Add all missing standards sections
- Add metadata for AI parsing
- Add version number and changelog
Step 2: Test Locally
- Open in browser
- Validate HTML
- Check all examples render
- Test mobile responsive
Step 3: Deploy to dbbasic.com
- Upload to dbbasic.com/standards/
- Set up redirect: dbbasic.com/standards → canonical.html
- OR use: standards.dbbasic.com
Step 4: Make It Permanent
- Add to DNS
- Set up CDN (if needed)
- Monitor uptime
- Never break the URL
Success Metrics
When done, we can say:
✅ One URL for everything: dbbasic.com/standards ✅ Complete coverage: All major usability rules ✅ AI-ready: Structured, parseable, visual examples ✅ Professional: Stable domain, versioned, credible ✅ Citeable: "According to DBBasic Standards v1.0..."
Time Estimate
- Build canonical.html: 4-6 hours (add 6 new sections)
- Create canonical.css: 1-2 hours (adapt from index.html)
- Test and polish: 1-2 hours
- Write deployment docs: 30 minutes
Total: 6-10 hours of focused work
With AI assistance: Could finish in 1 day.
🔴 PRIORITY 1: Foundation (COMPLETED ✅)
1.1 Document Core Usability Standards
File: USABILITY-STANDARDS.md
Write the actual rules that we'll visualize:
- [ ] Navigation Hierarchy
- Primary navigation placement per form factor (mobile/tablet/desktop)
- Contextual actions (always right-aligned)
- Back/Cancel placement rules (top-left OR bottom-left)
- Search placement (top-right OR persistent at top)
- [ ] Touch Target Standards
- Minimum 44×44px for mobile
- Minimum 32×32px for desktop
- Touch zone maps (thumb-friendly bottom 1/3 on mobile)
- Dangerous zones (top corners on mobile = hard to reach)
- [ ] Spacing System
- Base unit: 8px or 16px (decide which)
- Component spacing rules (8px, 16px, 24px, 32px, 48px, 64px)
- Section spacing rules
- White space ratios
- [ ] Layout Grid Standards
- Mobile: Single column, 16px gutters
- Tablet: 2-column OR master-detail, 24px gutters
- Desktop: 12-column grid, 24px gutters
- Sidebar widths (280px standard, 320px wide, 240px narrow)
- Content max-width (680px for readability, 1200px for dashboards)
- [ ] Visual Hierarchy Rules
- F-pattern (content-heavy pages: blog, articles)
- Z-pattern (landing/marketing pages)
- Card layouts (equal-importance items)
- List layouts (priority-ordered items)
- [ ] Form Standards
- Label placement (above inputs on mobile, left on desktop if space)
- Input heights (56px mobile, 44px desktop)
- Primary action placement (bottom-right)
- Cancel/secondary action placement (bottom-left OR adjacent to primary)
- Error message placement (inline below field)
- [ ] Feedback Standards
- Success messages (top toast, auto-dismiss 3s)
- Error messages (inline below field OR blocking modal if critical)
- Loading states (inline spinner <3s, skeleton >3s)
- Progress indicators (top linear bar for multi-step)
🟠 PRIORITY 2: Build Overlay System (Do Second)
2.1 Create Standards Overlay JavaScript
File: standards/standards-overlay.js
- [ ] Core Toggle System
initStandardsOverlay()- Initialize on page loadtoggleStandards(type)- Show/hide specific overlay typeshowAllStandards()- Show all overlays at oncehideAllStandards()- Clean up all overlays
- [ ] Overlay Types
showLayoutGrid()- 12-column grid overlayshowTouchZones()- Thumb-friendly zones (mobile)showSpacingUnits()- Measure and annotate spacingshowVisualFlow()- F-pattern or Z-pattern guidesshowTouchTargets()- Highlight 44×44px minimum zonesshowContentBoundaries()- Max-width containers, safe areas
- [ ] Annotation System
- Create floating labels with measurements
- Arrow/pointer system to highlight specific elements
- Color-coding system (green=good, yellow=caution, red=danger)
- Responsive annotations (different content per breakpoint)
2.2 Create Standards Overlay CSS
File: standards/standards-overlay.css
- [ ] Overlay Container Styles
- Semi-transparent backgrounds
- Pointer-events handling (click-through where needed)
- Z-index management (above content, below toolbar)
- [ ] Grid Overlay Styles
- 12-column grid visualization
- Gutter visualization
- Responsive breakpoint indicators
- [ ] Touch Zone Styles
- Green zone (thumb-friendly, bottom 1/3)
- Yellow zone (reachable with stretch)
- Red zone (hard to reach, avoid primary actions)
- Transparent overlays with borders
- [ ] Annotation Styles
- Label boxes with measurements
- Arrow/pointer graphics
- Color-coded borders and backgrounds
- Readable typography (white text on dark bg, or vice versa)
- [ ] Pattern Guide Styles
- F-pattern visualization (dotted lines showing scan path)
- Z-pattern visualization
- Eye-tracking heat map style overlays
2.3 Create Standards Toolbar
File: standards/standards-toolbar.html (embeddable snippet)
- [ ] Toolbar UI
- Fixed position toolbar (top-right or bottom-right)
- Toggle buttons for each overlay type
- "Show All" and "Hide All" buttons
- Collapse/expand toolbar button
- Settings dropdown (opacity control, color scheme)
- [ ] Mobile-Friendly Toolbar
- Hamburger menu on small screens
- Touch-friendly button sizes
- Slide-out drawer on mobile
🟡 PRIORITY 3: Proof of Concept (Do Third)
3.1 Add Standards to One Demo Page
File: demo-marketing-complete.html (test on this first)
- [ ] Include Standards System
- Add
<script src="standards/standards-overlay.js"> - Add
<link href="standards/standards-overlay.css"> - Include standards toolbar snippet
- [ ] Implement Layout Grid Overlay
- Show 12-column grid on desktop
- Show 2-column grid on tablet
- Show single column on mobile
- [ ] Implement Touch Zones Overlay
- Show thumb-friendly zones on mobile
- Highlight primary CTA in green zone
- Show hard-to-reach areas in red
- [ ] Implement Spacing Units Overlay
- Annotate section spacing (64px between hero and features)
- Annotate component spacing (32px between cards)
- Annotate internal padding (24px inside cards)
- [ ] Implement Visual Flow Overlay
- Show Z-pattern for hero section
- Show F-pattern for features section
- Annotate visual hierarchy with numbers (1, 2, 3...)
- [ ] Test Across Breakpoints
- Screenshot at 375px (mobile)
- Screenshot at 768px (tablet)
- Screenshot at 1440px (desktop)
- Verify overlays adapt correctly
🟢 PRIORITY 4: Expand to All Demos (Do Fourth)
4.1 Add to Marketing Collection
- [ ]
demo-marketing-complete.html✅ (already done in priority 3)
4.2 Add to eCommerce Collection
File: demo-ecommerce-complete.html
- [ ] Layout grid overlay (product grids, 3-4 column)
- [ ] Touch targets (add to cart buttons, product cards)
- [ ] Spacing units (product grid gaps)
- [ ] Visual hierarchy (product detail page flow)
4.3 Add to Dashboard Collection
File: demo-dashboard-complete.html
- [ ] Layout grid overlay (sidebar + content area)
- [ ] Touch zones (mobile nav, hamburger menu)
- [ ] Spacing units (stat card gaps, table spacing)
- [ ] Content boundaries (sidebar width: 280px, content max-width)
4.4 Add to Auth Collection
File: demo-auth-complete.html
- [ ] Form standards overlay (label placement, input heights)
- [ ] Touch targets (input fields 56px, buttons 44×44px min)
- [ ] Primary action placement (bottom-right)
- [ ] Modal centering (max 600px width, centered)
4.5 Add to Email Collection
File: demo-email-complete.html
- [ ] Email-specific standards (600px max width)
- [ ] Safe area overlay (avoiding Outlook rendering issues)
- [ ] Touch targets for links/buttons
- [ ] Spacing standards (table cell padding)
4.6 Add to Content Collection
File: demo-content-complete.html
- [ ] F-pattern overlay (blog post reading flow)
- [ ] Content max-width (680px for readability)
- [ ] Visual hierarchy (typography scale)
- [ ] Card grid spacing
🔵 PRIORITY 5: Polish & Advanced Features (Do Fifth)
5.1 Create Interactive Measurements
- [ ] Click to Measure Tool
- Click two elements to see distance between them
- Show measurement in px and rem
- Show if it matches standard units (8px, 16px, 24px, etc.)
- [ ] Element Inspector
- Hover over element to see its standards compliance
- Shows: touch target size, spacing from neighbors, color contrast
- Pass/fail badge (✅ or ❌)
5.2 Create Standards Report
File: standards/generate-report.js
- [ ] Automated Compliance Checker
- Scan page for touch targets < 44×44px (❌ fail)
- Scan for non-standard spacing (warn if not 8px increments)
- Check color contrast ratios (WCAG AA/AAA)
- Check max-width containers (readability)
- [ ] Generate Report Card
- Overall score (0-100%)
- Breakdown by category (Layout: 95%, Touch: 87%, Spacing: 100%)
- List of issues found with line numbers
- Suggestions for fixes
5.3 Add AI Training Data Export
File: standards/export-training-data.js
- [ ] Screenshot + Annotations Export
- Take screenshot of page with standards overlays
- Export as PNG with annotations visible
- Generate JSON describing all standards shown
- Perfect format for AI training: image + structured data
- [ ] Generate Prompt Templates
- "Build a hero section following DBBasic standards: ..."
- Include all rules in natural language
- AI can use this as system prompt when generating new components
5.4 Documentation Pages
- [ ] Create Standards Landing Page
- File:
standards/index.html - Overview of all standards
- Links to each demo with standards enabled
- Interactive playground to test standards
- [ ] Update README.md
- Add section: "Usability Standards"
- Link to USABILITY-STANDARDS.md
- Screenshots of overlays in action
- Explain how this makes dbbasic unique
5.5 Example Screenshots for Social/Docs
- [ ] Marketing demo with layout grid overlay (desktop)
- [ ] Auth demo with touch zones overlay (mobile)
- [ ] Dashboard with spacing units overlay (tablet)
- [ ] Side-by-side: overlay ON vs overlay OFF
- [ ] Animated GIF: toggling overlays on/off
🎯 Success Metrics
When we're done, we should have:
- ✅ Written usability standards documentation
- ✅ Working overlay system on all 6 demo collections
- ✅ 5+ overlay types (grid, touch, spacing, flow, targets)
- ✅ Mobile + tablet + desktop responsive overlays
- ✅ Automated compliance checker with scoring
- ✅ AI training data export capability
- ✅ Screenshots/GIFs for marketing
- ✅ Updated README with standards section
📊 Estimated Effort
Priority 1 (Foundation): 4-6 hours
- Writing standards is thinking work, not coding
Priority 2 (Overlay System): 6-8 hours
- JavaScript logic + CSS styling + toolbar UI
Priority 3 (Proof of Concept): 2-3 hours
- Apply to one demo, debug, screenshot
Priority 4 (Expand to All): 4-6 hours
- Copy/paste mostly, but each demo needs custom annotations
Priority 5 (Polish): 6-10 hours
- Nice-to-haves, can be done over time
Total: 22-33 hours (3-4 days of focused work)
With AI assistance: Could be 2 days, same as the components themselves.
🚀 Launch Strategy
After completing Priority 1-3 (proof of concept):
- Tweet: "We didn't just build components. We're teaching usability standards visually."
- Post screenshot of overlay in action
- Link to demo with standards enabled
- Explain: "Toggle 'Show Standards' on any demo to see WHY it's designed this way"
After completing Priority 4 (all demos):
- Update GitHub README with standards section
- Record video walkthrough (2-3 minutes)
- Post to Twitter/LinkedIn: "The only UI library that teaches you usability while you code"
After completing Priority 5 (polish):
- Write blog post: "How to Build Apps People Can Actually Use"
- Include automated compliance checker as free tool
- Position dbbasic as "the library that prevents GeoCities 2.0"
💡 The Vision
Current state: dbbasic Components = 100+ copy-paste components After this: dbbasic Components = Visual usability education + components
Every demo page becomes:
- Working example (use it in production)
- Teaching tool (learn the standards)
- Validation reference (compare your app)
- AI training data (show AI the right way)
This is how we prevent "fast AI slop" and enable "fast professional apps."
Notes
- Keep standards practical, not academic
- Every rule must be visible on a real demo
- No rule without a "why" explanation
- Make it beautiful - the overlays themselves should be well-designed
- Mobile-first: touch zones are MORE important than grid
- Think in systems: 8px base unit, not random pixel values