← All playbooks · Raw API

production-site

# Production site

How to read **published** HTML and Markdown from the live site.
Configured in `project.json` → `website.productionSiteUrl` and `website.markdownAccess`.
**Do not guess** markdown URLs — use the patterns below.

## Production URL

https://www.point.me

## Markdown access

Append `.md` to the **public HTML path** (the URL visitors see — may differ from CMS slugs; see `routing.md`).

### URL patterns

- **Homepage:** `https://www.point.me/index.md` (public path `/` → markdown `/index.md`)
- **Pages:** `https://www.point.me/{public-path}.md`
- **Articles:** `https://www.point.me/insights/{type}/{slug}.md`
- **Tags:** `https://www.point.me/topics/{slug}.md`
- **Team / people:** `https://www.point.me/insights/author/{slug}.md`

### Discovery (full URL lists)

- `https://www.point.me/llms.txt` — site summary and sample markdown links
- `https://www.point.me/markdown-index.txt` — complete markdown URL index
- `https://www.point.me/site-info.md` — factual site summary

### Notes

Tag index pages live under /insights/{tag}/. Only marketing routes on Vercel — not AWS product paths (/home, /search, /app).

## Agent rules

1. **Do not guess** — use the patterns above, `routing.md`, or fetch `llms.txt` / `markdown-index.txt`.
2. Use `cms_edit` (`open`, `list`, `snapshot`) for **editing CMS drafts**; use production `.md` URLs for **reading published content**.
3. Map CMS slugs to public paths via `routing.md` before building a markdown URL.