NUKnightLab / NUKnightLab/TimelineJS3
Design consideration to make the year more visible in particular situations
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.2k
- Forks
- 645
- PR merge metrics
- No merged PRs in 30d
Description
In particular, given a timeline with a large number of densely clustered events, the user must choose between a high zoom level, which may show the year but which results in a cluttered looking event bar ... or a low zoom level which gives more space to the events but does not display the year.
Is there a design consideration we could make which would show the year in the time navigation in cases like this?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the time-navigation implementation in TimelineJS3 and reproduce a timeline with many densely clustered events at both high and low zoom levels. Determine a design that keeps the year visible without making the event bar cluttered; done means the year remains readable in the described situations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100