first-repo

Edit requests

Website changes, newest at the top. Copy this file into your site repo and keep using it.

Why bother writing it down? Three reasons, all learned the hard way: you will forget what you asked for and why; you will want to know when something changed when a page breaks; and a request written down is one you can hand to someone else — or to a Claude Code session next month that has no memory of this one.


How to ask for a change

Say four things. Paste exact text wherever you can — “make the intro better” is a wish; pasted replacement text is a request.

  1. Page / section — e.g. Home hero, About, footer, the publications list
  2. Change — what to add, remove, or reword
  3. Why — optional, but it is what makes the entry worth reading in six months
  4. Urgency — is this a quick fix or does it need care?

Then either add it below yourself, or just tell Claude Code and let it log the entry.

The workflow, every time

  1. Log it here as REQ-NNN, status Requested.
  2. Make the change.
  3. Rebuild if the site has a build step. It must finish without errors.
  4. Verify — the change is actually present, nothing else broke, no dead links.
  5. Show the human the rendered result. Not a description of it. The actual thing.
  6. Wait for approval. Do not deploy.
  7. On approval: commit, push, then check the live URL and confirm it is really there.
  8. Mark it Done with one line on what changed.

Steps 5 and 6 are the point of this file. Building and publishing are two separate decisions, and only one of them is the agent’s. Everything else here is bookkeeping.

Status values: RequestedIn progress🟡 Drafted — awaiting approval✅ Done (or Declined, with a one-line reason — declined requests stay, they are the record of what you decided against).


Template — copy this

### REQ-NNN — <short title>
- Page/section: <where>
- Change: <what — paste exact text where possible>
- Why: <optional>
- Status: Requested

Requests

REQ-001 — [Your first change]