-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
e394d54
commit e092652
Showing
1 changed file
with
47 additions
and
73 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,76 +1,50 @@ | ||
<style> | ||
.spacing { | ||
margin-top: 36px; | ||
} | ||
</style> | ||
|
||
|
||
<div class="spacing"> | ||
<p>Principles are the foundation of the system. They form the basis of a good product and help the team with decision making. They are here to guide you and your team when working with the myriad parts of the system and help you do better and make more informed decisions.</p> | ||
</div> | ||
|
||
|
||
<div class="spacing"> | ||
<h3>###1. We start with user needs.</h3> | ||
<hr> | ||
<p>Do research, analyze data, talk to users. Don't make assumptions. Be human. Define the problem first.</p> | ||
</div> | ||
|
||
<div class="spacing"> | ||
<h3>###2. We add more value by presenting fewer choices.</h3> | ||
<hr> | ||
<p>Less is more. We seek to reduce clutter and cognitive load. Every piece of functionality we add to the system should add value for our users.</p> | ||
</div> | ||
|
||
<div class="spacing"> | ||
<h3>###3. We are consistent.</h3> | ||
<hr> | ||
<p>We are consistent with our designs, the language we use on interfaces, our code, and our data.</p> | ||
</div> | ||
|
||
<div class="spacing"> | ||
<h3>###4. We design with data.</h3> | ||
<hr> | ||
<p>We embrace data-driven decision making. We measure and evaluate against the original goals.</p> | ||
</div> | ||
|
||
<div class="spacing"> | ||
<h3>###5. We use our user's language.</h3> | ||
<hr> | ||
<p>Words can both clarify and confuse. We seek to use language that is familiar to our users and avoid using jargon.</p> | ||
</div> | ||
|
||
<div class="spacing"> | ||
<h3>###6. We make it accessible, responsive, and inclusive.</h3> | ||
<hr> | ||
<p>Everything we build is WCAG 2.0 AA compliant. We sacrifice elegance to inclusiveness, readability, and legibility.</p> | ||
</div> | ||
|
||
<div class="spacing"> | ||
<h3>###7. We provide context.</h3> | ||
<hr> | ||
<p>By communicating how everything interrelates, people are much more likely to understand the importance of what they are looking at.</p> | ||
<p>The design should keep people aware of where they are within the overall experience at all times in a consistent and clear fashion.</p> | ||
</div> | ||
|
||
<div class="spacing"> | ||
<h3>###8. We collaborate.</h3> | ||
<hr> | ||
<p>We tackle problems together. We listen, we understand, we critique, and we encourage rather than force solutions. We learn from each other and understand the value of what we're building.</p> | ||
</div> | ||
|
||
<div class="spacing"> | ||
<h3>###9. We make it shareable and reusable.</h3> | ||
<hr> | ||
<p>If we have found a way of doing something that works, we share it whenever we can instead of reinventing the wheel every time.</p> | ||
</div> | ||
|
||
<div class="spacing"> | ||
<h3>###10. We test and iterate.</h3> | ||
<hr> | ||
<p>We are aware that our solutions are assumptions unless tested with real users.</p> | ||
<p>We test hypotheses, learn, and improve our ideas.</p> | ||
</div> | ||
|
||
Principles are the foundation of the system. They form the basis of a good product and help the team with decision making. They are here to guide you and your team when working with the myriad parts of the system and help you do better and more informed decisions. | ||
|
||
## 1. We start with user needs. | ||
|
||
Do research, analyze data, talk to users. Don't make assumptions. Be human. Define the problem first. | ||
|
||
## 2. We add more value by presenting fewer choices. | ||
|
||
Less is more. We seek to reduce clutter and cognitive load. Every piece of functionality we add to the system should add value for our users. | ||
|
||
## 3. We are consistent. | ||
|
||
We are consistent with our designs, the language we use on interfaces, our code, and our data. | ||
|
||
## 4. We design with data. | ||
|
||
We embrace data-driven decision making. We measure and evaluate against the original goals. | ||
|
||
## 5. We use our user's language. | ||
|
||
Words can both clarify and confuse. We seek to use language that is familiar to our users and avoid using jargon. | ||
|
||
## 6. We make it accessible, responsive, and inclusive. | ||
|
||
Everything we build is WCAG 2.0 AA compliant. We sacrifice elegance to inclusiveness, readability, and legibility. | ||
|
||
## 7. We provide context. | ||
|
||
By communicating how everything interrelates, people are much more likely to understand the importance of what | ||
they are looking at. The design should keep people aware of where they are within the overall experience at all times in a consistent and clear fashion. | ||
|
||
## 8. We collaborate. | ||
|
||
We tackle problems together. We listen, we understand, we critique, and we encourage rather than force | ||
solutions. We learn from each other and understand the value of what we're building. | ||
|
||
## 9. We make it shareable and reusable. | ||
|
||
If we have found a way of doing something that works, we share it whenever we can instead of reinventing the | ||
wheel every time. | ||
|
||
## 10. We test and iterate. | ||
|
||
We are aware that our solutions are assumptions unless tested with real users. | ||
We test hypotheses, learn, and improve our ideas. | ||
|
||
--- | ||
|
||
Special thanks to [Design Manifesto](https://www.designmanifesto.org/) for inspiration. |