CORE CONCEPTS
Pages & Areas
Creating a Page means creating a perspective. Adding an Area means adding another timeline to it.
Creating a Page means creating a perspective. Adding an Area means adding another timeline to that perspective.
What is a Page?
A Page is a single perspective on your time.
- Daily Journal, Weekly Review
- Work Log, Project Alpha
- Sleep, Exercise
In the coordinate model, a Page represents the z-axis.
A Page is not just a saved filter
A Page is not a filter that hides or shows certain events. A Page carries its own purpose, Area layout, visible Calendars, arrangement, and the perspective you chose.
A filter decides what to hide or show. A Page decides how time is structured and interpreted.
What is an Area?
An Area is a parallel timeline inside a Page.
Daily Journal Health Product Development
├── Plan ├── Sleep ├── Research
├── Act ├── Exercise ├── Build
└── Review └── Recovery └── LaunchAreas are independent timelines
Each Area can independently have:
- Name, width, order
- Connected Calendar
- Visibility and property display settings
Even though every Area shares the same date and time range, each is treated as its own timeline.
Why all-day events repeat across Areas
Product note
An all-day event belongs to a date rather than a specific hour. Because each Area is an independent timeline, the event can appear at the top of every relevant Area.
Pages, Areas, Calendars, and Events
- Page — perspective
- Area — parallel timeline
- Calendar — the source or group of event data
- Event — a record on the timeline
- Property — structured data added to an Event
Page design guidelines
- A Page should answer one question.
- Areas should be distinct time flows.
- Don’t create too many Areas.
- Use a Property for simple categories; use an Area when you need a parallel timeline.
Example
If Project A, B, C are just categories, a Project Property fits better than Areas. But when you need to compare axes side by side — like Plan, Act, Review — Areas are the right choice.
Related concepts
Velprium