Acceptance criteria
These criteria allow you to recognize the possible new components and help you to feel comfortable collaborating with the Design System team.
- Does the new component solve a problem that can’t be solved with the existing one?
- Does it meet user and business needs across multiple areas?
- Does it match customers’ needs?
- Does it meet the accessibility standards?
If a component candidate meets these criteria, you can be confident that you’re at least on the right track. For the next step, ideally, meet one of our design system designers to validate your request before you jump to the flow for component creation.
1. Does the new component solve a problem that can’t be solved with the existing one?
In many cases, existing components or patterns can easily solve the problem, which can be better than introducing something new, even for users. It is generally recommended that the design be validated with the design system team first, and only if the existing solutions don't fit, continue to prepare new components.
2. Does it meet user and business needs across multiple areas?
The core of the design system is to bring components and patterns that can be used in multiple areas and create a consistent solution for the same or similar problems.
3. Does it match customers’ needs?
The design should center users and customers in most areas, and component creation is no exception. New components should be designed to solve our customers' problems and needs, ideally in multiple areas.
4. Does it meet the accessibility standards?
The soul design system is built to match accessibility standards in all areas, and the components are crucial to this principle. When validating a new component, keep this in mind, be ready to define specific areas of this discipline, and respect the accessibility rules.