Client Reporting Hubs

Private client reporting hubs live outside this public docs site.

Architecture

Layer	Pattern
Source	One private GitHub repo per client
Hosting	Cloudflare Pages
Domain	<client>.dalayon.work
Access	Cloudflare Access policy for client emails plus the Dalayon team
Content	Performance, conversion, CRO rounds, activity log, strategy, resources

Public Vs Private Rule

This public site can define the method. It must not contain client-attributed KPI data.

Client hubs can contain:

• Revenue, sessions, CVR, AOV, ATC rate, and funnel data.
• Client strategy and recommendations.
• Test logs and results.
• Technical notes.
• Raw export summaries.

Those hubs must be private and gated.

Refresh Loop

1. Add manual exports to the client's team-data/ folder.
2. Run the local data builder or client-specific generator.
3. Update static tables and narrative analysis.
4. Build with mkdocs build --strict.
5. Commit and push.
6. Verify Cloudflare Pages deploy and Access gating.

Access Gotcha

Gate both URLs:

• The custom domain, for example <client>.dalayon.work.
• The Cloudflare Pages fallback domain, for example client-<slug>.pages.dev.

The fallback URL can leak private content if it is not added as a second Access destination.