03 — Persistence

The page is static between edits. Its visible text is stored in the HTML file that GitHub Pages serves. When a visitor refreshes, the browser requests that published file again, so the same text appears as long as the same version remains published.

What “stays” means

The text stays across a refresh because it is part of the page file. This is persistence through a published static artifact—not a browser memory trick, not a Muse conversation that the site can query, and not a database that updates itself.

The content changes only after Muse edits the file, Git-FED uploads the returned version, and GitHub Pages publishes the new version. Until then, the deployed page remains the last published copy.

What this does not do

A static page does not automatically collect new messages from Muse, synchronize edits, or save visitor input as shared content. If a future requirement needs visitors to submit data that everyone can see, it would need a real data service and an explicit design for access, privacy, and updates. Do not describe the current static page as providing that behavior.

For the host distinction, see Google Sites vs Pages. For an old-looking page after an upload, see Troubleshooting.