eldritch horrors 725f5cd358 docs: redo content generation for mdbook and manual ... manpages can be rendered using the markdown output of mdbook, the rest of the manual can generated out of the main doc/manual source tree. we still use lowdown to actually render manpages instead of eg mdbook-man because lowdown does generate reasonably good manpages (though that is also somewhat debatable, but they're a lot better than mdbook-man). doing this not only lets us drastically simplify the lowdown pipeline, but also remove all custom {{#include}} handling since now mdbook does all of it, even for the manpage builds. even the lowdown wrapper isn't entirely necessary because lowdown can take all wrapper arguments with command line flags rather than bits of input file content. This also implements running mdbook in Meson, in order to generate the manpages. The mdbook outputs are also installed in the usual location. Co-authored-by: Qyriad <qyriad@qyriad.me> Change-Id: I60193f9fd0f15d48872f071af35855cda2a0f40b		2024-04-11 13:32:06 +00:00
..
internal-api	Merge pull request #9099 from obsidiansystems/common-proto	2024-03-04 04:36:58 +01:00
manual	docs: redo content generation for mdbook and manual	2024-04-11 13:32:06 +00:00