Open orta opened 5 years ago
"how do we handle JS"
covers a lot of the flaws if you're a JS dev trying to add TypeScript definitions - https://hueniverse.com/24-hours-with-typescript-638485d61c87
tsserver plugin dev notes dts linting for a JS + dts project
lots of documents + samples for project references
How to lint half js/ts projects: https://www.reddit.com/r/typescript/comments/caipx7/linting_a_half_js_half_ts_project/
Website
Nav
Six main navigation components
Then there is:
Optional, but maybe worth it? (if so, thinking from day one is useful)
Homepage
Not been thought of too hard yet, but some ideas
I've done redesigns of a few big JS project homepages:
So, I feel pretty comfortable getting reasonable fidelity mockups and presenting those to some MS designers who can help make it fit better.
Handbook
Website may come out before new handbook, so have to build with the 2nd in mind.
Note that the URLs will change across handbooks, so ideally we keep a forwaring map of the closest approximation of pages
Guides
A general idea of the guides heirarchy
Getting Started
From Scratch
From an existing project
Improve your tooling without adding adding dependencies
Integration with build tools
Converting a JS project to TS (current guide)
Building at Scale
Definitely Typed
Migrate the content of the definitely typed website into TS and update it
TypeSticter
A set of documents which guide you through turning on some of the strict flags in the tsconfig explaining with examples how they affect your code
noImplicitAny
noImplicitReturns
strictNullChecks
strictFunctionTypes
Blog
Same as current, maybe start encouraging folks write their own non-release notes post in there?
Playground
Embrace, extend and enhance
typescript-play
. I audited the code last night and it's pretty solid, and really simple.Things we like which it supports:
Extend:
Export to
Open code in
Stretch goals:
Community
Talks to the scope of people using TS, how you can meet others to talk to it or learn more