So you've written a UNIX utility, library, or driver—or have started writing one—and you want to document your work in a manual. What happens next?

Practical UNIX Manuals: mdoc is a guide for writing portable and maintainable UNIX manuals (manpages) in the mdoc language.

Why mdoc? Formatters for the language are available by default on all modern UNIX installations and may be downloaded for non-UNIX systems. Furthermore, mdoc annotates content semantically, not presentationally, producing consistent manpages across systems. For an analysis of mdoc and competing formats, refer to Fixing on a Standard Language for UNIX Manuals, published in the USENIX magazine.

This book is structured first as a series of tutorials, then a guide to best practises: it is not a reference! For that, refer to your local mdoc manual.

I also feature the History of UNIX Manpages, which chronicles the development of manpages from the 1960s to the present day.

All content licensed under Creative Commons' Attribution Share-Alike: deriving works must attribute the author, Kristaps Dzonsons, and use a similar license. Citations should include the current version, 0.1.4, and date, 07 April 2014.

Polished (editing) text in various places. Cleaned up markup for more variable media. Removed XHTML (of course, it's still used for the ePub) in favour of clean HTML5.

Added GNU troff archives and edited content in Part 3 as suggested by an outside contributor (thanks!).

Major addition of the History of UNIX Manpages study. Also moved this page's Table of Contents to its own page (to free up space) and simplified this page. Valuable editorial fixes thanks to an outside contributor: fixed History links and clarified several concepts in the first few chapters among other improvements.