Create a component guide based on components in an application #1
Not all components should be in static. If they are used only in one application it is preferable to keep them close to the point of use.
See README.md for further details.
Still to do but can be separate PRs:
Use models, logic and styles from https://github.com/alphagov/govuk-component-guide. Docs structure will be identical. * Render a list of components based on docs in the `app/views/components/docs` directory of the host app * Display a component with a set of test fixtures based on those docs * Include those partials in the view path * Use breadcrumbs component for navigating the guide * Use a less verbose component call for using a partial
Default both to rails convention, “application”