Dalayon Ops Manual

How the Dalayon team works: the guides, steps, and protocols we follow. If a task is repeatable, its SOP lives here.

Internal and team-gated

This site sits behind Cloudflare Access (team-only). It is not public. Write freely about process, tooling, and conventions. Two things still stay out, because they belong elsewhere: client-attributed KPI data (that lives in the gated client hubs) and live credentials (those live in each repo's gitignored personal-notes/).

Start Here

• New to the team?

  Start with how we operate and the rules that keep our work consistent.

  Operating model · House style · Teammate onboarding

• Onboarding a client?

  The end-to-end sequence from signed deal to a live, gated reporting hub.

  Client onboarding SOP

• Building a reporting hub?

  The step-by-step runbook: scaffold, deploy, gate, brand, populate.

  Reporting hub build

• Shipping a theme change?

  Branching, QA, publish, and rollback rules for Shopify theme work.

  Theme deployment · QA checklist

How this manual is organized

Section	What's in it
How We Work	The operating model, house style and conventions, and new-teammate onboarding.
Client Lifecycle	The client journey end to end: onboarding, reporting-hub build, data refresh, CRO delivery, offboarding.
Delivery SOPs	Repeatable delivery work: Shopify theme deployment, QA, speed optimization.
Tools & Admin	How we use Cloudflare, GitHub, ClickUp, Slack, and Drive, with the exact values that never change.
Reference	Metric definitions, reusable templates, and hard-won gotchas.

Operating model

Docs are the source-of-truth layer above the working tools. Each tool has one job:

Tool	Role
This manual	Internal SOPs, playbooks, protocols, conventions
ClickUp	Tasks, deadlines, ownership, per-client checklists
Slack	Discussion and fast decisions
Google Drive	Files, exports, creative, source assets
GitHub (Dalayon-Reports)	Code, version history, review trail
Cloudflare Pages	Built docs sites and gated client hubs

Full detail: Operating model.

How to use and improve it

• Follow the SOP, don't reinvent it. If reality differs from the SOP, fix the SOP.
• This manual teaches; ClickUp tracks. SOPs explain how; the per-client ClickUp checklist records whether we did it. Keep them in sync so neither becomes shelf-ware.
• Every SOP page names an owner and a "done when" gate. If it doesn't, add them.
• Living document. Update pages as the process changes and note the date. When something bites us, add it to Gotchas so we never relearn it.