void-docs VS s6-man-pages

In general, Void assumes familiarity with the principles of Linux and UNIX system. Basic questions about configuring or running a Linux system can frequently be answered with a Google search. The Internet grew up with UNIX, and Linux grew up on the Internet; you are encouraged to avail yourself of the extensive body of knowledge already out there. Some particulars of Void administration are described in the handbook; consult this document before asking common questions about configuring Void systems.

I know for sure that these images work with espeakup, and espeakup can be enabled at boot by adding live.screenreader to the command line as described here

You might look at https://docs.voidlinux.org/, which provides a good overview of Void. The package manager, xbps is [my opinion] better that apt [I have to use the latter in AntiX Linux].

the final criticism i have for void is the way they have decided to host their docs; as this void-docs. This bottlenecks the possible amount of expertise you'd receive from your doc writers by ensuring that only those who want to learn git are able to contribute to your docs. this, to me, is very inadequate if your intent is to have documentation written by those who are very good at docwriting but not necessarily maneuvering in version control systems like git. i'm not sure what the impetus was to move away from the traditional wiki model, but this from my perspective is a failure.

Follow the guide on the void website and you will be fine. Come here for support, we love helping others out and it's a great community, on par with the OpenBSD community as far as being helpful and encouraging you to learn the OS. If you find there's a package you need that hasn't been added to xbps yet, you can use a Flatpak or AppImage (easy way) or build the package yourself using xbps-src (advanced way, worth learning down the line).

I just made a PR on their github to add this.

Perl has traditionally been my language of choice for this sort of stuff (e.g. this script for converting mdBook to LaTeX), but more recently i've been focusing on POSIX shell scripts as a personal challenge and learning exercise.

from https://docs.voidlinux.org/

Understanding how runit manages services is critical. Also, there are certain "restricted" packages that xbps can manage but not download. The handbook does a good job covering both topics.

Finally, as someone who has put, and continues to put, a lot of volunteer effort into providing quality documentation (e.g. my work thus far on the Gentoo wiki, my work on the Void docs, my work porting the documentation for the s6 ecosystem), i can tell you it's frustrating and discouraging to put in all this work to provide helpful documentation to others - rather than having to write the same things in discussion threads again and again - and to continually improve it, only for people to ignore it in favour of some random (and often inaccurate) tutorial. So personally, i'm fine with the fact that, since the OP's question quickly got succinctly answered, people here subsequently wanted to (non-condescendingly) make sure the OP primarily used the Handbook.

Ultimately, my perspective is "let's try out a plethora of different approaches, and learn from experience what does and doesn't work in which situations". So i'd be all for a 'MiniHTML' effort (even if i don't end up getting involved myself), which i've seen many people suggest - but there doesn't seem to be any such effort that has gained momentum. Partly, i suspect, because of the common ICT phenomenon of "I want this, but someone else will have to work out the implementation details" (where the devils are). One personal example of this is of lots of people demanding man page versions of the s6 documentation, and lots of people talking about how this could be done, but no-one actually rolling up their sleeves - until i just got the bit between the teeth and did the work.

Well, indeed, i certainly wasn't expecting you to do so! But i already have more than enough volunteer FOSS stuff on my plate as it is (e.g. Ebuku, pulseaudio-control, s6-man-pages, execline-man-pages and guides, amongst various other things), and not using mold with gcc 11 is no problem for me at this point. So i've just noted the issue with the patch on the wiki page, and the patch will have to be updated by someone for whom it's more important.

About the man pages issue, Laurent Bercot (the creator of s6) already mentioned why he does not include man pages with s6 (here)[https://skarnet.org/cgi-bin/archive.cgi?2:mss:2583:202008:liednclklokjhnokhdhg]. You can find s6 man pages (here)[https://github.com/flexibeast/s6-man-pages] (those are made by flexibeast, using the online s6 documentation).