New Teammate Onboarding¶

Owner: Bryan · Goal: a new teammate can preview a client site locally and ship a small change by end of week one.

This is the "get set up and productive" track for a new team member. Client onboarding (a new client) is a different SOP: Client Onboarding.

Phase 1: Accounts and access¶

Least-privilege by default. Grant only what the role needs.

GitHub: invite to the Dalayon-Reports org (member, not owner).
Cloudflare: only if they need dashboard access. Most teammates never do. Never add clients here; teammates only if they run deploys.
ClickUp: add to the workspace and the relevant client spaces.
Slack: add to the workspace and client channels.
Google Drive: share the relevant client folders.
Password manager: share only the vaults their role requires.

Phase 2: Local setup¶

Install Python 3.12, Git, and GitHub Desktop.
Clone a client repo (start with client-sample, the cleanest reference build).
Create the environment and preview:

cd client-sample
py -m venv .venv
.\.venv\Scripts\python.exe -m pip install -r requirements.txt
.\.venv\Scripts\python.exe -m mkdocs serve -a 127.0.0.1:8000

Open http://127.0.0.1:8000 and confirm the site renders.

Phase 3: Read these first¶

Operating model: how the pieces fit together.
House style & conventions: the rules for everything we publish (especially: no em dashes).
Public CRO Methodology and CRO Process: how we think about conversion work.
Skim the Client Lifecycle section to see the shape of an engagement.

Phase 4: First real work¶

Shadow one data refresh and one CRO round if timing allows.
Make one small, real change to a client repo (a copy fix or a page tweak), build with mkdocs build --strict, and have it reviewed before it ships.
Learn the deploy path: who pushes, and how Cloudflare rebuilds (roughly 2 minutes).

Done when¶

The teammate can: preview any client site locally, explain the three-site model, name the house-style rules, and has shipped one reviewed change. Log completion in their ClickUp onboarding task.