Thank you for your interest in Mística. You can contribute to this project in several ways:
- Pull Requests
- Bug reports
- Feature requests (no UI/UX changes)
- Documentation and help requests
- New component proposals or UI/UX changes
You can contact maintainers at the Mística Teams Channel. Don't hesitate to ask any questions and share your ideas
We would love to accept your Pull Requests but please, before starting your development, create an issue.
- PR title must follow conventional commits format; the scope must be the affected component name
(e.g.
fix(TextField): ...). If no component was affected but the change is internal you can use set "Chore" as the component name. For allowed types check lint action. - PR description: concise summary of the problem and fix, ending with
Ref: <TICKET-ID>(if there's a jira ticket). - Always add reviewers
aweell,atabel,yceballostandMarcosldto every PR.
If something is broken or not working as expected, let us know!
If you need additional functionality, support a new use case, improve a component API...
🚧 Open a Feature Request issue
Important: Your feature request should not include UI or UX changes, only implementation details, because
those kind of changes must be evaluated, approved and documented by the Design Core Team (see
New component proposals or UI/UX changes section).
Is something in our documentation not well explained? Do you need help using a component? Should we create a new Storybook story as example?
Adding a new component to the Mística Design System or updating the UI/UX of an existing one requires to
follow a process where the component and its use cases will be evaluated by the Design Core Team.
Share your ideas at the Mística Teams Channel or open an issue in the main Mistica Repository