Template Vertical

## Setup: Track this exercise with Beads

```bash
bd create "Praxis: Design template for [vertical]" --type=feature --labels=learn,systems
bd create "Research vertical—identify common patterns" --type=research --labels=learn
bd create "Define structure (what cannot change)" --type=task --labels=learn
bd create "Define configuration schema (what can change)" --type=task --labels=learn
bd create "Identify extension points with constraints" --type=task --labels=learn
bd create "Document rationale for each constraint" --type=task --labels=learn
```

---

Help me design MY template architecture for [VERTICAL].

I'm building a template system for [VERTICAL] (e.g., law firms, architecture studios, restaurants). Guide me through:

1. **Research the vertical**:
   - What pages does every [VERTICAL] website need?
   - What content types are universal vs. optional?
   - What industry conventions exist (terminology, navigation patterns)?

2. **Define structure** (what CANNOT change):
   These are the bones—the parts every instance shares:
   - Required pages (Home, About, Contact, ...)
   - Navigation patterns
   - SEO requirements
   - Accessibility standards

3. **Define configuration schema** (what CAN change):
   Create a JSON schema for customization:
   ```typescript
   interface SiteConfig {
     name: string;
     tagline?: string;
     // What else?
   }
   ```

4. **Identify extension points**:
   Where can users add custom content without breaking the system?
   - Custom pages?
   - Custom sections on standard pages?
   - Theme overrides?
   - List constraints for each extension point.

5. **Document constraints with rationale**:
   For each constraint, explain WHY:
   | Constraint | Rationale |
   |------------|-----------|
   | Max 6 nav items | Cognitive load research |

6. **Write MY template philosophy**:
   - What is structure vs. configuration in my system?
   - How do I balance flexibility with coherence?

Vertical: [YOUR_VERTICAL - e.g., "law firms", "restaurants", "portfolios"]