It would be interesting to take a step back and consider what man pages actually are. Are they documentation structured in a specific way, dating back to Unix o

It would be interesting to take a step back and consider what man pages actually are. Are they documentation structured in a specific way, dating back to Unix origins, or are they what the user sees if they type "man command" on the command line? Because if we consider the latter, I think it will be much easier to see radical improvement of the "man experience" If I type "man ps" I see Man: find all matching manual pages (set MAN_POSIXLY_CORRECT to avoid this) * ps (1) ps (1p) Man: What manual page do you want? What if I instead saw Man: find all matching manual pages (set MAN_POSIXLY_CORRECT to avoid this) * ps (1) ps (1.tldr) ps (1p) Man: What manual page do you want? where the man command retrieved that information from the TLDR-pages site? In the last years we have seen many innovative Rust re-implementations of classical commands such as cat, find, grep. Maybe the man command is next up?