Create educational & technical video explaining AsyncAPI's main features

[quetzalliwrites]

Reason/Context

Creating an educational & technical video explaining AsyncAPI's main features will be helpful for new on-boarders that need a high-level intro to the spec.

This video can be used for any kind of audience and should be agnostic-minded.

---

Tagging @derberg @Barbanio @fmvilas

(note: Can lukasz or someone help me tag Debi into this issue? I don't know her GH handle and me trying @Docjones doesn't seem to be working here, that seems to belong to someone named Mark?...)

[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.

[Barbanio]

@alequetzalli That's a great idea, of course, count me in. I understand that the main objective is a promotional and educational video that summarizes what AsyncAPI is, can it be?
On the other hand, I wonder if it is better to make a single video or a series of these. What do you think?

[Docjones]

Guess that's not related to me in any way...?

[derberg]

@alequetzalli GH sucks in proper support to research on user handle when tagging -> @doc-jones (this is our Doc 😄 )

@Docjones not, but you can join us here, especially if you did not hear about AsyncAPI and much about Event-Driven Architecture before, we would love to see some validate the script and idea for the video 😄

[boyney123]

@alequetzalli I love the idea, would of helped me loads when I was learning what's going on and the ins + outs of AsyncAPI.

On the other hand, I wonder if it is better to make a single video or a series of these. What do you think?

@Barbanio think my vote would be series of smaller videos, each video that focuses on a particular part of the spec, just some examples

• What is AsyncAPI
• Why it was created
• Defining Events with AsyncAPI
• Publish/Subscribe
• etc...

To be honest once you get passed that stuff, would be cool to go into features like, Modelina, Studio, CLI etc.... (maybe)

[Barbanio]

Hi! I would like to start working on this. I agree with a series of short videos would be best.

My proposal is as follows:

• Videos of 10-15 minutes in length.
• Starting with general topics and gradually covering more specific topics as @boyney123 points out.
• The videos would be free and open access.
• Could we have a section on the AsyncAPI website for this in "Learning"?

What do you think? Who would be interested in participating?

[quetzalliwrites]

I am interested in participating, but mostly because I want women on those videos too. 😀 (@Barbanio, would you also do some of them so that we have several women faces too? ❤️✨✨)

I love the idea of creating a playlist for this learning vids and of thinking more about what creating a simple Learning platform for us could look like. 😀 I have started thinking about this more and more lately!!

[Barbanio]

Great @alequetzalli! Of course, we have to give more visibility to women in the sector 💜

[derberg]

I suggest rethinking the length of videos or basically being flexible there. When you will work on scripts, consider 1min length of videos to later release these as YouTube Shorts. Shorter videos, more chance people will watch it

[Barbanio]

Yes, we could make the videos of 5-15 minutes, being flexible here, and then take out a teaser for social networks.

[doc-jones]

Since this is basically an experiment, we should do all the things with a plan to measure the results so that we can do more of what works and less of what doesn't. Does our audience want 1 min teaser videos or should we do longer videos? What about adding links in the Show More tab? As an avid consumer of Youtube videos, I always appreciate those links pointing me to where I can get more information or detail.

I would think the length of videos is a result of the topic or content covered. So maybe we start with a list of topics like @boyney123 presented and see how long it takes to cover that topic? I'm a fan of experimentation when doing a new thing, because it gives our audience the chance to choose and we learn more from it. The key will be a plan to measure our results.

[doc-jones]

@alequetzalli GH sucks in proper support to research on user handle when tagging -> @doc-jones (this is our Doc 😄 )

"@"Docjones not, but you can join us here, especially if you did not hear about AsyncAPI and much about Event-Driven Architecture before, we would love to see some validate the script and idea for the video 😄

For future reference, the link to my github presence is given on my LinkedIn profile. Alternatively, you could just ask me. heh

[boyney123]

Since this is basically an experiment, we should do all the things with a plan to measure the results so that we can do more of what works and less of what doesn't

Yeah I agree with @doc-jones here, we should do some things and learn from feedback etc (whatever that looks like)

Does our audience want 1 min teaser videos or should we do longer videos?

Same with @doc-jones I'm a huge user of Youtube to learn stuff, 1 minute videos personally would not be enough for me, when I learn a new tool or thing I personally want more than a minute, something high level, with slight level of detail, but having more detailed videos if I wanted them (maybe we do them in the future).

I'm also interested in helping out and making some videos count me in :)

[derberg]

We should just be flexible and try to satisfy as many different users as possible. There will always be different preferences and thing that @Barbanio wrote I think makes most sense

Yes, we could make the videos of 5-15 minutes, being flexible here, and then take out a teaser for social networks.

Why? because we already have one experiment done: https://www.youtube.com/watch?v=pU71J-F7pfI

I recorded ☝🏼 this last year, for the Hacktoberfest participants, there was a series of videos that I wanted to give folks to onboard them quickly to contributions. As you can see, quality is not what attracts people there (I did not have good equipment at that time, paid by Open Collective, not Postman 😆 ) and I'm also not 100% happy with the content. What I do know is that people open it up for 2 reasons:

• title
• they see it is super short

does it mean we should have only short videos? NO 😄
it is just that when you will work on scripts for videos, I bet there will always be a chance to figure a "short version" and "advanced version". Like basically "watch short? want more details explanation, watch longer one"

Anyway, love the initiative ❤️