Edit this site
The CoE site is built from markdown in a GitHub repo. If you see something wrong, you can fix it yourself, or you can ask for help. There’s no gatekeeping review before you open a change. This site belongs to the people doing the work.
Ways to edit
| Path | How it works | When to use it |
|---|---|---|
| GitHub pull request | Edit the markdown file, open a PR, a reviewer merges it. | Primary path right now. Works for anyone with a GitHub account. |
| Ask Claude / ChatGPT (coming soon) | Once the write-capable MCP lands, you’ll be able to ask your chat client to open the PR for you. | Right now this is read-only; write mode is a tracked follow-up. |
| Slack Mike or Alex | Send a Slack message with the URL, the current text, and what you want it to say. They’ll open the PR on your behalf. | No GitHub account, or you just want it done for you. |
| Become a direct collaborator | Send your GitHub username to Mike Joyce or Alex Finnemore in Slack. They’ll add you to the repo. | You want to commit directly — skip the fork. |
Open a pull request on GitHub
This is the primary path today.
- Find the file in the repo
- Edit the markdown directly in the GitHub UI, or clone the repo and work locally
- Describe what you changed and why
- A reviewer will merge it
Where the content lives
| Content type | Folder |
|---|---|
Workflow pages (/workflows/*) | src/content/workflows/ |
| Top-level site pages (About, How It Works, etc.) | src/content/site/ |
Cohort pages (/cohorts/*) | src/content/cohorts/ |
| Operator-tier pages (gated) | src/content/operators/ |
New to GitHub PRs? Contributing walks through the flow.
Ask Claude / ChatGPT (coming soon)
A read-only MCP server exposing this site’s content to chat clients is in flight — tracked as issue #8. Once extended to writes, you’ll be able to say things like:
“On the Product Data workflow page, change ‘Cohort 1 active’ to ‘Cohort 1 launched’.”
…and Claude will open the PR for you. Until then, chat-client edits still need a human to open the PR.
Slack us (no GitHub needed)
Send a Slack message to Mike Joyce or Alex Finnemore with:
- The page URL you want changed
- What you want it to say — quote the before and after, or just describe it
They’ll open the PR on your behalf and tag you when it merges.
Become a direct collaborator
Want to commit directly to the repo? Send your GitHub username to Mike or Alex in Slack. They’ll add you as a collaborator. After that, you can push branches and open PRs without forking.
What to edit
| Good target | Example |
|---|---|
| Facts that are wrong | A system has been renamed; a process step has been replaced; a detail was true in March but isn’t now. |
| Copy that reads badly | Sentences that don’t land; tone that feels off; jargon that doesn’t help. |
| Missing detail | A workflow page that skims over a phase you live in daily. |
| A workflow perspective not yet captured | Your team’s experience of the workflow differs from the current write-up. |
What not to edit (for now)
| Don’t | Why |
|---|---|
| Name individuals | CoE content is invitational, not evaluative. Frame the role, not the person. |
| Characterize a team or person’s performance | Describe the workflow and where it gets stuck; don’t evaluate the people inside it. |
| Cohort membership | Cohorts form through submissions and conversations. Submit an idea to be part of a future cohort. |