Documentation improvements for onboarding

[dmccown]

Description

First time users of Habitat have a hard time getting started. There's a number of documentation improvements we could do to ease their onboarding.

• Publish a state machine for all Habitat related hooks. Indicate when and what order hooks will run in.
• Publish a state machine for all build steps a user would expect to interact with in plan.sh (or plan.ps1). Indicate what order they run and when you should override them.
• It should be easy to find what you're looking for in the documentation.
• Varbiable documentation. It's very hard to understand under which context which variables are available and what you should use them for.

[bdangit]

One thing I have noticed is that my early adopters at my work see a bunch of “random” text and have not clue how it relates to the plan build. All that is expected is as long as they see the successful banner they know they didn’t break anything.

However when things break, they choke and don’t know exactly where in the plan broke.

All in all, there is too much stdout. It would be nice that to:

1. Emphasis clearly what phase is being run (bold text, uppercase, brackets?)
2. Making things less verbose (at least the automatic stuff could be hidden to extent).

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.