Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/tournantdev/ui
πββοΈ Inclusive Vue Components
https://github.com/tournantdev/ui
accessibility inclusive-components ui-components vue
Last synced: about 1 month ago
JSON representation
πββοΈ Inclusive Vue Components
- Host: GitHub
- URL: https://github.com/tournantdev/ui
- Owner: tournantdev
- Created: 2019-07-05T21:17:25.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2024-10-18T07:23:31.000Z (2 months ago)
- Last Synced: 2024-10-29T19:57:32.273Z (about 2 months ago)
- Topics: accessibility, inclusive-components, ui-components, vue
- Language: JavaScript
- Homepage: https://ui.tournant.dev
- Size: 1.42 MB
- Stars: 26
- Watchers: 3
- Forks: 1
- Open Issues: 59
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
- awesome-a11y-vue - Tournant UI - Inclusive Vue Components (Accessible projects / Vuepress)
- awesome-access - Tournant UI - Inclusive Vue Components (Accessible projects / Vuepress)
README
# Tournant UI
In the kitchen, the _tournant_ is the person moving around, helping out.
Tournant UI aims to be this. For User Interfaces. Tournant UI will not replace your complete UI or dictate how to you design your elements.
But if you need to integrate inclusive components in your site, Tournant UI will be there. Like a helping hand.
## Note
This is still in early development. Many components needed are missing. If you are able to contribute, please do!
## Components
This project aims to provide common user interface patterns. It revolves around the [WAI-ARIA design patterns and examples](https://www.w3.org/TR/wai-aria-practices-1.1/#aria_ex) list. But it is not limited to it.
You can track our progress and development plans in the [Component Development project](https://github.com/tournantdev/ui/projects/2). Again, if you are able to contribute one of the components, please do so. If you need one of the components but donβt feel like you can build it on your own, open a [feature request issue](https://github.com/tournantdev/ui/issues/new?assignees=&labels=enhancement&template=feature_request.md&title=).
## Acknowledgment
Tournant is heavily inspired by projects such as Reach UI, Inclusive Components and Accessible App.
## Feedback & Contributions
Contributions are always welcome.
We have written down detailed [contribution guidelines](CONTRIBUTING.md).
Please be aware that all contributions have to follow our [Code of Conduct](CODE_OF_CONDUCT.md). Contributions of any kind which to not adhere to it will be removed. No exceptions will be made.
Thanks. π
## Development
If you want to improve the component, follow these steps.
Tournant UI uses [Lerna](https://lerna.js.org/). You will need to bootstrap the project folder:
```
yarn bootstrap
```This will install all packages and hoist them to the project root folder.
### Create a Component
We maintain a CLI helper tool named [Communard](https://github.com/tournantdev/communard) to quickly scaffold the folder structure needed to develop a new component. It is integrated into the project. You can start it by running `yarn run create`.
To develop your components please use Storybook [as explained in the contribution documentation](CONTRIBUTING.md#storybook).
### Build packages
To build all packages run:
```
yarn build
```### Run your tests
```
yarn run test
```### Lints and fixes files
```
yarn run lint
```### Publish Packages
π _Note:_ You need to have access to the npm @tournant organisation to run this command.
Before you are able to use the integrated Lerna publishing flow the package needs to be on NPM already. We recommend [np](https://github.com/sindresorhus/np) for doing so.
To publish everything run:
```
yarn publish:packages
```## Authorship
Tournant UI is maintained by Marcus and Oscar. But, in reality, this project wouldnβt be possible without the amazing community that has evolved around inclusive web development. Thanks, yβall.
Special thanks to Ryan Florence and the [Reach UI](https://github.com/reach/reach-ui) project, from which we blatantly copied lots of the architecutural decisions and the idea itself.
Marcus Herrmann | [@marcus-herrmann](https://github.com/marcus-herrmann) | [www.marcus.io](www.marcus.io)
Oscar Braunert | [@ovlb](https://github.com/ovlb) | [www.ovl.design](www.ovl.design)