add Steps component

[nreese]

Needs some CSS work to use variable instead of hard coded colors and sizes but otherwise is complete

[snide]

CSS will need to be rewritten for this to use our usual sass variable stuff, and I'll also likely change the defined classes (like title and text) you're defining to just use existing components (like EuiTitle and EuiText).

Functionality seems ok and @cchaos or I can make those changes in a subsequent PR.

[cchaos]

I can handle the CSS updates.

[nreese]

@snide @cjcenizal Should the content of each step be more riggid? Like pre-text, commands, post-text? Or, should it just be any generic node?

[snide]

@nreese I think you want generic nodes. It's more flexible. The docs can always handle use cases for what to stuff in there (which is what I'd recommend in your examples... like showing a full instruction with code / text mixed in...etc).

[cjcenizal]

Should the content of each step be more rigid?

I think it's perfect the way it is now. I think more rigid components for various formats of content may belong closer to where EuiSteps is consumed. If we want to provide guidance on how this format should look, then maybe we can document it in a sandbox or in a new "Patterns" section.

[cchaos]

@snide Do we want to be able to customize the step coloring?

[snide]

@cchaos Probably. I'm thinking more in a sense of a trackable step (ex: primary are completed steps, gray for incomplete ones...etc). We'd want to set a default though (i think the blue primary is fine for this for now).

[nreese]

Created new PR, #202, that merges against feature branch instead of merging into master