Design Pattern Library: Document Tags
Tags make it possible to show non-quantitative object metadata that are mostly either a system result or used by the system itself.
We show a tag as a simple small badge-like object that can be included anywhere in the UI.
Use this when objects need to show non-quantitative object metadata that are mostly either a system result or used by the system itself.
Usage should make sense in terms of context. This means that placement can, for example, be near an ID of an object in order to strengthen the connection that this tag belongs to that object.
Dos and dont's
Don't use this pattern to represent status, quantitative object metadata, or non-quantitative object metadata only meant to be used by humans.
Links / references
Make sure these are completed before closing the issue, with a link to the relevant commit, if applicable.
- Ensure that you have broken things down into atoms, molecules, and organisms.
- Check that you have not created a duplicate of an existing pattern.
- Ensure that you have used the proper method for creating the pattern depending on the complexity. Atoms and molecules are symbols, organisms are groups.
- Make sure that typography is using text styles. When applicable used shared styles for colors.
- QA check by another UXer
- Add changes to the pattern library
Add a merge request that includes any new or updated guidelines to the Design System
Add an agenda item to the next UX weekly call to inform everyone (if new pattern, not yet used in the application)