docs: new style guide - Docs Contributions

[quetzalliwrites]

Let's finally get around to creating, designing, and incorporating an AsyncAPI Style Guide!

Why the need?

In tech jobs, we often focus on our technology's technical aspects, such as functionality and performance. However, the documentation for our technology is equally important to the code itself. A style guide ensures consistency and clarity, establishes a consistent voice and tone in your documentation, makes it easier for multiple writers to work together on a single doc, and helps ensure documentation is accurate and up-to-date. When all of your technical writers follow the same guidelines, it's easier for readers to find the information they need and understand how to use your product or OSS technology.

What section of the AsyncAPI Style Guide is this issue for?

• Docs contributions: Don’t leave technical writers clueless about the contribution guidelines for docs! They must understand content selection, prioritization, review processes, and releases.

Where should this go?

Let's create a new .md file for only the Docs contributions section of the new AsyncAPI Style Guide.

Create the following directory and place your file there: asyncapi.com/docs/community/styleguide/docs-contributions.md.

Extra Resources

• Write the Docs: Style Guides
• Gatsby Style Guide
• Gatsby Docs Structure & Documentation Types
• Mozilla Style Guide
• Google Style Guide
• Microsoft Style Guide

[octonawish-akcodes]

I wanna work on this one

[quetzalliwrites]

go for it!! ✨

[octonawish-akcodes]

Since we have the contributor's onboarding guide in progress which overlaps this issue's main agenda, we can close it.

[quetzalliwrites]

Thank you for pointing this out, agreed. Closing.