[📑 Docs]: Add content to "Where to Contribute" onboarding page

[me-pradeep]

What Dev Docs changes are you proposing?

I would like to contribute to AsyncAPI Docs by adding content to the
"Where to Contribute" page under the community onboarding section.

Currently, this page is marked as under construction and does not provide
guidance for new contributors. The proposed update would explain the different
ways people can contribute to AsyncAPI, such as documentation, code, testing,
design, and community support, along with basic guidance on how to get started.

This change would help improve onboarding for first-time contributors and make
it easier for them to identify suitable areas to contribute based on their
interests and skills.

Code of Conduct

• I agree to follow this project's Code of Conduct

Are you willing to work on this issue ?

Yes I am willing to submit a PR!

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[thulieblack]

The content needs to be defined first, and create an epic on what we want to do with the pages. cc @bandantonio, not sure your thoughts here?

[me-pradeep]

@thulieblack I have already defined the content , may I share?

[bandantonio]

@thulieblack Agreed, I thought it would be a great topic to discuss during our "Docs meeting"

@me-pradeep Sure, go ahead.

[me-pradeep]

@bandantonio @thulieblack

---

title: Where to Contribute

Where to Contribute

This section helps new contributors understand the different areas where they can contribute to the AsyncAPI project.

AsyncAPI welcomes contributions from people with different skill sets, experience levels, and interests.

Documentation

You can contribute to documentation by improving clarity and accuracy across guides and references.

Examples of documentation contributions:

• Fixing typos and grammatical errors
• Improving explanations and structure
• Adding examples or diagrams
• Updating outdated content

Relevant repositories:

• AsyncAPI Website
• AsyncAPI Specification

---

Code

Contributors can work on features, bug fixes, and enhancements across various AsyncAPI projects.

Common contribution areas include:

• Website frontend
• CLI tools
• Generators
• Core libraries

Relevant repositories:

• AsyncAPI CLI
• AsyncAPI Generator
• AsyncAPI Website

---

Testing and Quality

Help improve the reliability and stability of AsyncAPI by:

• Writing or improving tests
• Identifying and reporting bugs
• Improving test coverage

---

Design and User Experience

Design-focused contributions are also valuable and include:

• Improving UI and UX
• Creating diagrams or visual assets
• Enhancing accessibility

---

Community and Support

You can also contribute without writing code by:

• Helping contributors in Slack and GitHub Discussions
• Reviewing pull requests
• Improving onboarding and contributor resources

---

How to Get Started

To begin contributing:

• Look for issues labeled good first issue or help wanted
• Start with small documentation updates or minor bug fixes
• Join the AsyncAPI Slack workspace to ask questions and get guidance

[thulieblack]

This is too generic and doesn't reference the existing docs written. @me-pradeep did you got through the TW onboarding checklist and Style Guide?

[me-pradeep]

@thulieblack Thanks for pointing this out. You’re right the content was too generic. I’ve gone through the TW onboarding checklist and the Style Guide and updated the content to reference existing documentation and align better with the current structure and tone.
Please let me know if there’s anything specific you’d like adjusted further.

---

title: Where to Contribute

Where to Contribute

This page explains the main areas where contributors can get involved in the AsyncAPI project. Contributions are welcome from people with different skills, experience levels, and time availability.

You do not need to be an expert to contribute. Many contributions start with small improvements.

---

Documentation

Documentation contributions focus on improving clarity, correctness, and usefulness of existing content across guides, tutorials, and reference materials.

Examples of documentation contributions include:

• Fixing typos, grammar, and broken links
• Clarifying unclear explanations
• Improving structure or readability
• Adding examples, diagrams, or references
• Updating outdated or deprecated information

Relevant repositories:

• AsyncAPI Website
• AsyncAPI Specification

Before contributing, review the documentation Style Guide to ensure consistency.

---

Code

Code contributions involve improving AsyncAPI tools, libraries, and infrastructure.

Common areas include:

• Website frontend features and fixes
• CLI enhancements and bug fixes
• Generator templates and logic
• Core libraries and tooling

Relevant repositories:

• AsyncAPI CLI
• AsyncAPI Generator
• AsyncAPI Website

Each repository contains contribution guidelines specific to that project.

---

Testing and Quality

Testing contributions help improve the reliability and stability of AsyncAPI projects.

You can contribute by:

• Writing or improving automated tests
• Increasing test coverage
• Reproducing, reporting, or verifying bugs

Testing improvements are valuable even when no new features are added.

---

Design and User Experience

Design-focused contributions help improve how users interact with AsyncAPI tools and documentation.

Examples include:

• Improving UI and UX
• Creating or refining diagrams and visual assets
• Enhancing accessibility and visual consistency

Design discussions often start in GitHub issues or Slack.

---

Community and Support

Non-code contributions are essential to the project’s health.

You can help by:

• Answering questions in Slack or GitHub Discussions
• Reviewing pull requests
• Improving onboarding or contributor documentation
• Helping triage issues

---

How to Get Started

To start contributing:

• Look for issues labeled good first issue or help wanted
• Begin with small documentation or minor fixes
• Review the Technical Writer onboarding checklist if contributing to docs
• Join the AsyncAPI Slack workspace to ask questions and get guidance