feat: add JS level system for component preview notices#393
Merged
Conversation
Introduces jsLevel (1/2/3) on fixtures to classify JavaScript dependency: - Level 1: hard JS requirement, shows a GOV.UK notification banner only - Level 2: progressively enhanced, shows a notice + static preview - Level 3: no meaningful JS dependency beyond GOV.UK Frontend, static preview only Adds buildJsNotice helper, wires notices into generateComponentMd, and documents the jsLevel/jsNotice/previewSuffix fixture properties.
davidjamesstone
approved these changes
May 13, 2026
davidjamesstone
approved these changes
May 13, 2026
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed change
Introduces the the concept of a "javascript level" on fixtures to classify the component's dependency on client-side Javascript.
This PR visually documents the different levels in the plugin documentation for each component.
Examples
Level 1 (no viable non-JS route)
Level 2 (progressive enhancement)
Level 3 (standard components)
Type of change
Checklist
README.mdanddocs/*(where appropriate, e.g. new features).npm run test).npm run lint).npm run format).