Revel
GitHub
GitHub
  • Overview

    • Getting started
    • FAQ
    • Release notes
  • Foundations

    • Meet the standard
    • Accessibility
    • Internationalization
    • Information hierarchy
    • Speed
  • Design

    • Visual principles
    • Colors
    • Space
    • Icons
    • Typography
  • Design tokens
  • Style helpers
  • Content

    • Express your ideas
    • Actionable language
    • Inclusive and accessible language
    • Alternative text
    • Grammar and mechanics
      • Basics
      • Capitalization
      • Dates and units of measurement
      • Punctuation
  • Components

    • Alert
    • Avatar
    • Badge
    • Button
    • Button group
    • Checkbox
    • Date Input
      • dates
      • datetimes
      • ranges
    • Field group
    • File upload
    • Flex
    • Grid
    • Icon
    • Image
    • Input
    • Loader
    • Modal
    • Month picker
    • Pagination
    • Popper
    • Radio
    • Repeater
    • Select
    • Tabs
    • Tile
    • Toast
    • Toggle
  • Directives

    • Click outside
    • Tooltip

Speed

Standardizing components & patterns that saves time during production.

Standardizing components and patterns helps designers and developers to understand the process of creating a product, and let's them focus their efforts on other aspects of the product. This means that they don't have to spend time building the same components each time they create a new product, which saves a great deal of time. Additionally, having standardized components and patterns ensures that the product is consistent and of high quality, since the same processes are applied each time. This is beneficial both to the production team and to the customers, as they can be assured of a reliable product.

The following principles outline the key steps to be taken in order to ensure that components and patterns are standardized in an efficient and effective manner:

  • Establish a consistent design language throughout the product. This will ensure that the product is cohesive and recognizable.
  • Leverage existing components and patterns where possible this will save time and reduce the amount of custom code that needs to be written.
  • Ensure the components and patterns are flexible and easy to customize. This will ensure that the product can be easily adapted to different needs and requirements and will make it easier to maintain and update.
  • Document all components and patterns for easy reference. This will save time and reduce the need for extra training and development.
  • Optimize components and patterns for performance. This includes optimizing the code, making sure that the components and patterns are lightweight, and using caching where appropriate. This will ensure that the product runs smoothly and efficiently, and is not slowed down by inefficient components and patterns.
Edit this page
Last Updated: 7/6/23, 6:53 AM
Contributors: noon-dawg, Cesar Level, John Hannagan, Weetbix
Prev
Information hierarchy