Figure out a script to maintain the "how to use" command documentation about drupal-console-book

[jmolivas]

This sounds interesting, we can create a few twig templates and render the available commands md files.

[LowellMontgomery]

Right... I was thinking about it during the initial copy/paste/format repetition: "surely we can automate this" ;-)

Maybe the documentation and project could be in one repository for this to be most ideally implemented? Command/API documentation could be re-generated (perhaps even automagically) whenever the commands are updated or new ones added. I'm not yet the Git geek some are, so I'm not sure how to implement it, but then the command documentation could be in both repositories (the "book" and the actual Console), included in one from the other. Having the most critical "API docs" in the same repository as the Console could also just be handy for users.

[jmolivas]

@LowellMontgomery I just send a PR hechoendrupal/drupal-console#868, on the DrupalConsole repository.

This PR provides a new --generate-doc option to automate documentation generation.

[jmolivas]

I sent another PR hechoendrupal/drupal-console#877 this one includes the generate:doc command, this command iterate each DrupalConsole core command and generates the proper Markdown files.

You must run the generate:doc command within a Drupal 8 installation.

$ console.dev generate:doc --path=/path/to/your/repo/drupal-console-book/

[jmolivas]

Cosidered closed since generate:doc:gitbook command is working properly