Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: new style guide - Glossary #1294

Closed
Tracked by #1240
quetzalliwrites opened this issue Feb 2, 2023 · 5 comments
Closed
Tracked by #1240

docs: new style guide - Glossary #1294

quetzalliwrites opened this issue Feb 2, 2023 · 5 comments
Assignees
Labels
area/docs Specify what technical area given issue relates to. Its goal is to ease filtering good first issues. 📑 docs good first issue Good for newcomers stale

Comments

@quetzalliwrites
Copy link
Member

quetzalliwrites commented Feb 2, 2023

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?

  • Glossary: A glossary can help to ensure consistency in the use of terminology throughout your documentation, which can improve clarity and comprehension for readers. The guidelines can include instructions on the types of terms to include, how to define and format them, and how to maintain and update the glossary over time. (Source: OpenAI's ChatGPT)

Where should this go?

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

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

Extra Resources

@quetzalliwrites quetzalliwrites changed the title Glossary docs: new style guide - Glossary Feb 2, 2023
@quetzalliwrites quetzalliwrites self-assigned this Feb 2, 2023
@quetzalliwrites quetzalliwrites added 📑 docs area/docs Specify what technical area given issue relates to. Its goal is to ease filtering good first issues. labels Feb 2, 2023
@quetzalliwrites quetzalliwrites moved this to Changes proposed 📄 ✨✨ in AsyncAPI Docs Board Feb 2, 2023
@octonawish-akcodes
Copy link
Contributor

Can I take this one

Copy link
Member Author

heyo! we'll assign this task once we've completed the previous ones so we get it done in order... glad we already synced via DM slack too ✌🏽😄

@CynthiaPeter
Copy link
Contributor

Adding this discussion link shared by @derberg.

@rukundob451
Copy link
Contributor

Adding this discussion link shared by @derberg.

Sure sure, we do.

Copy link

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Mar 10, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docs Specify what technical area given issue relates to. Its goal is to ease filtering good first issues. 📑 docs good first issue Good for newcomers stale
Projects
Status: In progress 😀👍🏽
Development

No branches or pull requests

4 participants