void-docs VS web

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.

Sure, at some point you're going to be relying on some 3rd party somewhere. We use a VPS and not a bare-metal hand-installed rack, and we rely on an electrical company and not a hand-turned crank to power our servers. As far as email goes, It's simply not possible to self-host transactional email in 2024 if you want it to arrive in an inbox and not a permanent spam blackhole; likewise it's not possible to accept money without involving a 3rd party service like Fractured Atlas or Stripe or PayPal. (Moving away from GitHub towards a self-hosted Git solution is actually on our long-term todo list[1]).

All those things doesn't mean you can't run your web app on a single tiny server, and that outsourcing the basic underpinnings of your web app, like the OS, runtime, and database to some cloud service, or that resorting to flavor-of-the-month frameworks or containers, will result in complexity and bloat.

[1] https://github.com/standardebooks/web/blob/master/README.md#...

Hey a little later to the party here but I'm really enjoying this. I started reading a book with it and while I agree with others it's not great for grammar it certainly shows me many new words without requiring me to read at a glacial pace.

PS: You should def try to include some books from https://standardebooks.org/ which are much nicer formatted than the ones you're using from Project Gutenberg.

Good luck and I hope you can keep building this out. Already the update to tap anywhere to close the word definition is a nice improvement :)

A number of e-book platforms are discussed on my blog, which dives deeply into the technical nuances of typesetting a few[1]. Ultimately, I typeset a classic from Standard EBooks[2], Dr. Jekyll and Mister Hyde[3].

[1]: https://dave.autonoma.ca/blog/2020/04/11/project-gutenberg-p...

[2]: https://standardebooks.org/

[3]: https://dave.autonoma.ca/blog/2020/04/28/typesetting-markdow...

As an aside, for anyone looking for free classic books to read on their various eReaders, these are very well done: https://standardebooks.org

It is the same when you download a kepub book from standardebooks.org. You will have the epub file with kepub features.

> https://standardebooks.org/

Standard Ebooks is seriously impressive. One of my favorite sources of books in the public domain.

I’d also add in addition to this excellent list of DRM-free ebooks, it’s always worth looking into borrowing a book from the library via Libby/Overdrive.