Ya, same for FreeBSD. You can literally operate a system with nothing but the handbook in most cases - the documentation is much more systematic and developed than Linux. What you get isn't just a "how to use a GUI" tutorial or manpages, it's a comprehensive look at how you do routine sysadmin tasks. The kind of thing that Linux pushes off to web tutorials or stackoverflow.
Compare:
https://help.ubuntu.com/lts/ubuntu-help/index.html
https://docs.freebsd.org/doc/13.0-RELEASE/usr/local/share/do...
It of course helps that nothing ever changes in BSD-land. After 50 years of development, they are largely feature-complete and are not going to be doing massive changes just for the sake of massive changes. As such they get much lower levels of "documentation rot", things rust a lot slower when nothing ever changes and as such it's a lot easier (and more productive) to build comprehensive documentation.
But the amount of churn in linux is insane, Ubuntu has used three completely different init systems in the 15 years since I started using Linux seriously. For java development, I routinely see and use StackOverflow answers from like 2009 that are completely valid still, and yet answers from that era are completely useless for Linux, which has invalidated that acquired-knowledge twice since then. You can pretty much sysadmin FreeBSD out of the handbook, and if you need to search then an answer from 2009 is usually still valid.
It's absolutely a cathedral-vs-bazaar situation. Cathedral is presented as a negative in that metaphor, but the cathedral ensures enough stability that you can start Having Nice Things instead of just constantly scrambling to rewrite everything every time a vendor thinks they've built a better mousetrap.