-
Notifications
You must be signed in to change notification settings - Fork 4
Contribution Guidelines
Shaheer Ahmad edited this page Dec 17, 2025
·
1 revision
We love contributors! Here is how you can help.
Be respectful and kind. Harassment of any kind will not be tolerated.
- Fork the Repo: Click the "Fork" button on GitHub.
-
Clone your Fork:
git clone https://github.com/YOUR_USERNAME/365connectcommunity.github.io.git
-
Create a Branch:
git checkout -b feature/amazing-new-feature
- Make Changes: Write your code.
-
Commit:
Use conventional commits (feat, fix, docs, style, refactor).
git commit -m "feat: Add amazing new feature" -
Push:
git push origin feature/amazing-new-feature
- Open a Pull Request: Go to the original repo and click "New Pull Request".
-
Formatting: We use Prettier/ESLint. Run
npm run lintbefore committing. - Components: Keep components small and focused.
- Styling: Use Tailwind CSS utility classes. Avoid custom CSS files unless necessary.
-
Images: Put images in
public/assets.
Please open an Issue on GitHub with:
- Steps to reproduce.
- Expected behavior.
- Screenshots (if applicable).
Home • GitHub Repository • Report an Issue • Contribute
Maintained with ❤️ by the 365Connect Community Team.
© 2025 365Connect Community. Licensed under MIT.