-
Notifications
You must be signed in to change notification settings - Fork 170
/
contribute.html
16 lines (12 loc) · 1.08 KB
/
contribute.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
---
layout: page
title: Contributing to the design system
description: This page explains the process (or processes) by which the design system gets updated
---
## People
Describe who's involved in changes to the system. Describe who's expected to do the work and who approves changes.
## Process
Describe specifically the process or processes by which the system gets [updated](http://atomicdesign.bradfrost.com/chapter-5/#making-changes-to-patterns). What happens when existing component need modified? What if an entire new component needs created? What happens if a component is deprecated? See [Canonical's fantastic decision tree](http://design.canonical.com/2016/07/getting-vanilla-ready-for-v1-the-roadmap/) for contributing changes to their design system.
Since a design system is made up of component code, guidelines, documentation, design tools, and resources, keep in mind you'll likely need to define several processes to contribute each of these ingredients.
## Support
Cross-linking to the <a href="{{ "/support.html" | prepend: site.baseurl }}">support page</a> is a good idea here.