Add demo & usage documentation

[arschles]

After #192, add documentation in doc/DEMO.md for what resources to watch and what state the cluster should be in after each action in the demo run-through

[arschles]

Removing from alpha 2. Demo documentation is sufficient at this point, given https://github.com/deis/steward-demo-s3 is in order

[arschles]

This issue has changed a bit. We've split steward into two components as of now:

• steward-framework: the Go SDK for Kubernetes resource and control loops
• steward-cf: the CloudFoundry broker API implementation on top of steward-framework

Documentation of the kind described herein should still live inside this repository, but it shouldn't just be for demos. It should be extended to general usage. I've changed the title of this issue accordingly.

[CoolatMax]

Hi @arschles,

I’ve been going through the history of this issue and the later clarification about expanding this beyond demo-only docs into general usage, especially after the split into steward-framework and steward-cf.

Before starting work, I wanted to confirm alignment on scope. My current understanding is that this documentation should:

Describe a demo run-through with clear expectations (resources to watch and expected cluster state at each step), and

Extend into general usage guidance explaining how users typically work with steward-framework and when steward-cf fits in.

My thought was to place this under doc/ (either as an expanded DEMO.md or a combined demo + usage document) and focus on observable behavior rather than just commands.

Does this direction still match what you had in mind, or is there a particular structure or focus you’d prefer at this point?