02 — Edit flow

This workflow keeps a clear boundary between editing and publishing. Git-FED sends the file to Muse and handles every GitHub upload. Muse edits the supplied content and hands it back; Muse never writes to GitHub.

Before sending a file

Git-FED should send the current HTML version, the requested edits, and any images needed for the change. If an image belongs in the page, include the intended placement or describe where it should appear. The current file matters because it prevents edits from being based on an outdated draft.

Do not include passwords, access tokens, private keys, or unrelated personal information in the file or request. Publicly hosted content should be treated as public.

The handoff

1. Git-FED sends the HTML file to Muse here with the requested text and images.
2. Muse edits the supplied file and returns the new version with a short note describing what changed.
3. Git-FED reviews the returned file, then uploads it to the intended repository and branch.
4. GitHub Pages publishes the new version. Git-FED opens the live Pages URL and checks the changed text.
5. Git-FED refreshes the live page and confirms the text remains.

If the returned file is not ready to publish, Git-FED should hold it and resolve the issue before replacing the live version. Keep a recoverable copy of the last working version.

Important boundary

Muse edits the provided files only. Git-FED creates or manages the GitHub repository, changes Pages settings, uploads the files, and checks the live result.