-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
21 changed files
with
27,230 additions
and
3,248 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
<script type="text/javascript"> | ||
document.addEventListener( | ||
'DOMContentLoaded', | ||
function () { | ||
document.body.classList.add('js-enabled'); | ||
}, | ||
false, | ||
); | ||
</script> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,90 @@ | ||
# Upgrading to 4.0 | ||
|
||
There are some breaking changes you'll need to be aware of when upgrading to v4. These are mostly related to us upgrading our dependency on [nhsuk-frontend to v8](https://github.com/nhsuk/nhsuk-frontend/blob/main/CHANGELOG.md#810---11-january-2024) which also includes breaking changes. | ||
There are some breaking changes you'll need to be aware of when upgrading to v4. These are mostly related to us upgrading our dependency on [nhsuk-frontend to v8](https://github.com/nhsuk/nhsuk-frontend/blob/main/CHANGELOG.md#810---11-january-2024) which also includes breaking changes. | ||
|
||
## Major changes | ||
## Breaking changes | ||
|
||
### ADD_HEADING_HERE | ||
### Breadcrumbs | ||
|
||
TODO | ||
The breadcrumbs component has been brought in line with nhsuk-frontend. As part of this, the mobile-only 'back link' which is displayed will now have a hidden 'Back to' prefix added to it. Please ensure you remove any custom accessibility around this. | ||
|
||
### ADD_HEADING_HERE_2 | ||
I.e., this: | ||
|
||
TODO | ||
``` | ||
<Breadcrumb.Back href="/level-one/level-two/level-three">Back to Level three</Breadcrumb.Back> | ||
``` | ||
|
||
Should now become this: | ||
|
||
``` | ||
<Breadcrumb.Back href="/level-one/level-two/level-three">Level three</Breadcrumb.Back> | ||
``` | ||
|
||
### Header | ||
|
||
The header implementation has been simplified and a reduced set of components are on offer for this version. | ||
The `Header.NavContainer`, `Header.NavItemList`, and `Header.NavTitle` components have been removed. Instead, the `Header.Nav` component includes the container for rendering items. The nav title has been removed, and customisation of the dropdown manu link text can be done via the `dropdownText` prop on the new `Header.NavDropdownMenu` component. | ||
The `Header.MenuToggle` and `Header.NavMenuClose` components have been removed. Instead, these should be replaced with a usage of `Header.NavDropdownMenu` added as the last child of `Header.NavMenu`. | ||
|
||
For example, this: | ||
|
||
``` | ||
<Header> | ||
<Header.Container> | ||
<Header.Logo href="/" /> | ||
<Header.Content> | ||
<Header.MenuToggle /> | ||
<Header.Search /> | ||
</Header.Content> | ||
</Header.Container> | ||
<Header.NavContainer> | ||
<Header.NavTitle> | ||
<span>Menu</span> | ||
<Header.NavMenuClose /> | ||
</Header.NavTitle> | ||
<Header.NavItemList> | ||
<Header.NavItem href="/" mobileOnly> | ||
Home | ||
</Header.NavItem> | ||
<Header.NavItem href="/conditions">Health A-Z</Header.NavItem> | ||
<Header.NavItem href="/live-well">Live Well</Header.NavItem> | ||
</Header.NavItemList> | ||
</Header.NavContainer> | ||
</Header> | ||
``` | ||
|
||
Should become this: | ||
|
||
``` | ||
<Header> | ||
<Header.Container> | ||
<Header.Logo href="/" /> | ||
<Header.Content> | ||
<Header.Search /> | ||
</Header.Content> | ||
</Header.Container> | ||
<Header.Nav> | ||
<Header.NavItem href="/" mobileOnly> | ||
Home | ||
</Header.NavItem> | ||
<Header.NavItem href="/conditions">Health A-Z</Header.NavItem> | ||
<Header.NavItem href="/live-well">Live Well</Header.NavItem> | ||
<Header.NavDropdownMenu dropdownText="Menu" /> | ||
</Header.NavContainer> | ||
</Header> | ||
``` | ||
|
||
### Adding a `js-enabled` class | ||
|
||
It is now required that a `js-enabled` class is added to a parent element if JavaScript is enabled (we suggest using `body`). E.g. `<body class="js-enabled">`. | ||
This is to facilitate a differentiation in styling to the header depending on whether JavaScript is enabled or disabled. | ||
|
||
## New features | ||
|
||
### Text input prefixes + suffixes | ||
|
||
You can now specify prefixes and/or suffixes for your text inputs. These are exposed as new props on the `TextInput` component, e.g. | ||
|
||
``` | ||
<TextInput prefix="£" suffix="pounds" /> | ||
``` |
Oops, something went wrong.