add a contributions page to docs

[amirfz]

TEMPLATE:

Onboarding new developers to an open-source project is a crucial step to ensure they have a smooth and successful integration into the community. Here's a template for the onboarding process that you can adapt and customize based on your specific project's needs:
Subject: Welcome to [Your Open Source Project Name] - Onboarding Process
Dear [New Developer's Name],
Welcome to the [Your Open Source Project Name] community! We are excited to have you on board and contributing to our project. This email outlines the onboarding process to help you get started and become an active member of our open-source community.

1. Project Overview:
   • Briefly introduce the project's purpose, goals, and target audience.
   • Share the project's mission and vision to give the new developer context.
2. Contribution Guidelines:
   • Direct them to the project's contribution guidelines and code of conduct.
   • Emphasize the importance of following these guidelines to maintain a healthy and inclusive community.
3. Communication Channels:
   • Provide a list of communication channels (e.g., Slack, Discord, mailing lists, forums) used by the community.
   • Explain the purpose of each channel and how to join them.
4. Development Environment Setup:
   • Provide detailed instructions on how to set up the development environment.
   • Include links to any relevant tools, dependencies, or style guides.
5. Codebase Overview:
   • Offer a high-level tour of the codebase to familiarize the new developer with the project's structure.
   • Point out essential directories, modules, and key components.
6. Starter Tasks:
   • Suggest beginner-friendly tasks that new developers can work on to get started.
   • Provide links to any "good first issues" or "beginner-friendly" labels in the issue tracker.
7. Mentoring/Buddy System:
   • Offer to pair the new developer with an experienced contributor (mentor/buddy) who can guide them through their first contributions.
   • Explain how they can reach out to a mentor if interested.
8. Community Events:
   • Inform the new developer about any upcoming community events, such as meetings, workshops, or hackathons.
   • Encourage participation in these events to build connections and share knowledge.
9. Recognition and Attribution:
   • Explain how the project recognizes and attributes contributions, such as through contributor badges, hall of fame, etc.
10. Feedback and Questions:

• Encourage the new developer to ask questions and seek help whenever needed.
• Provide contact details of community managers or project leaders for further assistance.
  Thank you for joining our open-source community! We believe that your contributions will make a valuable impact on [Your Open Source Project Name]. If you have any questions or need assistance during the onboarding process, please don't hesitate to ask.
  Happy coding!
  Best regards,
  [Your Name]
  [Your Open Source Project Name]
  [Website/Repository URL]
  [Contact Email/Handle]

[amirfz]

PR #96