Skip to main content

​
Improving the docs

Documentation is extremely important and takes a fair deal of time and effort to write and keep updated. Everything is written in Markdown to facilitate the process of contributing.

​
Docs Setup Guide

  1. Clone the repository:
  1. Install all dependencies:
  1. Navigate to the apps/docs folder:
  1. Run the development server:
  1. Make your changes under the apps/docs folder and see a live preview at localhost:3000.
  2. Submit a pull request.

​
Building new components

We’re open to expanding the catalog of components to cover as many use cases as possible. We suggest to open an issue for discussion first to make sure your idea is aligned with the project goals.

​
Components Setup Guide

  1. Clone the repository:
  1. Install all dependencies:
  1. Run local servers and watch for changes:
  1. Add a new folder under packages and build your component.
  2. Don’t forget to add tests.
  3. Submit a pull request.

​
Opening issues

Open an issue to report bugs or to propose new features.
  • Reporting bugs: describe the bug as clearly as you can, including steps to reproduce, what happened and what you were expecting to happen. Also include browser version, OS and other related software’s (npm, Node.js, etc) versions when applicable.
  • Suggesting features: explain the proposed feature, what it should do, why it is useful, how users should use it. Give us as much info as possible so it will be easier to discuss, access and implement the proposed feature. When you’re unsure about a certain aspect of the feature, feel free to leave it open for others to discuss and find an appropriate solution.

​
Proposing pull requests

Pull requests are very welcome. Note that if you are going to propose drastic changes, be sure to open an issue for discussion first, to make sure that your PR will be accepted before you spend effort coding it.
  • Forking the repository: clone it locally and create a branch for your proposed bug fix or new feature. Avoid working directly on the main branch.
  • Making changes: implement your bug fix or feature, write tests to cover it and make sure all tests are passing. Then commit your changes, push your bug fix/feature branch to the origin (your forked repo) and open a pull request to the upstream (the repository you originally forked)‘s main branch.