# What is Glider: Core concepts

> The eight nouns the rest of the documentation assumes you know.

Glider documentation · Getting Started · Web page: https://cgglider.com/docs/overview/concepts/

Sections of this page: [Introduction](https://cgglider.com/docs/overview.md) · [Core concepts](https://cgglider.com/docs/overview/concepts.md) · [Anatomy of the editor](https://cgglider.com/docs/overview/anatomy.md) · [Reading paths](https://cgglider.com/docs/overview/who-its-for.md)

| Concept | What it is |
| --- | --- |
| Page | The saved document. Holds scenes, data, units, animations, files and the rundown. |
| Scene (layer) | One composited surface of components. Canvas scenes go to air; control-panel scenes never do. |
| Component | A node on a scene: text, image, video, lottie, button, bar, chart, rectangle. |
| Store | The page's live key/value data at runtime. Everything readable is a path into it. |
| Binding | A link from a component input to a store path, so the graphic follows the data. |
| Unit | A declarative behaviour — clock, counter, ticker, formatter, watch rule, poller — that writes to the store. |
| Reaction | An event/condition/action rule: when this happens, do that. |
| Workflow | A named animation timeline with in / loop / out phases, targeting scenes, groups or nodes. |

> **Note:** Units write to the store, bindings read from it, reactions react to it, and workflows animate what bindings paint. That one sentence is the whole data model.

![Poller → store → binding → component, with a reaction firing a workflow.](https://cgglider.com/docs-shots/overview-concept-map.png)