Static components currently live in a different directory to app components. (“govuk_component” vs “components”) While this discrepancy exists the gem needs to know whether it’s documenting static components or app components.
Some oddities were also found concerning the way dependencies are required when Slimmer is or isn't there:
(Gem changes tested against government-frontend and static)
Goes with alphagov/static#1125
Static behaves strangely when autoloading govuk_frontend_toolkit and importing the component_guide. Somehow the component guide sass file was loaded outside of the scope of the toolkit, so did not have access to things like $gutter and core-19. By moving into a single file we avoid this problem. Although the initial cause is still unclear.
Allow components to be generated in static, taking account of subtle inconsistencies that currently exist. In static components: * use the govuk_component directory * don’t begin with an underscore * include `.raw` in their filename * use underscores in doc and partial filenames * use hyphens in styles * store styles in govuk-component rather than govuk_component * use the `pub-c-` prefix