How can I start contributing effectively to this project and make meaningful PRs for GSSoC’24?

[PratikRaval123]

Hi maintainers and community! 👋

I'm a participant in GSSoC’24 and super excited to contribute to this amazing project. I'm looking forward to making my first contributions and learning through open-source collaboration.

Could you please guide me on:

Which issues are good for beginners or first-time contributors?

Are there any specific areas or features of the project that need help right now?

Do you have any contribution guidelines or tips to ensure my PRs are accepted?

How can I stay consistent and eventually become a valuable contributor?

I'm comfortable with JavaScript, React, Next.js and eager to take up any tasks where I can help. 🚀

Looking forward to your suggestions and getting started!

Thanks in advance!

[vnaik10]

Beginner-Friendly Issues:
• Look for “good first issue” or “help wanted” labels (often docs, small UI fixes).

Current Help Needed:
• Update docs/setup guides; minor React/Next.js bug fixes; add or refine UI components; write tests.

PR Guidelines:
• Fork → branch → PR; follow ESLint/Prettier; reference issue number; include tests/docs; use clear commit messages.

Consistency & Growth:
• Schedule regular contribution time; start with small issues, then larger tasks; join community chats; request and offer reviews.

[lothartj]

Beginner-Friendly Issues:

• Look for issues labeled "good first issue" or "help wanted"
• These usually involve things like:
  • Updating documentation
  • Fixing small UI bugs
  • Cleaning up code or making small component tweaks

Areas That Need Help Right Now:

• Improving the setup guides or contribution docs
• Fixing minor bugs in React or Next.js components
• Writing or updating unit tests
• Refactoring or enhancing smaller UI pieces

PR Guidelines:

• Fork the repo, make a new branch, then submit a pull request
• Follow the existing code style (ESLint, Prettier, etc.)
• Reference the issue number you're addressing (e.g. Fixes about mentor #123)
• Keep commit messages clear and descriptive
• Add comments or update docs if needed
• Include tests if you're fixing a bug or adding a feature

Staying Consistent & Growing as a Contributor:

• Set aside regular time each week to contribute (even 1–2 hours)
• Start with smaller tasks, then work your way up to bigger ones
• Join the community chats if there are any
• Give and ask for code reviews – it helps you learn a lot
• Don’t worry about making mistakes – that’s part of the process

Let me know if you’d like help picking your first issue or walking through your first PR!