Contributing Guidelines & Community Guide

[DokaIzk]

Title: docs: update contributing guidelines with code style, review process, and community standards

Complexity: medium

Time Estimate: 5-7 hours

Description:
Update and expand CONTRIBUTING.md with clear guidelines for all contribution types. Cover code style, commit conventions, PR process, and community expectations.

Deliverables:

• Code Style Guidelines

  • Python (PEP 8, type hints, linting)
  • TypeScript/JavaScript (ESLint, Prettier)
  • Rust (clippy, fmt)
  • CSS/Tailwind class organization
  • SQL (formatting, naming conventions)

• Git Workflow Guide

  • Branching strategy (main/develop)
  • Commit message conventions (Conventional Commits)
  • Force push rules
  • Squashing vs rebasing
  • Cherry-picking policy

• Pull Request Process

  • PR title and description template
  • Required checks and reviews
  • How to respond to review feedback
  • When to request changes vs approve
  • Merging strategy (squash/rebase/merge)

• Issue Management

  • Issue labeling system
  • Triaging new issues
  • Issue prioritization
  • Issue assignment procedures

• Community Standards

  • Code of conduct
  • Communication norms (Slack, GitHub)
  • Resolving conflicts
  • Welcoming new contributors
  • Mentorship opportunities

• Documentation Contributing

  • How to write docs
  • Documentation style guide
  • Adding to Docusaurus
  • Reviewing docs PRs

• Contributor Recognition

  • Contributors list/hall of fame
  • Recognition system
  • Swag/rewards for major contributions
  • Becoming a maintainer

Problem Context:
Contributing guidelines are minimal. Code style is inconsistent. Review process unclear. Hard to onboard new contributors.

Scope:

• Update CONTRIBUTING.md in root
• Create detailed guides in docs/contributing/
• Link to existing style guides (black, ESLint)
• Include examples of good PRs

---

[Tijesunimi004]

@Tijesunimi004 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Maintainer I have gained experience over different waves and would love to solve this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Tijesunimi004 to this issue.

[Mehcee]

@Mehcee has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mehcee to this issue.

[drips-wave]

Congratulations, @Mehcee! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Mehcee: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @Mehcee as part of the Stellar Wave Program's 6th Wave 🥳

😎 @Mehcee: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.