└── README.md /README.md: -------------------------------------------------------------------------------- 1 | # Design Systems 2 | 3 | [http://designsystems.info](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).* 4 | 5 | **Want to help? Get in touch with [@viljamis](https://twitter.com/viljamis).** 6 | 7 | ## To do *(Work-in-progress)* 8 | 9 | - Write introduction content 10 | - Collect and organize resources 11 | - Create information architecture 12 | - Publish as a website 13 | - Make it easy to contribute 14 | 15 | ## Topics *(Work-in-progress)* 16 | 17 | - Introduction 18 | - What is [http://designsystems.info](http://designsystems.info) 19 | - Why is it needed 20 | - Who is it for 21 | - How to contribute 22 | - Why a Design System 23 | - Better consistency 24 | - Centralized assets 25 | - More efficient processes 26 | - Establishes shared vocabulary 27 | - Provides documentation 28 | - Makes testing easier 29 | - Increased collaboration and knowledge sharing 30 | - Less time and money wasted 31 | - What is a Design System 32 | - A blueprint for product development 33 | - Building blocks 34 | - Typography 35 | - Color 36 | - Grid 37 | - Icons 38 | - Images 39 | - UI Patterns 40 | - Templates 41 | - Modules 42 | - Components 43 | - Elements 44 | - Rules 45 | - Design Principles 46 | - Implementation guidelines 47 | - Do’s and Don’ts 48 | - Naming of Things 49 | - Voice and tone 50 | - Editorial guidelines 51 | - Selling design systems 52 | - Pitching to managers and leaders 53 | - Getting buy-in from design and front-end teams 54 | - Building the design system 55 | - Changing the way we build 56 | - Team activities to start a design system 57 | - Component cut-up workshop 58 | - Component checklist workshop 59 | - Creating interface inventory 60 | - Audit of interface and code 61 | - Screenshotting different UI patterns 62 | - Categorizing patterns by their purpose 63 | - Marking inconsistencies between patterns 64 | - Defining design principles 65 | - Unifying the design 66 | - Creating component library 67 | - Synchronized or separated system 68 | - Public or private 69 | - Planning for maintenance 70 | - Maintenance strategy 71 | - Design system ops 72 | - Deprecating components 73 | - Adding new components 74 | - Component QA Process 75 | - Source of truth 76 | - Documentation 77 | - Changelog 78 | - Deployment 79 | - Tools 80 | - Live Examples 81 | 82 | ## Who’s Behind This 83 | 84 | * [@viljamis](https://viljamisdesign.com) 85 | 86 | ## License 87 | 88 | The MIT License (MIT) 89 | 90 | Copyright (c) 2017 [Viljami S. Design](https://viljamisdesign.com) 91 | 92 | 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: 93 | 94 | The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. 95 | 96 | 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. 97 | --------------------------------------------------------------------------------