Migrate behaviour to go generate ./...

[ChausseBenjamin]

In most cases, end-users don't need to be capable of generating documentation for the software they use. They only need it to be accessible somewhere on their machine.

Following that train of though, it feels a bit wasteful to include a text generation as part of any application only for the sake of generating documentation.

However, Go has tooling builtin for generating text/code which can be run outside of a compiled go program: go generate ./.... What would be the sentiment towards making cli-docs more of a code/text generator instead of something that gets compiled into an application?

A good example of code generation being used is 99designs/gqlgen which generates method templates for an API implementation. In this case, man pages and markdown could get generated instead of code.

I know this is a big philosophy change which might not correlate with your vision. I'm just throwing the idea out there as it occurred to me :)