Increase the likelihood that service teams will only include the bits of the Design System they are using about govuk-design-system HOT 4 CLOSED

I'll leave defining the tasks we want to do until this epic is picked up, but a few thoughts on things we could do:

• #3732 – this would help us learn where the pain points are
• move as many responsibilities from initAll to the components (for example, the data-module selector is only defined in initAll) to make it easier to include the JS for components without initAll
• make it possible to generate a custom version of the 'dist' JS + CSS, like you could with Bootstrap in ye olde days
• improve our documentation to nudge people towards optimising what they include
• create a calculator that asks people to select the components they're actually using, and then show them how much they could shave off their file size – it could also
  • ask for approx number of sessions and calculate the impact on carbon footprint
  • allow the data to be submitted and feed into a dashboard with the estimated collective impact the changes have had
• blog about it
• show and tell about it
• run a clinic or workshop focused around it

from govuk-design-system.

Another suggestion that came up in a recent conversation with @romaricpascal – allowing users to specify which components (or other parts of the code?) they want to include the Sass for using a Sass variable:

$govuk-included-components: (
    "button",
    "header",
    "footer"
);

@import "govuk/all";

from govuk-design-system.

If we're revisiting our guidance on importing things, we might want to take this opportunity to split up or re-organise the 'Import CSS, assets and JavaScript' page which is becoming a bit unwieldy.

from govuk-design-system.

Calling this done.

from govuk-design-system.