Vocabulary
- alias
- A contextualized type of design token that references another (typically global) token.
- author
- A designer or engineer that consumes the design system in order to build products/applications.
- component
- A reusable block of code, tokens, and/or other components that are composed to serve a specific function. A component should not be confused with a pattern.
- component library
- A collection of browseable components accompanied with implementation reference and other relevant technical documentation.
- composite token
- A design token whose value is made up of multiple, named child values.
- design kit
- A comprehensive visual representation of components, styles, and assets structured in a way that allows designers to create, edit, or expand on the existing components without creating them from scratch and consistently and rapidly create and iterate interface mockups.
- design system
- A complete and organized set of guidelines, components, and other relevant resources necessary to inform users how to consistently and efficiently create cohesive digital products.
- design token
- A methodology for expressing design decisions in a platform-agnostic way so that they can be shared across different disciplines, tools, and technologies. They help establish a common vocabulary across organizations.
- engagement
- The processes that control decision-making, contribution, enhancements, and workflows for the design system. This is also often referred to as governance.
- global token
- A highly-abstracted type of design token that represents one of a series of options available for use in building and extending the system.
- guidelines
- Suggestions and best practices to follow for how to best use the various facets of the design system.
- library
- A published design file that contains reusable design elements such as variables, styles, icons, and components.
- pattern
- Reusable best-practice solutions for how a user achieves a goal or solves a design problem. A pattern should not be confused with a component.
- style hook
- A component-specific way to represent and customize design decision. This was previously referred to as a component token.
- toolkit
- The collection of resources and technologies necessary to effectively build products that seamlessly integrate with other Jack Henry products.
- user
- The end user that is interacting with design system components that have been integrated into the product.
- variable
- Reusable values that can be applied to design properties and prototyping actions. Figma uses the name “variable” to represent the concept of design tokens. We often use variable and token interchangeably. However, variables are platform-specific. As such, they have opinions and constraints associated with them that don’t necessarily apply to the tokens they derive from. It’s important to note that a token can be represented as either a variable or style within Figma.
- visual language
- A unified and specific set of guidelines that thoughtfully and intelligibly describes how the design system should look and feel.