void-docs VS pandoc

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.

My main authoring tool is then Emacs Markdown Mode (https://jblevins.org/projects/markdown-mode/). For data entry, it comes with some bells and whistles similar to org-mode, like C-c C-l for inserting links etc.

I seldom export my notes for external usage, but if it is the case, I use lowdown (https://kristaps.bsd.lv/lowdown/) which also comes with some nice output targets (among the more unusual are Groff and Terminal). Of cource pandoc (https://pandoc.org/) does a very good job here, too.

This is one of those things that the ever-amazing pandoc (https://pandoc.org/) does very well, on top of supporting virtually every other document format.

Folks feel the same way about Markdown versus LaTeX: why use something significantly more complicated where a looser, human-readable grammar works better?

For any other situations, I use https://pandoc.org/, or, generate a Word doc scriptomatically.

pandoc toolchain pour builder une version confortable/imprimable en phase de travail (ePub, pdf, docx, html)

Congrats on the launch, I guess, but there are so many free options that I can't think of a situation where paying $0.25 per document would be justified...? Just to name a few:

Back in the days, I used to use XSL-FO [0] and it was okay. It was not very precise but it rarely if ever broke, and was perfectly integrated with an XML/XSLT solution. Yeah, this was a long time ago.

Last month I used html-to-pdfmake [1] and it's also not very precise and more fragile, but very efficient and fast.

Yet another approach would be to pro grammatically generate .rtf files (for example) and use Pandoc [2] to produce PDFs (I have not tried this in production but don't see why it wouldn't work).

[0] https://en.wikipedia.org/wiki/XSL_Formatting_Objects

[1] https://www.npmjs.com/package/html-to-pdfmake

[2] https://pandoc.org/

Others have mentioned static site generators. I like Hakyll [1] because it can tightly integrate with Pandoc [2] and allows you to develop custom solutions if your needs ever grow.

[1]: https://jaspervdj.be/hakyll/

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

Have you compared it with a conversion by pandoc (https://pandoc.org/)?

I have used it to kickstart a blogging project that I wish to come back to soon. The Lua inter-op for custom readers, writers and filters is great but I wish there was more editor integration and even perhaps an official IDE/editor with built-in debugging features (probably something already do-able with Emacs but I haven't checked). The only blocker for my project is no support for "ChunkedDoc" for Lua filters [1] which forces me to write more code and a complicated Makefile.

[1]: https://github.com/jgm/pandoc/issues/9061