Public · Information modeling
Timeline
A workspace for constructing timelines from point events, ranges, categories and linked stories so a temporal sequence can become a structured, navigable explanation.
- Niche
- Timelines that need relationships and narrative, not only dates
- Core stack
- Static web application · responsive design
- Model
- Events · ranges · categories · stories
- Focus
- Narrative structure · navigation · publishing
System view
The niche
A useful timeline is rarely just a sorted list of dates.
Timeline is aimed at research, project history and other domains where point events, sustained periods, overlapping categories and an editorial story connecting those facts all need representation.
What is different
The model separates temporal facts from the narrative assembled from them.
Point facts and duration ranges retain different semantics rather than collapsing into equivalent markers.
Classification lets a chronology be explored by theme without destroying the common temporal order.
A story selects and relates facts to explain a trajectory without mutating the source data.
The same structure must remain readable from a phone to a wide desktop view.
Product & design thinking
The product distinguishes recording, organizing and interpreting.
A user can capture events, group them by category and then construct a story from them. That separation prevents narrative prose from becoming the only place where facts live.
The interface uses horizontal space when it exists but must preserve linear reading and editing on narrow screens so chronology does not depend on an infinite canvas.
Development approach
The design process alternates between two views of the same material: the strict chronology and the story a person is trying to tell with it.
Instead of choosing a spectacular visualization first, experiments begin with real event/range/category/story combinations and deliberately awkward screen sizes. When a visual idea helps interpretation without damaging the underlying facts, it graduates into the shared model and responsive rules.
That is faster than a traditional mockup-to-build handoff because narrative experiments happen against working data from the start. Validation and publishing checks preserve the factual structure while the presentation is free to keep evolving.