I think now is a good time to start thinking about a “Pijul Manual”. The man pages are important to write because being able to write something as man pijul-<subcommand> would be awesome and wanted by end-users. But the language is… meh.
Any feedback about the manpage-writing process? Ideas on tools to use?
Great! Apparently pandoc can convert markdown to man pages (with the -t man option). I’ve never tried it, though…
Also, it might be nice to display the man pages when someone types, e.g., pijul help init or pijul init --help. Git, hg, and darcs all do some version of this (git and darcs seem to use pagers by default, while hg doesn’t), so there’s precedent.
Have you thought about going the git way of using asciidoc as the input language and generating man pages, html and info documents from there. I admit, it takes creating some build infrastructure at first (Windows support might be a show stopper) but is extremely lightweight on the side of actually writing documentation.
And making it easy to write new documentation seems to be a lot more worthwhile than having a lean build system.