Client Repos, Branding & Structure

1. Client repo naming

Every client repo — proposal-stage or a signed full project — comes from platform/build/new-client.sh. The name depends on whether Firefly is a delivery partner:

Project codes are standardized as CODE_0026 (e.g. KIND_0026, BOR_0026) — always include the numeric suffix, and use the client's real full name alongside the code, not just the code alone.

2. Client area vs. internal area

Every scaffolded repo gets both, automatically:

The gate fails closed: if INTERNAL_PASSWORD is never set, /internal/* stays locked, full stop.

printf '%s' '<password>' | CLOUDFLARE_ACCOUNT_ID=69e5e3e036619168d7a1ab4b9b9b1fa5 \
  wrangler pages secret put INTERNAL_PASSWORD --project-name <project>
./publish.sh   # redeploy — required to bind the secret

Visual marker for internal pages

Put this at the very top of any page under /internal/* — same banner, same copy, regardless of which brand the page otherwise uses. It's a signal about audience, not brand.

<div class="internal-banner">Internal — not for client sharing</div>

.internal-banner{
  background:#B45309; color:#fff;
  font:600 12px/1 -apple-system,BlinkMacSystemFont,"Segoe UI",sans-serif;
  letter-spacing:.06em; text-transform:uppercase; text-align:center; padding:.6rem 1rem;
}

2a. docs.mangrove-web.com hub structure

The hub index groups everything three levels deep: section (MG Internal / Tools & Projects / MG Clients + BD / Firefly x Mangrove / Made for Good / The Collective) → subsection (e.g. Estimates + Resourcing, Clients) → client overview (name + code) → items. Firefly-partnered clients (CAF, RHF, INEX, KIND) live under one Firefly x Mangrove section rather than each getting their own top-level block; Mangrove-solo clients (TFF, etc.) keep their own section.

Repo map — every hub entry to its source

Where each thing on the hub actually lives. The hub only lists the external ones; each is published from its own repo to its own Cloudflare Pages project. Internal docs (this doc, Data Architecture, RHF resourcing) are published straight from the hub repo.

Naming convention (now consistent): Firefly-partnered client repos are mg-ff-client-<CODE> (CAF, RHF, INEX, KIND, BOR); Mangrove-solo client repos are mg-client-<CODE> (TFF, POTR). A couple of local folders still read mg-client-* for CAF/RHF even though their repos are mg-ff-client-* — cosmetic, left as-is to avoid disrupting open sessions.

3. Two brand systems

Pick one per document based on whether Firefly is a delivery partner on that engagement. Never blend them, never improvise a third palette — that's exactly how the FFxMG brand went missing for months before this session.

MG

Mangrove-solo

Deep teal + crimson, Newsreader + DMSans. For any Mangrove-only work — no Firefly partnership.

#04404a

#00646b

#c71a43

#ff5942

[Client]

Page headline

In the repo: platform/docs/brand/mangrove.md + tokens.css · starter template platform/templates/brand/mangrove-page.html

FFxMG

Firefly x Mangrove

Firefly's real brand colors (yellow/purple/orange, off-black), Stabil Grotesk + Monosten. For Firefly-partnered client engagements only — not Made for Good.

#FFC817

#868BFC

#FF661F

#141414

[Client] [Client] Label

Page headline

In the repo: platform/docs/brand/firefly-mangrove.md + firefly-mangrove-tokens.css · starter template platform/templates/brand/firefly-mangrove-page.html

Templates

What's still open

• No real client repo has been scaffolded with --ff yet under live conditions.
• No existing client repo has been migrated onto these tokens — this applies going forward.
• No live page currently shows the internal banner in production (the one example was deleted along with the duplicate one-pager it lived on).