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. πππ½
Google Season of Docs 2022 (GSoD) is coming up and the application process is opening soon on February 23, 2022. As you can imagine, I'm submitting an application for the AsyncAPI initiative once it's open. π
In anticipation of this, I have also created a new AsyncAPI Slack channel named #temp-gsod-2022
that you can now 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
For this time period, Docs got to talk through a lot of cool changes coming up within the DESIGN side of the initiative!
/website
issue #453 update: Our design contributor @mcturco finished the ideation and design of our new feedback card that would be added at the bottom of each Docs page. But now we need a developer contributor to add it to the Docs.
- blog: Apicurio and AsyncAPI
- blog: radical transparency
- Provided input about adding sticky nav bar on Docs
- docs: adding custom styling to react component
- blog: add release notes for 2.3 release
- Provided input on adding Go Back and Up Next Buttons in docs
- docs: added asyncapi-format in tooling.md
- Provided input and grid/card design idea for proposed
/tools
landing page by contributor @iamVP7 - blog: 2021 at AsyncAPI
- Provided input on getting push notifications in #docs Slack channel for broken links found in READMEs
- Admitted I wasn't a fan of pre-commit hooks. πͺπ
- blog: Openforce
Badass and genius @barbanio strikes again, this time for creating 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:
I'm finally tackling the writing for /website
issue #350 in Q1 of 2022.
As promised in the previous Gist, here is that scintillating Draft
PR that can now be followed for updates: asyncapi/website#601. The goal is to have preview links to help community members better visualize current proposed changes in 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:
- @barbanio
- @nadjahagen: she wrote the blog post on Apicurio and AsyncAPI
- @fmvilas
- @akshatnema
- @magicmatatjahu
- @thim81
- @dalelane
- @lukasz
- @mcturco
There is always something to do for OSS Docs, and it's no different for us! π
We could really use contributors for the following Docs issues:
- Development work for β¨NEWβ¨ Docs
feedback card
#453 - Technical Writing for defining
server
in spec #587 - Development work for β¨NEWβ¨ Docs homepage, based on new design components created in #503
That's it for now. See you in 2 weeks! -A.Q. π©π»βπ» y Canela πβπ¦Ί