Small notes for people maintaining structured copy

This site focuses on the practical questions behind storing text in JSON. It is written for people who maintain modest websites, edit interface wording, or inherit files with little explanation.

We distinguish between JSON syntax, project-specific content models, and conventions for discovering machine-readable files. Those subjects can overlap, but none automatically defines the others. A valid JSON document can still contain confusing fields or sit in an unsuitable location.

The guidance here favors explicit names, short documentation, and changes that another person can check. Where a filename has no established meaning, we treat it as a project decision rather than presenting it as a standard.