4 ms·
It is bound to actual release data! https://github.com/microsoft/TypeScript-Website/blob/v2/packages/typescriptlang-org/src/lib/release-plan.json https://githu
by orta 6y ago
It is bound to actual release data!
https://github.com/microsoft/TypeScript-Website/blob/v2/packages/typescriptlang-org/src/lib/release-plan.json https://github.com/microsoft/TypeScript-Website/blob/v2/pack...
The divs are updated every time the website is re-deployed, and it deploys often. This means we don't need to run JS to give you the right date info.
- jordache 6y agothanks for the info and that link to the source. Edit: Isn't this where the 55%, 28%, 17% widths derived from? Looks like a hard coded values? https://github.com/microsoft/TypeScript-Website/blob/d4c638ffb113ad0b91f0614569b7e2b6882ad803/packages/typescriptlang-org/src/components/index/UpcomingReleaseMeta.tsx#L54 https://github.com/microsoft/TypeScript-Website/blob/d4c638f...
- orta 6y agoAh, yeah that's what you mean - so the first time I built this graph I used the real dates and their difference from release to give accurate %s. This turned out to not work, because there wasn't enough space to fit the text underneath. I then explored making the graph vertical with accurate %s, but it still felt heavily one-sided at end with the beta/rc/release. all clumped at the bottom. The third iteration is this, I moved the release date up into a sentence above, then had a mostly representational but kinda accurate overview of the three release stages. I think it gets the idea of the phases across, works in all browser sizes etc and doesn't take up too much visual space