Blitzpanel · Standard Operating Procedure
Editing the Standards Wiki SOP
First draft for review. Cite comments by section & line — e.g. "§6 L4" means Section 6, line 4 (line numbers are in the left gutter and reset each section). Items marked TODO need Blitzpanel-specific confirmation.
1. Purpose
This procedure defines the two ways anyone at Blitzpanel can read or update a document in this Standards Wiki: asking Claude in Slack, or editing the repository directly on GitHub.
It exists so new content gets added correctly and consistently — right folder, right frontmatter, INDEX.html kept in sync — regardless of which of the two paths someone uses.
2. Scope
Applies to every document under standards/, sops/, policies/, guidelines/, playbooks/, and reference/ in the BlitzpanelStandards repository.
Does not cover the underlying hosting/Slack setup itself (Cloudflare Pages, Claude for Slack, the GitHub connector) — that is one-time IT configuration, not something editors need to touch.
3. Definitions
The wiki — the published, read-only view of this repo at blitzpanel-standards.pages.dev. It always mirrors the main branch; you cannot edit it there.
The repo — the actual source of truth, Blitzpanel/BlitzpanelStandards on GitHub. Editing means changing a file here and getting it onto main.
GitHub connector — the Claude.ai integration that lets Claude read and commit to the repo on your behalf when you talk to it in Slack.
4. Roles & Responsibilities
| Role | Responsibility |
|---|---|
| Any teammate | Ask Claude in Slack to look up or add/update a document; review Claude's summary of what it changed. |
| Comfortable with GitHub | May edit files directly in the repo instead of going through Slack (§6.2). |
Doc owner (per doc:owner meta tag) | Reviews changes to their document after the fact, corrects anything wrong, and promotes status from draft to approved when ready. |
5. Materials, Tools & Systems
Slack workspace with the Claude app installed, and a Claude account with the GitHub connector authorized against Blitzpanel/BlitzpanelStandards.
For direct edits: a GitHub account with write access to the repo (see an admin to be added as a collaborator).
6. Procedure
6.1 Editing via Slack (recommended for most people)
Open Slack and @Claude in a channel it's been added to, or DM it directly.
To look something up: ask a plain question, e.g. "@Claude what does the quoting SOP say about approval thresholds?" Claude reads the live repo to answer — it is not relying on memory, so the answer reflects the current document.
To add or change a document: describe what you want in plain language, e.g. "@Claude add an SOP for onboarding a new AE, here's the process: ..." Claude picks the right folder and template, fills in the metadata, writes the content, updates INDEX.html, and commits straight to main — there is no approval step in between.
Read Claude's reply before moving on. It always summarizes exactly what file it created or changed. Because the commit lands immediately (see §6.3), this reply is your only checkpoint to catch a mistake early.
The wiki at blitzpanel-standards.pages.dev updates automatically within a minute or two of the commit — refresh to see the change live.
6.2 Editing directly on GitHub (for anyone comfortable with git)
Clone or pull Blitzpanel/BlitzpanelStandards, or edit a file in-browser on github.com.
Follow CLAUDE.md's "How to create a new document" section: pick the type, copy the matching file from templates/, fill in the <meta name="doc:*"> tags, write the body using numbered sections and <p class="l"> lines.
Add a row to INDEX.html in the same change — this step is required and is easy to forget when editing by hand (Claude does it automatically in §6.1).
Commit and push (or merge a PR) to main. The wiki rebuilds automatically the same way as a Slack-driven edit.
6.3 What happens after you save
Every change to main, by either path, triggers an automatic Cloudflare Pages deploy — no one needs to run a build or deploy command manually.
There is no review/approval gate before a change goes live, by design, to keep adding documents fast. This means mistakes are visible immediately rather than caught before publish.
7. Records & Documentation
Every edit is a normal git commit on main in Blitzpanel/BlitzpanelStandards — the commit history is the audit trail of who (or which Slack request) changed what, and when.
Cloudflare Pages keeps a log of every deploy, viewable in the Cloudflare dashboard, if you need to confirm when a change went live.
8. References
CLAUDE.md at the repo root — the full authoring rules (naming, frontmatter, section/line numbering) that both editing paths must follow.