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]: Identify topics to cover in first interactive learning path #1523

Closed
1 task done
quetzalliwrites opened this issue Apr 7, 2023 · 4 comments
Closed
1 task done
Assignees
Labels
area/docs Specify what technical area given issue relates to. Its goal is to ease filtering good first issues. 📑 docs gsod This label should be used for issues or discussions related to ideas for Google Season of Docs stale

Comments

@quetzalliwrites
Copy link
Member

What Dev Docs changes are you proposing?

As part of Google Season of Docs 2023 at AsyncAPI, we're going to create a 100-level interactive learning path.

Our only educational content is static AsyncAPI documentation; the community needs more engaging and interactive ways to learn AsyncAPI concepts and architecture. To make learning AsyncAPI more accessible and enjoyable, we propose creating interactive learning paths that incorporate best practices. Our solution is to create interactive learning paths with engaging videos, gamification elements, immersive storylines with eLearning characters, badges, quizzes, points systems, etc.

➡️ This task belongs to the following Docs EPIC: #1520.

What will this task cover?

Conduct research on AsyncAPI concepts and architecture to identify the most important topics to cover in the interactive learning path. This includes reviewing the existing static documentation and identifying gaps in the content.

NOTE: The first learning paths can re-purpose content from the current AsyncAPI Docs content buckets of tutorials and concepts, which were created thanks to GSoD 2022.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@quetzalliwrites quetzalliwrites added 📑 docs area/docs Specify what technical area given issue relates to. Its goal is to ease filtering good first issues. gsod This label should be used for issues or discussions related to ideas for Google Season of Docs labels Apr 7, 2023
@quetzalliwrites quetzalliwrites self-assigned this Apr 7, 2023
@quetzalliwrites quetzalliwrites moved this to Changes proposed 📄 ✨✨ in AsyncAPI Docs Board Apr 7, 2023
@quetzalliwrites
Copy link
Member Author

assigned to @TRohit20 and @kakabisht

@quetzalliwrites
Copy link
Member Author

Might get some other good ideas here from last year discussion on tutorials:
https://github.com/orgs/asyncapi/discussions/379

@TRohit20
Copy link
Collaborator

Working on it

@quetzalliwrites quetzalliwrites moved this from Changes proposed 📄 ✨✨ to In progress 😀👍🏽 in AsyncAPI Docs Board Jul 12, 2023
Copy link

github-actions bot commented Mar 4, 2024

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 4, 2024
@TRohit20 TRohit20 closed this as completed Mar 4, 2024
@quetzalliwrites quetzalliwrites moved this from In progress 😀👍🏽 to Done 🚀 in AsyncAPI Docs Board Mar 25, 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 gsod This label should be used for issues or discussions related to ideas for Google Season of Docs stale
Projects
Status: Done 🚀
Development

No branches or pull requests

2 participants