|
| 1 | +--- |
| 2 | +title: Generic header |
| 3 | +description: A generic header to help services not on GOV.UK |
| 4 | +section: Components |
| 5 | +aliases: Header (generic) |
| 6 | +backlogIssueId: 185 |
| 7 | +layout: layout-pane.njk |
| 8 | +--- |
| 9 | + |
| 10 | +{% from "_example.njk" import example %} |
| 11 | + |
| 12 | +Use this generic version of the header to tell users they’re using a government service that’s not part of the GOV.UK website. |
| 13 | + |
| 14 | +{{ example({ group: "components", item: "generic-header", example: "default", id: "default-1", html: true, nunjucks: true, open: false, loading: "eager" }) }} |
| 15 | + |
| 16 | +## When to use this component |
| 17 | + |
| 18 | +Use the Generic header component if your service is both: |
| 19 | + |
| 20 | +- a public-facing government service |
| 21 | +- not on the GOV.UK website (meaning that your service is not part of the [GOV.UK proposition](https://www.gov.uk/government/publications/govuk-proposition/govuk-proposition)) |
| 22 | + |
| 23 | +This is to bring consistency and maintain user trust in journeys that move between the GOV.UK website and other government websites and services. |
| 24 | + |
| 25 | +This component also helps ensure your non-GOV.UK service does not: |
| 26 | + |
| 27 | +- identify itself as being part of GOV.UK |
| 28 | +- use the crown or GOV.UK logotype in the header |
| 29 | +- use the GDS Transport typeface |
| 30 | +- use the [GOV.UK brand colours](https://brand.design-system.service.gov.uk/colour/govuk-blue/) |
| 31 | + |
| 32 | +See the guidance on [if your service is not on GOV.UK in the Service manual](https://www.gov.uk/service-manual/design/making-your-service-look-like-govuk). |
| 33 | + |
| 34 | +## When not to use this component |
| 35 | + |
| 36 | +If your service is hosted on one of these gov.uk domains, you must use the [GOV.UK header component](/components/header/) instead: |
| 37 | + |
| 38 | +- gov.uk/[myservice] |
| 39 | +- [myservice].service.gov.uk |
| 40 | +- [myblog].blog.gov.uk |
| 41 | + |
| 42 | +## How it works |
| 43 | + |
| 44 | +If you use the [page template](/styles/page-template/), you’ll first need to replace the default GOV.UK header in the page template with the Generic header component. |
| 45 | + |
| 46 | +Use the Generic header component to display your own: |
| 47 | + |
| 48 | +- brand logo |
| 49 | +- homepage link |
| 50 | +- font for your service name (instead of GDS Transport) |
| 51 | + |
| 52 | +You must also follow the steps in the [Using GOV.UK Frontend without GOV.UK branding guidance](https://frontend.design-system.service.gov.uk/using-govuk-frontend-without-govuk-branding/) to remove other GOV.UK brand elements elsewhere in your service. |
| 53 | + |
| 54 | +### Using your own brand logo |
| 55 | + |
| 56 | +Follow your organisation’s guidelines and best practice to show your brand logo. |
| 57 | + |
| 58 | +To make your logo image as accessible and optimised as possible, also see: |
| 59 | + |
| 60 | +- Design System guidance on [using images](/styles/images/) |
| 61 | +- [Image guidance for GOV.UK content and publishers](https://guidance.publishing.service.gov.uk/formatting-content/images/) |
| 62 | + |
| 63 | +### Homepage link |
| 64 | + |
| 65 | +By default, the Generic header component links to `/`, which is the top level of your service’s domain. You should customise the link to point to wherever makes the most sense for your service. |
| 66 | + |
| 67 | +### Do not show service name or navigation links in the Generic header component |
| 68 | + |
| 69 | +As with the GOV.UK header component, you should not use the Generic header component to show service name or navigation links. Use the [Service navigation component](/components/service-navigation) instead. |
| 70 | + |
| 71 | +## Research on this component |
| 72 | + |
| 73 | +When developing this component, we worked with a cross-government working group representing various government departments that work on services not hosted on GOV.UK. |
| 74 | + |
| 75 | +We thank them for their work to gather the needs and considerations for consistent headers across all government services. |
0 commit comments