Edit This Wiki.

This whole site is a folder of files that lives in one place: the perkupapp/perkup-internal repo on GitHub. To change a page you get that folder onto your computer, edit it, preview it at localhost:4444, and push it back. Every push to main publishes to internal.perkup.com automatically. You do not need to be an engineer — copy the prompts below and your Claude can do the typing.

How it works, in one picture

There are four moves. You'll do the first one once, and the other three every time you want to change something.

Get the repo — download the folder of files to your computer (called "cloning"). One time.
Preview — start a tiny local web server and open http://localhost:4444/ to see the site exactly as it'll look live.
Edit — change the wording, fix a number, add a section. Refresh the browser to see it.
Push — send your change back to GitHub. It goes live on internal.perkup.com within a minute or two, automatically.

The golden rule: what you see at localhost:4444 is exactly what goes live. Get it looking right locally first, then push.

The fast way — let Claude do it

If you're not comfortable in a terminal, this is the path for you. Open Claude Code in a fresh folder, paste the prompt below, and answer its questions. It will install what's needed, get the repo, and start the preview server for you.

1 · Get the wiki onto your machine & preview it

I want to edit PerkUp's internal wiki. The source lives in the GitHub repo perkupapp/perkup-internal. Please: (1) check that git is installed (install it if not), (2) clone https://github.com/perkupapp/perkup-internal.git into my current folder if I don't already have it, otherwise run `git pull` to get the latest, (3) start a local preview by running `python3 -m http.server 4444` from inside the repo, and (4) tell me to open http://localhost:4444/ in my browser. Then ask me which page I want to change. The site is a flat tree of static HTML — each page is //index.html. Keep the preview server running while I work.

2 · When you're happy with the preview, publish it

I'm done editing the PerkUp wiki and the preview at localhost:4444 looks right. Please publish my changes: show me a short summary of which files changed, then commit them to the perkupapp/perkup-internal repo with a clear message describing what I changed, and push to the main branch. Pushing to main auto-deploys to internal.perkup.com, so confirm the push succeeded and remind me it'll be live in a minute or two. If a page's "last updated" date is now stale, update it to today first.

That's the whole loop. Edit → check localhost:4444 → paste the publish prompt. Repeat as often as you like.

The manual way — get the repo

Prefer to run the commands yourself? Here's exactly what the prompts above do. You'll need git (install here if you don't have it) and access to the perkupapp GitHub org — ask Thomas if you can't reach the repo.

First time — download a copy

git clone https://github.com/perkupapp/perkup-internal.git
cd perkup-internal

Every other time — grab the latest before you edit

cd perkup-internal
git pull

Always git pull before you start. Other people edit this wiki too — pulling first means you're working on top of their latest changes, not an old copy.

Run it locally

The site is plain HTML — there's no build step. Any static web server works. The simplest one ships with macOS: from inside the perkup-internal folder, run

python3 -m http.server 4444

Then open http://localhost:4444/ in your browser. That's the wiki, running on your machine. Edit any file, save it, and refresh the browser to see the change instantly. Leave the server running while you work; press Control + C in the terminal to stop it when you're done.

Locally you'll see the pages but not the sign-in widget or theme niceties that depend on Cloudflare — that's normal. Content and layout render exactly as they will live.

Make your edit

Every page is a single self-contained file at <section>/<page>/index.html. To change the Sales pitch page, for example, open sales/pitch/index.html. Find the words you want to change, change them, save, and refresh localhost:4444.

Editing existing copy — just change the text between the tags. You don't need to touch anything else.
Keep the date honest — near the top of each file is <meta name="wiki-last-updated" content="YYYY-MM-DD">. Bump it to today when you make a real change.
Adding a brand-new page? That has a few more steps (meta tags, registries). Read the Agent Guide or, easier, ask your Claude to "build a new wiki page following the contract at /agents/."
Unsure if it looks right? Compare it side-by-side with a sibling page on localhost:4444. Every page should feel like part of the same site.

Push to publish

When the preview looks right, send it back to GitHub. These three commands save your changes and ship them:

git add -A
git commit -m "Update the sales pitch intro"
git push

That's it. The repo is connected to Cloudflare Pages — every push to the main branch automatically deploys to internal.perkup.com, usually within a minute or two. There is no separate "deploy" button to press.

Command	What it does
`git add -A`	Marks all your edited files to be saved.
`git commit -m "…"`	Saves a snapshot with a short note describing what you changed.
`git push`	Sends that snapshot to GitHub → triggers the auto-deploy.

Write a clear commit message. "Update Mapbox case study results" tells the next person what changed. "stuff" does not. It's the history everyone reads later.

Getting unstuck

"git push was rejected" — someone else pushed while you were editing. Run git pull, resolve any overlap (or ask Claude to), then git push again.
"I can't reach the repo / permission denied" — you need access to the perkupapp GitHub org. Ask Thomas to add you.
"localhost:4444 won't load" — make sure the python3 -m http.server 4444 command is still running in your terminal, and that you're inside the perkup-internal folder.
"I pushed but the live site hasn't changed" — give it two or three minutes. If it's still stale, check the deploy status with Thomas; a build may have failed.
"I think I broke something" — nothing is permanent. Ask Thomas, or your Claude, to roll back to the previous version. That's what the commit history is for.
Building a whole new page or section — read the Agent Guide first; it's the contract for how pages are structured and registered.

Source: the perkup-internal repo README and the deploy setup (GitHub → Cloudflare Pages auto-deploy). Compiled 2026-06-07.