Operating Model¶
Owner: Bryan · Read this first if you're new.
What we do¶
Dalayon runs Shopify client work: conversion rate optimization, theme work, and performance. For each client we run a private, gated reporting hub that shows their performance, CRO rounds, activity log, and strategy. This ops manual is the internal layer above all of that: the repeatable how.
Source of truth¶
Docs are the source-of-truth layer above the working tools. When a process is repeatable, the SOP here is authoritative. The working tools hold the live state; the docs hold the method.
| Tool | Role | Not for |
|---|---|---|
This manual (ops.dalayon.work) |
Internal SOPs, playbooks, protocols, conventions | Live client KPIs, credentials |
Client hubs (<client>.dalayon.work) |
Per-client performance, CRO, strategy, activity log | Anything another client should not see |
Public docs (docs.dalayon.work) |
Client-facing methodology (CRO Methodology + Process) | Any private or client-attributed material |
| ClickUp | Tasks, deadlines, ownership, per-client checklists | The method itself (that lives here) |
| Slack | Discussion, fast decisions | Durable decisions (record those in docs) |
| Google Drive | Files, exports, creative, source assets | Version-controlled code |
| GitHub (Dalayon-Reports) | Code, version history, review trail | Secrets (use gitignored personal-notes/) |
| Cloudflare Pages + Access | Building and gating the docs sites | n/a |
The three-site model¶
| Site | Audience | Gated? | Source |
|---|---|---|---|
docs.dalayon.work |
Prospects, clients, public | No (public-safe) | dalayon-docs/ |
ops.dalayon.work |
The team only | Yes (team-only Access) | ops-manual/ |
<client>.dalayon.work |
One client + the team | Yes (client + team Access) | client-<slug>/ |
The public site is deliberately small: it holds only the client-facing CRO methodology that client hubs link to. Everything internal lives here. Client-specific data lives in each client hub.
The docs stack¶
Every site is the same stack, which is why the playbook is reusable:
MkDocs Material → private GitHub repo (Dalayon-Reports) → Cloudflare Pages build → custom domain → Cloudflare Access
- Build:
pip install -r requirements.txt && mkdocs build, outputsite,PYTHON_VERSION=3.12. - Zero Trust team:
dalayon(dalayon.cloudflareaccess.com), Free plan (50 Access seats). - Login methods (account-wide, already set up): One-time PIN + Google.
Exact values live in Cloudflare (Pages + Access). Repo conventions live in GitHub & Repos.
Where work lives in a repo¶
Each client repo (and this manual) follows the same shape:
| Path | What it is |
|---|---|
docs/ |
The pages. Content is Markdown. |
docs/stylesheets/extra.css |
All styling. |
overrides/ |
Theme HTML (header/footer tweaks). |
docs/_headers |
Cloudflare cache rules. |
personal-notes/ |
Gitignored. Per-repo secrets and notes. Never committed. |
site/ |
Build output. Never edit by hand. |
Client hubs additionally carry team-data/ (raw exports, committed) and tools/ (data builders). This manual has neither.