WDS Documentation Navigator

Docs path: node_modules/@wix/design-system/dist/docs/

CRITICAL: Never Read Entire Files

Files are 200-900+ lines. Follow the staged discovery flow below.

Stage 1: Find Component

Goal: Search for component by feature/keyword

bash
1Grep: "table" in components.md
2Grep: "form\|input\|validation" in components.md
3Grep: "modal\|dialog\|popup" in components.md

Output: Component name + description + do/don'ts

Next: Go to Stage 2 with component name

Stage 2: Get Props + Example List

Goal: Get props AND discover available examples

bash
1# 2a. Get props (small files OK to read, large files grep)
2Read: components/ButtonProps.md              # OK if <100 lines
3Grep: "### disabled" in components/BoxProps.md -A 3  # Box is huge
4
5# 2b. List available examples (ALWAYS grep, never read)
6Grep: "^### " in components/ButtonExamples.md -n

Output from 2b:

5:### Size
17:### Skin
71:### Affix
123:### Disabled
183:### Loading state

Next: Pick example(s) from list, go to Stage 3

Stage 3: Fetch Specific Example

Goal: Read only the example you need (~30-50 lines)

bash
1# Option A: Read with offset (line number from Stage 2)
2Read: components/ButtonExamples.md offset=183 limit=40
3
4# Option B: Grep with context
5Grep: "### Loading state" in components/ButtonExamples.md -A 40

Output: JSX code example for that specific feature

Stage 4: Icons (when needed)

bash
1Grep: "Add\|Edit\|Delete\|Search" in icons.md

Flow Summary

┌─────────────────────────────────────────────────────────┐
│ Stage 1: Grep components.md for keyword                 │
│          → finds: Button, Card, Table...                │
└────────────────────┬────────────────────────────────────┘
                     ↓
┌─────────────────────────────────────────────────────────┐
│ Stage 2a: Read/Grep {Component}Props.md                 │
│           → gets: props with types & descriptions       │
│                                                         │
│ Stage 2b: Grep "^### " in {Component}Examples.md        │
│           → gets: example names + line numbers          │
│           "5:### Size, 71:### Affix, 183:### Loading"   │
└────────────────────┬────────────────────────────────────┘
                     ↓
┌─────────────────────────────────────────────────────────┐
│ Stage 3: Read offset=183 limit=40                       │
│          → gets: specific example JSX code              │
└────────────────────────────────────────────────────────┘

Example Session: Product Page

bash
1# Stage 1: Find components
2Grep: "image\|card\|price" in components.md
3→ Image, Card, Text found
4
5# Stage 2a: Get Card props
6Read: components/CardProps.md
7
8# Stage 2b: List Card examples
9Grep: "^### " in components/CardExamples.md -n
10→ 5:### Basic, 25:### With media, 60:### Clickable
11
12# Stage 3: Fetch "With media" example
13Read: components/CardExamples.md offset=25 limit=35
14→ Gets Card with Image example code
15
16# Repeat Stage 2-3 for other components as needed

Result: ~80 lines read instead of 1500+

Quick Reference

File Sizes

Grep Patterns by Use Case

bash
1# Forms
2Grep: "form\|input\|validation" in components.md
3
4# Layout
5Grep: "layout\|page\|card\|box" in components.md
6
7# Data display
8Grep: "table\|list\|badge" in components.md
9
10# Feedback
11Grep: "notification\|toast\|loader" in components.md

Quick Component Mapping (Design → WDS)

Spacing (px → SP conversion)

When designer specifies pixels, convert to the nearest SP token:

tsx
1<Box gap="SP2" padding="SP3">

Only use SP tokens for gap, padding, margin - not for width/height.

Imports

tsx
1import { Button, Card, Image } from '@wix/design-system';
2import { Add, Edit, Delete } from '@wix/wix-ui-icons-common';