New metadata component markup and Sass
Add basic test to ensure docs are returned

This test ensures that docs are returned when you try and request them.
As the docs controller tries to parse the JSON it also validates that
the format is correct and will fail if bad JSON is in the docs file.
Merge pull request #443 from alphagov/metadta-component

New metadata component markup and Sass
Add instructions for running static locally

In particular how to have static point at it's own assets, not default to
static.dev.gov.uk, which won't exist unless you're running our whole VM stack.

This makes it easier for:
 - new devs seeing how static works
 - external contributors
 - developers of apps that depend on static (eg, may use slimmer)
Add clearing to report a problem wrapper

Without this it's breaking sticky navigation elsewhere in whitehall.
Add documentation on GOV.UK Components

Static is the authorative source for components, including documentation, so should be included here.
- As this grows it might want to be split into a README in a components specific directory, tho a good one doesn't exist yet
- It might be worth creating a generator to do the creation, just docing for now
Add a rails generator for GOV.UK components

Generates all the file scaffolding, in the right places, as
the files are a bit spread throughout static at the moment.

This will include all the files required to let the component
be demo'd on govuk-component

Appending to the json docs file is a bit shonky, but we're
not planning on using that as a docs method long term. It'll
likely be inline with template, or at least one doc file per
component, which will make this simpler.
Make the GOV.UK component doc fixture structure clearer

Fixtures are a hash of hashes, the parent hash is fixture_name => fixture

The fixture is a hash of locals to be passed to the compontent view.
Update readme to include component generator
Fix typos and confusing wording in README