The five ideas
Five words explain all of Kaizendex: collection, property, entry, view and block.
| Idea | In one line | Example |
|---|---|---|
| Collection | A list of one kind of thing. | Workouts |
| Property | A field that every entry in the collection fills in. Each property has a type. | Distance (Number), Type (Tags) |
| Entry | One item in a collection. It holds one value for each property. | “Morning run”: Distance 5.2 km, Type Run |
| View | One way to show a collection’s entries. | A table, a calendar, a board |
| Block | One piece inside a Block page or a Dashboard property. | A paragraph, a photo, a chart |
The shape and the data
A collection and its properties are the shape of your data. This shape is also called the schema: the plan of what each entry holds. The entries are the data. Each entry fills in one value for each property.
When you add a property, such as Duration, you change the shape. Every workout can then hold a Duration. When you log “Morning run”, you add data.
Blocks
Most properties hold one value: a number, a date, some tags. Two property types hold blocks instead:
- A Block page holds blocks from top to bottom: paragraphs, headings, photos, charts.
- A Dashboard holds blocks as tiles that you drag and resize. A dashboard is an entry with one Dashboard property.
In the app you rarely see the word “block”. You click + Chart, + View or + Photo. See Block pages and dashboards.
The one rule to remember
Every entry lives in one collection, and that collection always shows it. Putting “Morning run” inside another entry, or showing it in a chart, never moves it out of Workouts. Only a filter you add hides an entry from a view.
What “page” means
A page is only a screen. The entry page shows one entry. The collection page shows one collection, with its views as tabs. The hub page shows a hub: a tab bar of your own, in the sidebar. You never make a “page”: you make collections and entries.
Read next
The full model, with Parents, links and the tree, is on one page: