# Site Output

`site/` is a lightweight publish-area staging location.

## Current Contents

- `index.html`: main applications catalog website for browsing approved brand outputs
- `download-packs.html`: family-level download hub for bundled ZIP packs
- `downloads/`: packaged ZIP bundles grouped by asset family for handoff and quick retrieval
- `previews/`: rendered PNG previews generated from live HTML templates for catalog use
- `using-the-brand.html`: guided usage page for choosing the right asset family and escalation path
- `families/`: detail pages for the main application families
- `applications-catalog.css`: dedicated stylesheet for the catalog and family pages
- `brand-book.css` and `brand-book-print.css`: mirrored style sources for standalone brand-book HTML outputs

## Current Role

- Use `index.html` as the fast browsing surface for the applications layer.
- Use the catalog search and filter controls to narrow assets by readiness state and channel family.
- Use `download-packs.html` when the goal is to retrieve grouped deliverables quickly rather than browse the catalog.
- Use `using-the-brand.html` when the question is “how should I apply the system?” rather than “where is the file?”
- Use the `families/` pages for grouped downloads, richer previews, and family-specific guidance.
- Keep public-facing language aligned to the canonical message, service, naming, and proof chapters under `docs/brand-book/`.
- Avoid turning `site/` into a separate source of truth from the brand book itself.

## Pages Packaging

- Cloudflare Pages publishes only the `site/` directory for this project.
- Before deploys, run `python3 scripts/sync_site_publish_assets.py` from the repo root.
- That sync step mirrors externally linked public assets, templates, and brand-book files into `site/files/` and rewrites the live HTML to use publish-safe paths.
- Treat `site/files/` as generated publish content for the deployed portal, not as the canonical source of truth.

## Next Publishing Direction

- Treat the catalog, usage guide, and family pages as the first publish-ready website surface in this repo.
- Use Cloudflare Pages with Git integration as the first live publishing path for this site surface.
- Create the Pages project from the GitHub repo with:
  - production branch: `main`
  - build command: none
  - output directory: `site`
  - framework preset: `None`
- Start with the Cloudflare preview deployment, then attach `brand.techops.ph` after final QA.
- Follow [`docs/brand-guide/cloudflare-pages-setup-2026-04-09.md`](../docs/brand-guide/cloudflare-pages-setup-2026-04-09.md) for the exact setup.
- Keep future public site output clearly separated from the canonical docs and template source files.