This repository contains reusable HTML components styled with Tailwind CSS. The components are designed to be used in various web projects.
Component-Next is a collection of ready-to-use HTML components styled with Tailwind CSS. These components help developers quickly integrate modern, responsive web design into their projects.
The goal of this project is to provide developers with a set of highly customizable, reusable components that can be easily integrated into any web application. The components are designed to follow the best practices of web development with a focus on performance and accessibility.
To use these components in your project, follow the steps below:
Clone this repository using Git:
git clone https://github.com/iranpsc/component-next.git
cd component-nextBefore starting, make sure you have installed Node.js and npm. Then, install the necessary dependencies by running:
npm installTo enable custom scrollbars in your project, you need to install the tailwind-scrollbar plugin:
npm install tailwind-scrollbarThen, add the plugin to your tailwind.config.js file:
module.exports = {
theme: {
extend: {},
},
plugins: [
require('tailwind-scrollbar'),
],
}You can use these components by copying the HTML structure and Tailwind CSS classes into your own web project. Feel free to customize the components as needed.
To build the project (e.g., compile the components into the final build version), you can run the following command:
npm run buildThis will generate the final output in the dist/ directory, including your CSS files.
We welcome contributions! If you'd like to contribute to this project, feel free to open issues or submit pull requests. Follow the contribution guidelines below to ensure a smooth collaboration.
-
Create a Separate Branch for Each Feature
For each new feature or bug fix, create a new branch off of themainbranch. The branch should follow the naming conventionfeature-[description]orbugfix-[description]. For example:git checkout -b feature-navbar-component
-
Commit Regularly with Detailed Messages
Make small, frequent commits with clear, descriptive commit messages that explain the changes you made. This helps maintain an organized history and makes it easier to track changes.Example:
git commit -m "Added responsive navbar component" -
Submit Pull Requests for Code Review
Once your feature is complete, submit a pull request (PR) to merge your branch into themainbranch. All PRs should be reviewed and approved before merging. Make sure to resolve any merge conflicts before submitting. -
Follow Coding Standards
Ensure that your code follows the established coding standards for the project. Consistent code improves readability and maintainability. If you're unsure about a particular standard, review the existing code or ask for guidance.
This project is licensed under the MIT License.