← All playbooks · Raw API
audience-hubs
# Audience hubs — HopSkipDrive
Playbook for the three primary **audience landing hubs**: Schools, Families, and CareDrivers.
## URL patterns
| Audience | Public path | CMS slug | Template (typical) |
|----------|-------------|----------|---------------------|
| Schools / districts | `/schools` | `schools` | General page — **b2b newsletter** |
| Families / caregivers | `/families` | `families` | General page — **no newsletter** |
| CareDrivers | `/drive` | `drive` | General page — **caredriver newsletter** |
Nav label for CareDrivers is **“CareDrivers”**; URL remains **`/drive`**. Do not create `/caredrivers` without product intent.
Related hubs (not this playbook’s primary clone set — still marketing pages): `/government-agencies`, `/nonprofits`, offerings under What We Offer.
## Typical content stacks (live CMS)
Clone from these; do not invent new module vocabularies when updating.
### Schools — `/schools`
1. **Text and Image** hero
2. **Full width landscape** — How We Help
3. **Landscape cards** — Why schools choose HSD
4. **Central image carousel** — Ride management platform
5. **Testimonials**
6. Text header + **Steps cards** ×3 (safety)
7. **Tabs** — student needs
8. **Logos** — co-op partners
9. **Locations** (collection)
10. **FAQs**
11. Contact **narrow cards**
### Families — `/families`
1. **Text and Image** hero
2. **Landscape cards**
3. **Ordered List With Image** — How it works
4. **Testimonials**
5. Text header + **external video** (safety)
6. **Locations**
7. **Cards overlapping image** — support needs
8. **Product CTA** — app
### CareDrivers — `/drive`
1. **Text and Floating Image** hero
2. **Square Cards** — Why drive
3. **External video**
4. **Product CTA**
5. **Tiles** — requirements
6. **Testimonials**
7. **Locations: Linked** (CareDriver)
8. **FAQs**
9. **Large text only link cards** — resources
City-specific pages under `/drive/{city}` are **not** audience hubs — use `cms-edit://customer/location-pages`.
## Voice by audience
| Hub | Emphasize | Avoid |
|-----|-----------|--------|
| Schools | Safety, reliability, RideIQ / RouteWise AI™, district outcomes, equity of access | Consumer app-only tone |
| Families | Trust, how it works, safety, app | Dense B2B jargon |
| CareDrivers | Requirements, earnings narrative, resources, apply path | District procurement language |
Use brand terms: **CareDriver**, **RouteWise AI™**, **RideIQ**, **supplemental transportation**.
## Reference pages
| Path | Clone when |
|------|------------|
| `/schools` | District / co-op / school-facing hub or major redesign |
| `/families` | Caregiver / parent hub updates |
| `/drive` | CareDriver marketing hub (not a single city page) |
Also useful adjacent clones: `/safety`, `/supplemental-transportation`, `/caredriver-resources` (resources, not the primary hub).
## Workflow
1. Read `cms-edit://customer/pages` for general page rules
2. Open the hub: `cms-edit open --page-slug /schools` (or `/families`, `/drive`)
3. Prefer **editing existing components** in place over wholesale replacement
4. When restructuring, `task-clone-page` from the same hub as a draft sandbox (`indexed: false`) first
5. Keep **one primary orange CTA** per section; forms/HubSpot IDs from existing entries
6. Locations modules: update linked location data carefully — city pages are separate entries
7. `preview urls` → `diff` → `save` → `task-publish-handoff`
## Icons and media
- Prefer CMS **`icon …`** assets (see website-guide icon index)
- Prefer existing photography on the hub; upload only approved assets
- Safety video: reuse external video entries already on Families / Safety where possible
## Out of scope
- `/drive/{city}` location content type → `location-pages`
- Blog/news content → `articles`
- Full What We Offer product pages (RouteWise, Supplemental) — clone those pages via `pages`
- Nav/footer structure — `task-navigation`
## Related
- General pages hub: `cms-edit://customer/pages`
- Locations: `cms-edit://customer/location-pages`
- Articles / newsroom links on hubs: `cms-edit://customer/articles`