# Page Data

> The JSON the page owns, and the store it becomes at runtime.

Glider documentation · Data · Web page: https://cgglider.com/docs/page-data/

Sections of this page: [Editing data](https://cgglider.com/docs/page-data.md) · [Paths](https://cgglider.com/docs/page-data/paths.md) · [The runtime store](https://cgglider.com/docs/page-data/store.md) · [Reserved paths](https://cgglider.com/docs/page-data/reserved.md) · [Keys view](https://cgglider.com/docs/page-data/keys-panel.md)

The Keys and JSON views of Logic → Data.

Logic → Data is the page's seed state: a JSON object whose paths bindings, units and reactions all read and write. It has two faces of the same data — Keys, a clickable tree that binding picks from, and JSON, the raw document that authors keys.

```json
{
  "title": "My Scene",
  "score": 0,
  "items": []
}
```

- The root must be a JSON object; an array or a scalar is rejected.
- Invalid JSON is reported inline and nothing is written.
- Format tidies the document; applying shows a brief Saved indicator.
- Arming a field for binding forces the Keys view forward.

> **Edit through the app:** Do not hand-edit data/pages/*.json while the dev server is running — the running app rewrites the file and your edit is lost. Use the editor or the HTTP API.

![Logic → Data in Keys view.](https://cgglider.com/docs-shots/data-keys.png)