Each JSON article needs a stable ID, unique slug, publication date and modification date. The file also needs a schema version and update timestamp.
The useful answer depends on the purpose of the page, the people allowed to edit it and the cost of an error. A reliable workflow separates editorial decisions, technical delivery and final verification instead of hiding all three inside one automated operation.
The decision to make first
Version both data and structure. Adding an optional field is simple; deleting or renaming one requires an explicit migration and checks.
A practical method
- Assign an immutable ID independent of the title.
- Keep published slugs or prepare redirects.
- Use consistent key order for readable diffs.
- Check duplicates, types and dates before commits.
- Tag significant editorial batches in Git.
Checks before publishing
- The source of truth is explicit and can be restored.
- URLs, dates and visible claims match the delivered page.
- A human reviewer can reproduce the check without a hidden service.
The main pitfall
Reusing IDs or regenerating slugs creates collisions, broken links and lost history.
Recommended next step
Write a CLI test that counts items, detects duplicate slugs and validates required fields per language.
Verification workshop: evidence before a decision
A proposed exercise on a chosen scope, using fictional data where needed. Record what you observe; this scenario describes no test already performed on your website.
- Action to try
In a working copy, correct one JSON article sentence while retaining its ID. Compare before and after data, then regenerate the page.
- Record to retain
Keep the diff, JSON parser result and rendered page. Check that title, URL, relationships and neighbouring content did not change unintentionally.
- What this evidence does not establish
Valid JSON may contain a factual error. A stable ID alone guarantees neither correct release nor rollback.
A change worth versioning
A team corrects the response time stated in twelve JSON articles. It updates the source fact, records the twelve affected IDs, then checks that titles, dates and links were not changed accidentally. A file comparison before release shows exactly which answers were edited.
Keep a stable ID for every article and validate JSON before deployment. A one-sentence correction should not create a new URL or erase history. Record why the change was made and who approved it.