MARKED-MAN(1)

πŸ’– NAME πŸ’–

marked-man β€” it's giving markdown to roff, bestie ✨


🌸 SYNOPSIS 🌸

marked-man README.md > doc/foo.1
# works too with stdin
cat README.md | marked-man --version 1.0 | man /dev/stdin

Also lowkey check out the marked documentation, fr fr πŸ“š


✨ DESCRIPTION ✨

So marked-man wraps marked and extends it with groff output support, and the whole point of that glow-up is so you can create Unix manual pages for use with man. Iconic, honestly. πŸ’…

It follows the ronn markdown level-1 header format:

# name(section) -- short description

and that line right there populates the HEADER section, plus the NAME section too (but only if you haven't already written one yourself, no cap). πŸ‘‘


πŸŽ€ OPTIONS πŸŽ€

marked-man is a marked CLI extension, meaning options can be passed directly to marked. Bestie, you have full access, go wild πŸ¦‹

The --breaks option β€” the one that retains intra-paragraph line breaks β€” is now true by default. So if you want it off, use --no-breaks to disable it. Periodt.

marked-man also adds some options on top of marked's existing options, so you can override the header/footer of your generated man pages. Very main character of it, honestly.

  • --name <name> β€” Optional! Overrides the name in the ronn header. πŸ’œ
  • --section <section> β€” Optional! Overrides the section in the ronn header. Defaults to 1.
  • --description <description> β€” Optional! Overrides the description in the ronn header.
  • --version <version> β€” The version shown in the manpage footer. Optional β€” when you omit it, it defaults to the target node module version, or empty. πŸ™ˆ
  • --manual <manual> β€” The manual-group name shown in the manpage header. Optional β€” when you omit it, man displays a value matching the section.
  • --date <date> β€” The date shown in the manpage header. Optional, and it defaults to now. ✨ Must be acceptable to new Date(string or timestamp). It also honors the SOURCE_DATE_EPOCH environment variable for reproducible builds. Reproducibility? We love her. 🫢

🧚 INSTALLATION 🧚

Go see your node package manager manual... you got this, bestie πŸ’–

For example:

npx marked-man simple.md

🌈 EXAMPLE 🌈

Wanna view this README as a man page? Run something like the following:

marked-man README.md | man /dev/stdin
ok that pipe into man /dev/stdin is genuinely such a slay, no notes πŸŽ€

πŸ’… AS MARKED EXTENSION πŸ’…

import markedMan from 'marked-man';
import marked from 'marked';

marked.use(markedMan);

πŸ‘‘ SEE ALSO πŸ‘‘

  • Ronn
  • Ronn-NG
  • groff

πŸ’€ REPORTING BUGS πŸ’€

See the marked-man repository. (Yep, that's the whole vibe β€” go check the repo, bestie.)


so like... that's literally the whole page. marked-man, version 2.1.1, from June 2026, General Commands Manual energy, and the manual name is MARKED-MAN(1) in case you forgot πŸ’œ mwah, go write some man pages πŸŽ€βœ¨

πŸ“¦ where this page comes from