Learn & Docs
How We Pick Resources for the Directory
The simple criteria behind every link in the catalog — and how to suggest one.
Every entry in this directory is hand-picked. We are deliberately not trying to list everything — a directory that includes everything helps no one. Here is the bar a resource has to clear.
The criteria
- Still maintained. Active development or a stable, still-correct reference.
- Broadly useful. It should help a wide range of developers, not one narrow stack.
- Free or fairly priced. Paid is fine when the value is obvious; we say so.
- Good docs. If we can't get started in ten minutes, neither can you.
Categories and tags
Each resource lives in exactly one category and carries a handful of tags so you can browse by topic across categories. Looking for somewhere to start? The Frontend and Developer Tools sections are the busiest.
Suggesting a resource
Found something missing? That's the whole point of a curated list growing over time — open an issue or a pull request with the link and a one-line reason it clears the bar.