How to Contribute - Flowbite React
Learn how you can start contributing to the open-source Flowbite React UI component library
First off, thanks for taking the time to contribute! ❤️
All types of contributions are encouraged and valued. See the Table of Contents for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
- Star the project
- Tweet about it
- Refer this project in your project's readme
- Mention the project at local meetups and tell your friends/colleagues
Table of Contents#
Code of Conduct#
I Have a Question#
If you want to ask a question, we assume that you have read the available Documentation.
Before you ask a question, it is best to search for existing Issues that might help you. We also have a Discord server where you can ask questions and get help from the community directly. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
If you then still feel the need to ask a question and need clarification, we recommend the following:
- Open an Issue.
- Follow the Issue template and fill it out as completely as possible. Don't forget to:
- Provide as much context as you can about what you're running into.
- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
We will then take care of the issue as soon as possible.
I Want To Contribute#
When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
Before Submitting a Bug Report
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
- Make sure that you are using the latest version.
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the documentation. If you are looking for support, you might want to check this section).
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the bug tracker.
- Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
- Can you reliably reproduce the issue? And can you also reproduce it with older versions?
How Do I Submit a Good Bug Report?
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
Don't forget to:
- Explain the behavior you would expect and the actual behavior.
- Please provide as much context as possible and describe the reproduction steps that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
- Provide the information you collected in the previous section.
Once it's filed:
- The project team will label the issue accordingly.
- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as
needs info. Bugs with the
needs infotag will not be addressed until they are reproduced.
- If the team is able to reproduce the issue, it will be marked
confirmed, as well as possibly other tags (such as
help wanted), and the issue will be left to be implemented by someone.
This section guides you through submitting an enhancement suggestion for flowbite-react, including completely new features and minor improvements to existing functionality. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
Before Submitting an Enhancement
- Make sure that you are using the latest version.
- Read the documentation carefully and find out if the functionality is already covered, maybe by an individual configuration.
- Perform a search to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
How Do I Submit a Good Enhancement Suggestion?
Enhancement suggestions are tracked as GitHub issues.
- Use a clear and descriptive title for the issue to identify the suggestion.
- Follow the Issue template for feature requests to the best of your ability.
Don't forget to:
- Provide a step-by-step description of the suggested enhancement in as many details as possible.
- Describe the current behavior and explain which behavior you expected to see instead and why. At this point you can also tell which alternatives do not work for you.
- You may want to include screenshots and animated GIFs which help you demonstrate the steps or point out the part which the suggestion is related to. You can use this tool to record GIFs on macOS and Windows, and this tool or this tool on Linux.
- Explain why this enhancement would be useful to most flowbite-react users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
Your First Code Contribution#
- You need to understand how to use a terminal, Git, Node.js, and Yarn
- You should be able to write Markdown and React TypeScript
- You should be familiar with Tailwind CSS, ESLint, and Prettier
- You should understand what vitest is, and be able to write tests if your contribution changes the behavior of the library in some way
- You should strongly consider using Visual Studio Code as your editor, as it has plugins for Tailwind CSS, ESLint, and Prettier which will automatically fix most style issues for you, and offer suggestions for how to fix the rest
Creating a Pull Request
- Fork the repository
- Clone the fork and add a remote called
git clone https://github.com/<your username>/flowbite-react.git cd flowbite-react git remote add upstream https://github.com/themesberg/flowbite-react.git
- Create a new branch named after your PR:
git checkout -b fix/accordion-alwaysopen
- Install dependencies with
- Start a development server on your machine:
- Commit changes with
yarn committo follow the required commitizen format:
- Make sure your changes work and don't break anything else:
yarn format && yarn lint && yarn test && yarn build
- Push to your forked repository
git push -u origin fix/accordion-alwaysopen
Fill out the Pull Request template, which will be available automatically
What Happens Next?
If you have followed the steps above, your Pull Request will be reviewed by a maintainer soon. If it passes review, it will be merged into the
main branch and will be included in the next release. If not, you will receive feedback about what needs to be improved until it is ready to be merged.
Please note that you will be expected to update the documentation and write appropriate unit tests if your contribution changes the behavior of the library in some way.
Improving The Documentation#
The documentation at flowbite-react.com can all be found inside the
app folder of this repository. It's written in Next.js, and we use Markdown for almost all of the content, so you don't need to even be able to write React TypeScript to make documentation changes!
We use Prettier to format all of our code. Please make sure to run
yarn format before committing any changes. You can also use VS Code as your editor, and install the Prettier and Tailwind CSS IntelliSense plugins to automatically format your code each time you save.
Please refer to the code written already in the project to see how we format our code, what naming conventions we use, and so on. The more consistent your code is with the rest of the project, the easier it will be to review and merge your Pull Request.
We use commitizen to format commit messages. Please use
yarn commit instead of
git commit when committing changes.
Branches & Pull Requests#
Please follow the same guidelines published by commitizen when you name a branch that will be used for a Pull Request. The branch name should be prefixed with the most significant change that will be introduced in the Pull Request.
For example, if you are fixing a bug in the accordion component, the branch name should be something like,
This guide is based on the contributing-gen. Make your own!