EditStatic

Docs / Reference

Saving and history

Nothing is saved until you press Save all. Then each change goes into your code as a commit, so every version is kept and any change can be undone.

From Save all to your code

  1. Save all sends each changed text, before and after, to your host.
  2. Your host adds it to a queue in your repo: a small file in .editstatic/pending/ on the staging branch. The bar says Saved. Publishing.
  3. The GitHub Action finds each text in your code, writes the new words, records the outcome, and commits as EditStatic.
  4. Your host deploys that commit. The bar says Published, or names any change that couldn't be saved.

The whole trip takes about a minute, most of it your host's build.

Changing the same text twice

You can keep editing while a save publishes. Saves are applied in the order they were made, so a second change to the same heading applies after the first.

When two people edit the same page

On plain HTML pages, a save is refused when the page changed since it was opened, and the editor asks for a reload. On React sites, each change is matched on its old text: if someone already changed that text, the change is refused instead of overwriting theirs.

Undo a change

git revert 3fa2c1d
git push

Settings: editstatic.config.json

{
  "sources": ["."],
  "ignore": [],
  "build": null
}