Update Discord link in design docs, fix #672 (#710)

This commit is contained in:
Niklas Ek
2020-05-04 12:15:22 +02:00
committed by GitHub
parent 190f11c8f7
commit 8c65917914
+6 -6
View File
@@ -9,11 +9,11 @@ Backstage Open Source is a newly launched endeavor, and were excited to scale
### Collaborative
The Backstage Design Team is small but mighty, and we truly cherish the amazing opportunity we have to work with the Backstage Open Source community! Have an idea? A component request? Feel free to communicate with us via [Discord](https://discord.gg/PefUsZ) (*#design* channel). Collaboration trumps individual speed, and we want to work with you to make Backstage work for all of our users.
The Backstage Design Team is small but mighty, and we truly cherish the amazing opportunity we have to work with the Backstage Open Source community! Have an idea? A component request? Feel free to communicate with us via [Discord](https://discord.gg/EBHEGzX) (*#design* channel). Collaboration trumps individual speed, and we want to work with you to make Backstage work for all of our users.
### Transparent
There are a lot of exciting things coming up and we want to keep you in the loop! Keep an eye on our Milestones in GitHub to see where were headed. Well also be posting updates in the *#design* channel on [Discord](https://discord.gg/PefUsZ). Not only that, we want to keep you informed on the decisions weve made and why weve made them.
There are a lot of exciting things coming up and we want to keep you in the loop! Keep an eye on our Milestones in GitHub to see where were headed. Well also be posting updates in the *#design* channel on [Discord](https://discord.gg/EBHEGzX). Not only that, we want to keep you informed on the decisions weve made and why weve made them.
## 🛠 Our Practice
@@ -48,15 +48,15 @@ This is the universal user experience that is shared amongst all Backstage users
## ⭐️ How to Contribute
### Pick up an issue!
In the beginning, most of our issues will be centered around creating universal components for our Backstage Design System and adding them to our Storybook so plugin developers can reference them. Well also be creating issues that are focused on building up our core Backstage user experience. Well be labeling our issues in GitHub with design and/or storybook - so feel free to browse and tackle the tasks that interest you. If you have any questions regarding an issue, you can ask them in the comments section of the issue or on [Discord](https://discord.gg/PefUsZ). We absolutely adore our external contributors and will send you virtual semlas for your contributions!
In the beginning, most of our issues will be centered around creating universal components for our Backstage Design System and adding them to our Storybook so plugin developers can reference them. Well also be creating issues that are focused on building up our core Backstage user experience. Well be labeling our issues in GitHub with design and/or storybook - so feel free to browse and tackle the tasks that interest you. If you have any questions regarding an issue, you can ask them in the comments section of the issue or on [Discord](https://discord.gg/EBHEGzX). We absolutely adore our external contributors and will send you virtual semlas for your contributions!
### Request a component.
Create an issue (label it design and assign it to katz95) or send us a message on [Discord](https://discord.gg/PefUsZ) (*#design* channel) with details of what the component is and its relevant use cases. Your request will be reviewed by our design team and you should hear back from us within 1-2 business days. Well get back to you and let you know whether your requested component will get picked up by our team as something to be added to our design system.
Create an issue (label it design and assign it to katz95) or send us a message on [Discord](https://discord.gg/EBHEGzX) (*#design* channel) with details of what the component is and its relevant use cases. Your request will be reviewed by our design team and you should hear back from us within 1-2 business days. Well get back to you and let you know whether your requested component will get picked up by our team as something to be added to our design system.
## ✏️ Resources
**[Storybook](http://storybook.backstage.io/)** - where you can view our components. If youd like to help build up our design system, you can also add components weve designed to the Storybook as well.
**[Discord](https://discord.gg/PefUsZ)** - all design questions should be directed to the *#design* channel.
**[Discord](https://discord.gg/EBHEGzX)** - all design questions should be directed to the *#design* channel.
**Documentation**
- Patterns (stay tuned)
@@ -64,7 +64,7 @@ Create an issue (label it design and assign it to katz95) or send us a message o
## 🔮 Future
### Contributions from designers
Are you a designer at an organisation thats implementing Backstage? A designer whos fascinated by the developer productivity problem space? A designer whos curious about open source design? Wed love for you to contribute. Behind the scenes, were setting up a few foundational elements to make sure that contributing to Backstage as a designer is easy. From styling guidelines to UX principles to Figma documents, well make sure youre equipped to chip in on this project. Were excited to work with you! In the meantime, wed love to hear from you on [Discord](https://discord.gg/PefUsZ).
Are you a designer at an organisation thats implementing Backstage? A designer whos fascinated by the developer productivity problem space? A designer whos curious about open source design? Wed love for you to contribute. Behind the scenes, were setting up a few foundational elements to make sure that contributing to Backstage as a designer is easy. From styling guidelines to UX principles to Figma documents, well make sure youre equipped to chip in on this project. Were excited to work with you! In the meantime, wed love to hear from you on [Discord](https://discord.gg/EBHEGzX).
[Back to Docs](../README.md)