write up one use-case, test the template by @braxton, add to repo

[aaronkaplan]

• look at the template structure by braxton. Maybe clarify if some things don't work yet
• create one use-case that you have to this template description, add to repo
• same for tools for this use-case

[bplaxco]

@aaronkaplan adding an example implementation playbook has been steadily bubbling up my todo list. That being said, I had a question:

Given that this will be turned into a web page, how/where would you like me to include an example playbook and its files? I didn't want to link off to a directory with all the files in it and that just be a 404 on the built site. I could also generate an index.md with links to all the files, but that seems like it'd be tedious to keep up to date when there are changes.

Thoughts?

[aaronkaplan]

Hi @bplaxco good point. I think it might make sense to simply link the playbook and its files as residing on github in a subdirectory. This way, in the document, we can link to it. I will check with FIRST that certain subdirs are not exported to the web page... or ... we have a separate repo for the PBs