# Project Context — UnifyBoard Website V1

Last updated: 2026-07-23

## Current status

| Item | Value |
|------|-------|
| Repository | https://github.com/UnifyBoard/unifyboard-website-v1 |
| Purpose | Static Marketing Website (V1) |
| Production apex today | Still WordPress at https://unifyboard.com |
| Cloudflare Pages project | `unifyboard-website-v1` |
| Pages URL | https://unifyboard-website-v1.pages.dev/ |
| Phase | Structure + Pages wired; Phase 2 visual implementation next |

## Completed work

- Created private GitHub repository `UnifyBoard/unifyboard-website-v1`
- Bootstrap docs: architecture pointer, brand principles, SEO URLs, agents rules
- Seeded WP migration inventory (sitemap, SEO extract, image URL list, primary brand assets under `assets/brand/`)
- Created Cloudflare Pages project `unifyboard-website-v1` linked to this repo; production deployment live on `*.pages.dev`
- Documented Phase 3 hard gate (owner review on Pages before DNS)

## Pending tasks

- Create/link Cloudflare Pages project `unifyboard-website-v1` (needs `CLOUDFLARE_API_TOKEN` or Dashboard)
- Complete content extraction into static HTML (Phase 2)
- Owner review on Pages → DNS approval (Phase 3)
- WordPress decommission after stability (Phase 4)

## Next recommended steps

1. Provide Cloudflare API token (Pages edit) or create Pages project in Dashboard linked to this repo.
2. Implement static pages per `docs/seo-urls.md` and inventory.
3. Deploy preview; request owner review.

## Important decisions

- V1 is long-lived production marketing, not a temporary artifact.
- V1 and V2 share brand principles; not the same runtime.
- No DNS or WordPress removal without explicit owner approval after Pages review.

## Required future prompts

```text
Read docs/project-context.md and docs/inventory/README.md. Continue UnifyBoard Website V1 static implementation from the inventory. Do not change DNS.
```