The FerUI project team welcomes contributions from the community. Together, we can grow FerUI and make it a better framework.
Before you contribute in any way to FerUI, please make sure to read our code of conduct.
Because FerUI provides everything from the abstract patterns of a design system to the implementation of accessibility for Angular components, contributions to FerUI can take many forms, and each of them will correspond to part of the full process. Generally speaking, contributions fit into one or more of these categories:
- New design or update to an existing one: general patterns, components, features, ... See Contributing to Design.
- Implementation of an existing design and bug fixes (which might involve a design). See Contributing to Development.
- Documentation. See Contributing to Documentation.
Many contributions can fall into more than one of these categories at once but it's important to split the contribution along these steps, to make sure each of them is solid before moving on to the next. For instance, if you want to contribute a brand new Angular component to Clarity you'll first need to go through a design submission step, then you can move to the development contribution process once the design has been finalized, and finally you can add the corresponding documentation to the website (that step is strongly recommended but optional, we know how it is...).
- Explain the use case
- Provide designs for the usual case
- Provide error states
- Edge cases
- i18n/long text visuals
- Example with scrollbars for Windows devices
- Accessibility recommendation (tab order, keyboard navigation, ...)
- Describe motion if needed or provide a GIF for it
Barring exceptionally small contributions like one-line bug fixes, please follow the process described in DEVELOPMENT_CONTRIBUTION.md.
The FerUI documentation website is also in this repository in the dev
folder. You can contribute to the documentation by submitting pull requests.
You can submit an issue or a bug to our GitHub repository. You must provide:
- The link to the reproduction scenario you created using the FerUI Stackblitz Template
- If possible please provide a minimal demo illustrating the issue by forking one of the FerUI Stackblitz Templates
- The version number of Angular
- The version number of FerUI
- The browser name and version number