How to create an Open Liberty guide

This is a working draft that we're compiling to produce some nice, simple guidance to creating Open Liberty guides. This guidance should clearly explain:

• The scope of an Open Liberty guide.
  • What to include and what to leave out.
  • What to focus on.
• Structure a guide.
• Sample code in the repository that accompanies the guide.

It should also provide links to extra info in case the contributor needs it, eg:

• Using Asciidoc to write the guide.
• Running a local build of your guide to see how it looks.
• Creating a repo with folder/file structure and example repo to follow.