Capabilities
A capability is a power a page uses when it needs to do more than show something: fetch and hold data, work with the app’s records, move between the app’s pages, or react to what a visitor does.
Blocks are the visual pieces; capabilities are what makes them work together.
The four
| ID | What it does |
|---|---|
platform/persistence | Fetching data and holding it: the page’s data sources and its state, such as a search box’s text or the selected filter. |
platform/entities | The app’s data models: what a record looks like, and creating, reading, updating and deleting records. Forms that save records use it. |
platform/navigation | Moving between the pages of the app. |
platform/interaction | Rules that react to what happens on a page: when a visitor does this, do that. |
Appearance is not a capability. The theme is set once for the whole app; see Blocks.
Sign-in is not one of the four either. It is part of the app’s sign-in and access settings; see Sign-in & roles.
Where they come from
Capabilities come from packs, like blocks. The foundation pack, which every project starts with, carries all four.
You do not declare them by hand
Describe what the page has to do — “save each booking”, “list the products with a search box”, “open the detail page” — and the agent puts the right capability, and its settings, into the page.