You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+6-5
Original file line number
Diff line number
Diff line change
@@ -104,17 +104,18 @@ If an unreviewed ticket reports a bug, try and reproduce it. If you can reproduc
104
104
105
105
Our documentation is great but it can always be improved. Did you find a typo? Do you think that something should be clarified? Go ahead and suggest a documentation patch!
106
106
107
-
We use [Docz](https://www.docz.site) to run our documentation site at [wave.free-now.com](https://wave.free-now.com/).
107
+
We use [Storybook](https://storybook.js.org) to run our documentation site at [wave.free-now.com](https://wave.free-now.com/).
108
108
109
109
To add a new component to our documentation site:
110
110
111
-
1. Create a new file with the `.md` extension for your component in `/components/[component]/docs`.
112
-
2. Add the markdown header for the page name, route and parent menu
113
-
3. Include a brief description, examples as well as the the `Playground` and `Props` components of [Docz].
111
+
1. Create a new file with the `.stories.tsx` prefix for your component in `/src/stories`.
112
+
2. Include a brief description and examples. Props should be configurable via Storybook
113
+
114
+
To learn more how to add stories go to [Storybook docs](https://storybook.js.org/docs/react/writing-stories/introduction)
114
115
115
116
### Reporting pains and use cases
116
117
117
-
Speak outloud for us to understand your pains is valuable, challenge current approaches and help us to understand how to do better. Make sure to verify that the topic hasn't being touched yet on the issues poll otherwise open a new one and let's start the conversation
118
+
Speak out loud for us to understand your pains is valuable, challenge current approaches and help us to understand how to do better. Make sure to verify that the topic hasn't being touched yet on the issues poll otherwise open a new one and let's start the conversation
Accessible design not only helps users with disabilities; it provides better user experiences for everyone.
8
+
9
+
## Overview
10
+
11
+
Our goal is to provide a consistent user experience for all users, whether they’re navigating with a mouse/touchscreen, keyboard, or screen reader.
12
+
13
+
An accessible product should:
14
+
15
+
- Give all users the same quality of experience
16
+
- Adapt to users and situations
17
+
18
+
Individually accessible elements and components are part of building accessible products, but the accessibility efforts need for manual testing. When designing new UIs, rely as much as possible on Wave existing components and follow accessible patterns. If you're creating a new component or pattern (one that doesn't exist in Wave), keep in mind accessibility practices before your implementation.
19
+
20
+
## Mission
21
+
22
+
The Wave Design System team wants as many people as possible to be able to use Wave powered products. For example, that means you should be able to:
23
+
24
+
-**zoom** in up to 300% without the text spilling off the screen
25
+
- navigate most of the website using just a **keyboard**
26
+
- listen to most of the website using a **screen reader**
27
+
28
+
## Aid development process
29
+
30
+
- How to [audit Web a11y Video](https://www.youtube.com/watch?v=cOmehxAU_4s)
31
+
- Use the [a11y project checklist](https://www.a11yproject.com/checklist/) and aim for at least A level compliance
32
+
- Use [axe dev tools](https://chrome.google.com/webstore/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd) for accessibility testing. Check more at [deque Axe](https://www.deque.com/axe/devtools/) and learn [how to use it with this Video](https://www.youtube.com/watch?v=dyU9yrRJ5Eg)
33
+
- Use [Lighthouse Chrome extension](https://chrome.google.com/webstore/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk?hl=en) for accessibility score. Check more at [Web.dev a11y](https://web.dev/accessibility-scoring/)
34
+
- Use [accessible queries](https://testing-library.com/docs/queries/about#priority) when writing tests. This assume you are using [testing-library](https://testing-library.com/)
Copy file name to clipboardExpand all lines: docs/contributing.storybook.mdx
+12-13
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
-
---
2
-
name: Contributing
3
-
route: /contributing
4
-
cardHeadline: Contributing
5
-
cardSubHeadline: Everyone is welcome to make contributions to the design system. To make sure that everyone can contribute, we have decided to write out a few steps that help you add your contributions.
Everyone is welcome to make contributions to the design system. To make sure that everyone can contribute, we have decided to write out a few steps that help you add your contributions.
10
+
11
11
## Reporting Bugs
12
12
13
13
The design system is used in many places. We have a hard time keeping our eyes on all of them to keep up with the issues
@@ -27,13 +27,13 @@ should be added to the design system.
27
27
This is the submission process for new components, essentials and improvements to existing components:
28
28
29
29
1.[Create a Github issue](https://github.com/freenowtech/wave/issues/new) with the basic information and gather
30
-
feedback from the maintainers and your fellow developers
30
+
feedback from the maintainers and your fellow developers
31
31
2. Align with the maintainers and other developers on the API of the component
32
32
3. After the development is done, open a pull request, keeping the
33
-
[development guidelines](../CONTRIBUTING.md) in mind. You will get feedback here, but we recommend check-ins with
34
-
designers and developers during the development
33
+
[development guidelines](../CONTRIBUTING.md) in mind. You will get feedback here, but we recommend check-ins with
34
+
designers and developers during the development
35
35
4. With the required approvals, you can merge your branch to main and it will be released by the maintainers in the
36
-
next version of `@freenow/wave`
36
+
next version of `@freenow/wave`
37
37
38
38
If you need any help during the process, don't hesitate to reach out to one of the maintainers.
39
39
@@ -51,7 +51,6 @@ Descriptions, FAQs and explanations are all valuable for us! Documentation PRs a
51
51
52
52
All the documentation pages are Markdown-based. You don't need to know how to write code to contribute.
53
53
54
-
55
54
## Other Contributions
56
55
57
56
Not all contributions have to be made in design, code and pull requests. You can for example help your team adopt the
0 commit comments