arielsdesign / design-systems

A project to document and share high quality, hand picked resources related to designing, building and maintaining modern design systems.

Design Systems

http://designsystems.info aims to document and share high quality, hand picked resources related to designing, building and maintaining modern design systems. The project is currently in planning phase (6/2017).

Want to help? Get in touch with @viljamis.

To do (Work-in-progress)

• Write introduction content
• Collect and organize resources
• Create information architecture
• Publish as a website
• Make it easy to contribute

Topics (Work-in-progress)

• Introduction
  • What is http://designsystems.info
  • Why is it needed
  • Who is it for
  • How to contribute
• Why a Design System
  • Better consistency
  • Centralized assets
  • More efficient processes
  • Establishes shared vocabulary
  • Provides documentation
  • Makes testing easier
  • Increased collaboration and knowledge sharing
  • Less time and money wasted
• What is a Design System
  • A blueprint for product development
  • Building blocks
    • Typography
    • Color
    • Grid
    • Icons
    • Images
  • UI Patterns
    • Templates
    • Modules
    • Components
    • Elements
  • Rules
    • Design Principles
    • Implementation guidelines
    • Do’s and Don’ts
    • Naming of Things
    • Voice and tone
    • Editorial guidelines
• Selling design systems
  • Pitching to managers and leaders
  • Getting buy-in from design and front-end teams
• Building the design system
  • Changing the way we build
  • Team activities to start a design system
    • Component cut-up workshop
    • Component checklist workshop
  • Creating interface inventory
    • Audit of interface and code
    • Screenshotting different UI patterns
    • Categorizing patterns by their purpose
    • Marking inconsistencies between patterns
  • Defining design principles
  • Unifying the design
  • Creating component library
    • Synchronized or separated system
    • Public or private
  • Planning for maintenance
• Maintenance strategy
  • Design system ops
  • Deprecating components
  • Adding new components
  • Component QA Process
  • Source of truth
  • Documentation
  • Changelog
  • Deployment
• Tools
• Live Examples

Who’s Behind This

• @viljamis

License

The MIT License (MIT)

Copyright (c) 2017 Viljami S. Design

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.