Timeline concept#17
Conversation
|
This is great! 🎉
Or use SVG? I wrote MDN's inheritance diagram in SVG years ago: https://developer.mozilla.org/en-US/docs/Web/API/SVGTextElement (source) |
| {% if version %} | ||
| { | ||
| "event": "{{ browser.id }}", | ||
| "date": new Date("{{ browser.releases[version].release_date }}"), |
There was a problem hiding this comment.
This will need fixing with the recent change where certain versions can contain the ≤ character. For example the sub-sup feature.
|
Future idea: also use data from browser-specs to add timeline key events from specs. Ideally, if we were also tracking dates for explainers, and intent to prototype/ship emails, that would be great. |
Mermaid supports timeline diagrams, I wonder if that could help? |
|
That's awesome! Thank you for sharing, Will. |
|
I hacked on a similar concept a while ago, figured I'd share it here: https://rviscomi.github.io/timebase/. It doesn't show the timeline for an individual feature, but it arranges Baseline moments for all features onto one big timeline, past and future. |
Playing with the idea of a timeline for features, discussed with @Elchi3.
A few work in progress screenshots below.
Grid

Font-synthesis

Async clipboard

We might need to leverage a graphics library to deal with overlapping labels, and to make things generally nicer.