docs: add content for module 4

[mhmohona]

---

Module 4: Creating and Validating AsyncAPI Documents

Reaction: With the spaceship fixed, Eve looks forward to testing communication with Chan.

• Writing and documenting AsyncAPI code from scratch.
• Utilizing AsyncAPI tools for document validation.
• Hands-on exercises for creating and validating AsyncAPI documents.

---

Related issue(s)
asyncapi/website#1520

[quetzalliwrites]

Hey folks, so please update your planet names to:

• Eve's planet: Capuccinova
• Chan's planet: Brownieterra

[derberg]

just one comment

to be honest killercoda tutorials is hard to review as there is no preview

I think technically accurate except of one comment I left

on to you @alequetzalli

[smoya]

@mhmohona I would like to get a clarified description of what this module wants to show because I don't see just a different approach on https://github.com/asyncapi/learning-paths/pull/9/files#r1494514714.

For example, it says nothing about generating code.

cc @alequetzalli

[quetzalliwrites]

...I would like to get a clarified description of what this module wants to show because I don't see just a different approach on https://github.com/asyncapi/learning-paths/pull/9/files#r1494514714. For example, it says nothing about generating code.

Sergio, yes, thank you for bringing this problem to our attention! I agree. It was also my bad for not catching myself earlier. 😬 Please find learning path modules' outline below:

---

Module 1: Introduction to AsyncAPI

Scene: Chan's ship crash-lands in Eve's backyard, initiating their adventure with AsyncAPI.

• What is AsyncAPI? An introduction to its purpose and capabilities.
• Why use AsyncAPI? Exploring its benefits and applications.
• Real-world use cases of AsyncAPI.

Module 2: Event-Driven Architectures

Reaction: Eve helps check Chan’s spaceship engine, introducing event-driven architectures.

• Introduction to event-driven architectures and their significance.
• How AsyncAPI facilitates designing event-driven systems.
• Designing APIs for microservices using AsyncAPI for effective integration.

Module 3: AsyncAPI Specification

Scene: Eve assists Chan in programming his spaceship, ensuring they can communicate.

• Understanding the AsyncAPI document structure and its core components.
• Deep dive into AsyncAPI's components: info, channels, components, tags, etc.
• Defining operations, messages, and schemas within AsyncAPI documents.

Module 4: Creating and Validating AsyncAPI Documents

Reaction: With the spaceship fixed, Eve looks forward to testing communication with Chan.

• Writing and documenting AsyncAPI code from scratch.
• Utilizing AsyncAPI tools for document validation.
• Hands-on exercises for creating and validating AsyncAPI documents.

Module 5: Summary & Next Steps

End Scene: Reflecting on the journey as Chan returns to his planet.

• Recap of what was learned across the modules.
• Recommend exploring AsyncAPI tools.
• Additional resources for extended learning, including documentation links and the AsyncAPI YouTube channel.

cc @smoya

[quetzalliwrites]

@mhmohona While this mentions creating an AsyncAPI document and document validation, we're still missing code creation with AsyncAPI.

[quetzalliwrites]

@mhmohona Thank you for adding code generation to your PR. 😄

Before we give this another technical review round, please notice how we have 2 sections repeating info about testing your work with the Studio tool. Please keep only one and remove the duplicate section.

[github-actions]

This pull request 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 pull request, add a comment with detailed explanation.

There can be many reasons why some specific pull request 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 pull request forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️