As an Open-Source (OSS) contributor, I volunteer to write periodic updates about the AsyncAPI Docs ecosystem every 2 weeks.
I want to note that this is not an official AsyncAPI Initiative update, but a personal summary I'm volunteering to write up for the OSS community. The goal is to let you know what's going on in the Docs area and how the Docs area has been teaming with other areas within the AsyncAPI Initiative. 😀👍🏽
As mentioned in previous Gists, we invested quality time in our application to GSoD 2022.
I published an AsyncAPI blog post announcing our GSoD application and projects, and we have a GH GSoD Docs Discussion where I will update the community of our application's status. Google will anounce which applications were accepted on April 14.
I'm also happy and humbled to see several folks already reached out, asked for Docs good-first-issues, and already opened a PR. 🌠
Lastly, there's also an open PR for creating organization level pages for GSoC and GSoD in our AsyncAPI website under Community, because it's another great way to add transparency of how we approach those programs.
Don't forget that we have an AsyncAPI Slack channel named #temp-gsod-2022 that you can join here. This slack channel is a temporary channel to coordinate GSoC 2022 setup. I'll publish regular updates on where we are in the application process, so stay tuned as the applicate date grows closer. 🙂
Join the #temp-gsod-2022 slack channel for:
- mentees identification
- mentors identification
- ideas identification
- mentees and ideas and mentors matching
Badass and genius @barbanio continues to strike again, for continuing to create educational and technical video scripts for a new series that explains AsyncAPI's main features.
We originally started discussing how this could be done via issue #155, but then @Barbanio created detailed outlines for a whole video series.
For now, here are her video scripts I helped review/edit/improve:
We're tackling the writing for /website issue #350. Here's that scintillating Draft PR that can be followed for updates: asyncapi/website#601. Check out the preview link to help you better visualize the current progress.
Notice how we're also in the design and development stage, because @magicmatatjahu is adding our content bucket cards in our NEW Docs /homepage.
@mcturco is creating new design guidelines to account for spacing/font/etc in the left-hand navigation.
You may also remember from a previous Gist Docs update that Design contributors were teaming with Docs on /websiteissue #453 for the ideation and development of a new feedback card that would be added at the bottom of each Docs page.
For now, we are still in the contributor development stage, with @akshatnema currently working on addressing feedback from several folks in the community. We're super thankful to his dev contribution and we'll keep you updated on his awesome progress. 🌠
A BIG thank you 🤗 to all of our OSS contributors; without you, there would be no OSS initiative! 😄🎉
For this biweekly update Gist, let's give a round of applause to:
- @akshatnema (
Feedback card) - @Barbanio (Educational Videos)
- @magicmatatjahu (Docs homepage updates)
- @mcturco (Design contributions)
- @deberg (always around to help review PRs 😄)
- @nafees87n (From the
GSoDchannel, where he completed his first Docsgood-first-issueticket!)
There is always something to do for OSS Docs, and it's no different for us! 😄
If you'd like to get involved, pick up an issue from our AsyncAPI GH Board.
That's it for now. See you in 2 weeks! -A.Q. 👩🏻💻 y Canela 🐕🦺