The "pytransform3d User Guide" is essentially a full textbook. Insane level of detail and quality from a project that is (I think) one dude's side project.
I don't think jquery's api ref (with all of its keyboard shortcuts for searching and navigation) will ever be beat, but nobody makes stuff like that anymore because the inspector exists now and everything has an IDE.
Also have a really high opinion of Apple's books for learning Objective-C
also it's not the official docs, the official one is https://discord.dev - the .sex one is a community made one which includes non-bot API endpoints (like account creation, captcha solving and many other routes that are not meant for bot accounts, which discord itself doesn't document)
as the owner of the domain https://estupi.do I approve of this. if i run into any trouble making the discord bot i've been envisioning, i'll be sure to reach out
https://fastapi.tiangolo.com/ is an excellent product that is really well documented , it introduces the concepts really well and explains what the code means. Its not just exported docs it carefully structured to help you learn.
Honestly, a lot of Rust has excellent documentation imo.
The whole standard library is full of detail and examples, official books, such as the Rustonomicon, provide even more detail, and popular crates like tokio are also well-documented.
Even non-doc comments can be insane (my fav example linked)
Comments
https://dfki-ric.github.io/pytransform3d/user_guide/index.html
Also have a really high opinion of Apple's books for learning Objective-C
And Emacs Lisp, but only within Emacs (describe-function plus access to all source code makes understanding all functions far easier)
especially these two pages of actual scenarios/use cases you might need
https://docs.pytest.org/en/stable/how-to/index.html
https://docs.pytest.org/en/stable/example/index.html
Tagging @estupi.do
https://docs.astro.build
https://svelte.dev/docs
The whole standard library is full of detail and examples, official books, such as the Rustonomicon, provide even more detail, and popular crates like tokio are also well-documented.
Even non-doc comments can be insane (my fav example linked)
Perl (CPAN included)
TeX, if you read the TeXBook, but that's literature.
...
...
N O T
I think what I mean by best is that the general flow of the documentation works very well at helping you understand the basics of the project.
It should also easily allow you to transition into more advanced topics.