← All playbooks · Raw API

partnerships-pages

# Partnership / Gateway pages — point.me

B2B **page** entries under `/partnerships/`. Clone these instead of the consumer homepage.

## URL patterns

| Public path | CMS slug |
|-------------|----------|
| `/partnerships/` | `partnerships` |
| `/partnerships/financial-institutions/` | `partnerships/financial-institutions` |
| `/partnerships/travel-and-loyalty-partners/` | `partnerships/travel-and-loyalty-partners` |

Markdown: `https://www.point.me/partnerships.md` (and nested paths). `contentType: page`.

## Typical stack

| Role | Types |
|------|--------|
| Hero | **Hero text left** / **Hero centered text** (match the live page) |
| Problem / proof | **Statistics**, **Content**, **Feature card** |
| Product story | Search / Compare / Checkout / Engage modules — clone, do not invent a fourth pillar |
| Paths | Cards or services linking to FI vs travel-loyalty L2 |
| Social proof | Logo row / quotes |
| Demo | **Hubspot form** (`#hubspot-form`) — do not swap for Iterable |
| FAQ | **FAQs** |
| CTA | **CTA** / email |

L2 pages (financial institutions, travel-and-loyalty) are longer: architecture, timelines, resource links, FAQs. Clone the matching L2, not the hub.

## Workflow

1. `cms-edit open /partnerships/` or the L2 path
2. Clone with `task-clone-page` when adding a new partner audience
3. Keep HubSpot as the demo form
4. `preview urls` on staging → `diff` → `save` → `task-publish-handoff`

## Out of scope

- Consumer Explore / search heroes unless the live partnership page already has them
- Insights articles about partners (`articles`)