Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional documentation, we greatly value feedback and contributions from our community.
Please read through this document before submitting any issues or pull requests to ensure we have all the necessary information to effectively respond to your bug report or contribution.
- Prettier - Code formatter using prettier
- ESLint - Integrates ESLint JavaScript into VS Code.
- CodeSpellChecker - Spelling checker for source code
- Tailwind IntelliSense - Intelligent Tailwind CSS tooling for VS Code
- ViteTest - A test runner for vite
We use GitHub Issues to track public bugs and features. Report a bug by opening a new issue; it's that easy!
We welcome your contributions. To make the process as seamless as possible, we ask for the following:
-
Go ahead and fork the project and make your changes. We encourage pull requests to discuss code changes.
-
When you’re ready to create a pull request, be sure to:
-
Have test cases for new code. If you have questions about how to do it, please ask in your pull request.
-
Run all the tests to ensure nothing else was accidentally broken.
-
We use GitHub Pull Requests for this purpose.
We also welcome your contributions to the documentation of this project. If you see an area for improvement, please submit a pull request.
Please ensure all your code changes retain proper attribution.
We have a code of conduct, please follow it in all your interactions with the project.
Your contributions will be under the same license as the original project, as described in the LICENSE file.
Thank you for your interest and we look forward to your contributions!