Open
Conversation
Dependency Compatibility Matrix
|
bryophyta
reviewed
Mar 11, 2026
bryophyta
reviewed
Mar 11, 2026
|
Nice! This is looking great so far 👍 I've added a couple of initial thoughts inline |
Co-Authored-By: Andrew Howe-Ely <114918544+andrewHEguardian@users.noreply.github.com>
62f3fcd to
415e5b4
Compare
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
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.
What does this change?
Adds a Vision doc for Stand. The contents of this document were collaborated on by a wider group in a session, and synthesised in this PR.
Here follows the doc:
Challenges:
Vision:
The goal of Stand is to provide a single design system that creates consistency within Guardian tools, ensuring clarity and reducing friction while being inclusive by design, so that everyone can use and contribute to our tools.
Clarity
End users should immediately understand the purpose, state and consequence of Stand components.
Each component defines when designers and engineers should use it. Its behaviour, interactions, logic and design decisions are explicit and documented.
KPIs:
Consistency
Stand components should work universally across tools. Components should increase efficiency by reducing friction in user interactions and improving delivery speed for engineers and designers.
Stand should provide clear defaults to reduce repeated design decisions and avoid one-off customisations that increase maintenance costs. Their design should feel familiar but distinct across tools. Components should be modular and composable.
There should be a source of truth that is easy to find. This should mitigate issues from divergence between design and code.
KPIs:
Inclusive by design
Accessibility in Stand is not optional. Designs should meet our accessibility standards. All colleagues should be able to work effectively in tools, regardless of role, ability or context.
Components should be well documented so designers and engineers can adopt them quickly. There should be contribution guidelines for extending the system.
KPIs: