Official documentation from various distros are usually more accurate in the information they provide for their particular distro than sundry other sources online like blogs, youtube videos and articles from unaffiliated websites. That said, there is some excellent information found in non-official sources, but one often needs some experience to assess it's value.
A user of documentation after some experience of learning linux will likely find that there's a lot of generic information that crosses over various distros, so at some level of advancement with linux, it's often worth not disregarding what is on offer from documentation projects of distros other than the user's targeted one.
Out of interest, taking a look at documentation data at distros which I've found useful in the past: debian, arch and gentoo, I entered search terms to see the number of items they held on those terms. The search terms were entered into the search boxes at each distro's documentation website, which were here:
https://www.debian.org/doc/,
https://wiki.archlinux.org/title/Main_page, and
https://www.gentoo.org/support/documentation/. The results were as follows:
Code:
Numbers of articles for search terms
====================================
Search term Debian Arch Gentoo
----------- ------ ---- ------
graphics........................602 618 547
intel graphics.................. 40 404 328
intel graphics kernel options... 40 179 220
A few observations:
Refining terms helps with reducing outputs.
Quantity is not quality, so searchers need to use their discrimination.
Considering output, one needs to differentiate between distro and generic info.
On the matter of init systems mentioned by
@ron.alan in post #2, it's worth noting that systemd in debian is integrated well beyond just init functionality. Here's an image of the directory holding systemd units that are currently on a debian system.
It can look like one is drowning in systemd but it does all work quite well.
It's worth noting that sites can be searched from external search engines as well using code like:
site:archlinux.org graphics, which may output different results.
