How to Contribute
How to Contribute
Section titled “How to Contribute”Thank you for your interest in contributing to CoogCasa! This guide will help you get started.
Ways to Contribute
Section titled “Ways to Contribute”1. Report Bugs
Section titled “1. Report Bugs”Found a bug? Open an issue with:
- Clear title describing the bug
- Steps to reproduce
- Expected vs actual behavior
- Screenshots (if applicable)
- Browser/device information
2. Suggest Features
Section titled “2. Suggest Features”Have an idea? We’d love to hear it!
- Check existing issues first
- Open a new issue with the
enhancementlabel - Describe the feature and its use case
- Include mockups if you have them
3. Improve Documentation
Section titled “3. Improve Documentation”Documentation is always appreciated:
- Fix typos and errors
- Add missing information
- Improve clarity
- Add examples
4. Write Code
Section titled “4. Write Code”Ready to code? Here’s how:
- Check open issues
- Look for
good first issuelabels for beginner-friendly tasks - Comment on the issue to claim it
- Follow the PR process below
Getting Started
Section titled “Getting Started”Prerequisites
Section titled “Prerequisites”- Node.js 18+
- Git
- GitHub account
Fork and Clone
Section titled “Fork and Clone”- Fork the repository on GitHub
- Clone your fork:
git clone https://github.com/YOUR-USERNAME/CoogCasa.gitcd CoogCasa- Add upstream remote:
git remote add upstream https://github.com/KevinTrinh1227/CoogCasa.gitSet Up Development Environment
Section titled “Set Up Development Environment”# Websitecd webnpm installnpm run dev
# Docscd ../docsnpm installnpm run devCreate a Branch
Section titled “Create a Branch”Always create a branch for your work:
git checkout -b feature/your-feature-name# orgit checkout -b fix/bug-descriptionBranch naming conventions:
feature/- New featuresfix/- Bug fixesdocs/- Documentation changesrefactor/- Code refactoringstyle/- UI/styling changes
Making Changes
Section titled “Making Changes”1. Write Code
Section titled “1. Write Code”Follow our code style guide.
2. Test Your Changes
Section titled “2. Test Your Changes”npm run build # Ensure it buildsnpm run lint # Check for lint errorsnpm run test # Run tests (if available)3. Commit Your Changes
Section titled “3. Commit Your Changes”Write clear commit messages:
git commit -m "feat(web): Add scholarship search filter
- Add GPA filter dropdown- Add deadline filter- Update API client to support filters
Closes #123"Commit message format:
<type>(<scope>): <description>
[optional body]
[optional footer]Types: feat, fix, docs, style, refactor, test, chore
4. Stay Updated
Section titled “4. Stay Updated”Keep your branch up to date:
git fetch upstreamgit rebase upstream/main5. Push and Create PR
Section titled “5. Push and Create PR”git push origin feature/your-feature-nameThen create a Pull Request.
Code of Conduct
Section titled “Code of Conduct”Be Respectful
Section titled “Be Respectful”- Treat everyone with respect
- Be constructive in feedback
- Welcome newcomers
Be Helpful
Section titled “Be Helpful”- Answer questions when you can
- Share knowledge
- Help others succeed
Be Professional
Section titled “Be Professional”- Focus on the work, not personalities
- Accept constructive criticism
- Take responsibility for mistakes
Communication
Section titled “Communication”GitHub Issues
Section titled “GitHub Issues”- Primary place for bug reports and feature requests
- Use clear titles and descriptions
- Search before opening new issues
Discord
Section titled “Discord”- Real-time discussion
- Quick questions
- Community chat
Recognition
Section titled “Recognition”Contributors are recognized in:
- Release notes
- CONTRIBUTORS.md file
- Community shoutouts
Questions?
Section titled “Questions?”- Check the documentation first
- Search existing issues
- Ask on Discord
- Open a new issue
Thank you for contributing to CoogCasa! Your help makes a difference for UH students. 🐾