Determine way to automate maintaining SUMMARY.md about drupal-console-book

[jmolivas]

Probably won't be that complex to create a script to iterate the directories and scan md files extract h1 # to generate the links, we may need to rename files as 01_ to set the order of the links within a directory.

[LowellMontgomery]

Right... just what I was thinking.

We could even have a standard that anything directly under the H1 could be taken as a "page synopsis" that could be used as the link title (for better UX / SEO, i.e. so people more easily find what they want).

Even cooler might be to also parse H2s and allow jumping directly to them... on pages where there is enough information that this could be useful. I'll create a new branch for the few necessary file changes. Then I'll look for an existing script or write one and share it... it might be useful for other projects, but that thought suddenly seems so true that I'm sure it must exist already, which could allow us to continue to build on "proudly found elsewhere". ;-)

[jmolivas]

@LowellMontgomery: I am planning to add a new command that takes advantage of PR hechoendrupal/drupal-console#868 I mentioned on the other issue #53

This command will iterate each one of the commands and generate both
Index
https://github.com/hechoendrupal/drupal-console-book/blob/master/commands/available-commands.md
And each command page
https://github.com/hechoendrupal/drupal-console-book/tree/master/commands

I can add some logic to read the repo files and generate the Summary file as well
https://github.com/hechoendrupal/drupal-console-book/blob/master/SUMMARY.md

[jmolivas]

Summary section related to Available Commands is now automatically generated by the new generate:doccommand.

[jmolivas]

@LowellMontgomery Closing this one, feel to open or create a another issue for new ideas for improvement the doc automation.