Concept Guide Help Subcommands

[t-mart]

With clap, is there a way to express "concept guides"?

For example, with git, concept guides are purely informational help outputs under the git help space. They do not refer to actual subcommands on the git command itself. Git's concept guides can be listed with git help --guide and include things like "core-tutorial", "everyday", "faq", and "glossary".

Concept guides are useful for things that cross-cut or compose your CLI API that would be redundant or too high level to state in each related subcommand's own help documentation.

So, can I make these with clap?

A given solution should:

• take a short description string (for describing the guide in myprog help's output) and a string of the actual guide content.
• not replace the autogenerated help subcommand for actual subcommands on the CLI. In other words, we just want to augment it.
• (Bonus) be composable with an existing a derive-defined CLI (even if it has to use builder APIs)

[epage]

To do this right now requires manually implementing the help command.

Feel free to create an issue if you want to explore a design for this. Overall, it won't be a priority for me as there are other areas calling my attention.

[t-mart]

That's fine, Ed. Thank you for your consideration. Just knowing the fact that this requires manual intervention (and would not be available "out of the box") is helpful.