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. πππ½
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 #503 update: chatting still w/ @mcturco through the ideation and development of a /new page added to the Docs to be a new homepage for our Docs./website
issue #518 update: chatting still w/ @mcturco through the ideation and development of a new diagram to be added to the homepage of the docs./website
issue #453 update: chatting still w/ @mcturco through the ideation and development of a new feedback card that would be added at the bottom of each Docs page.
- added asyncapi-format in tooling.md #569
- chore(blog): added blog post on Apicurio and AsyncAPI #533
- docs: add Automated Version Bump for AsyncAPI as GH action #560
- docs: add custom styling & custom logo #531
- docs: add a guide to blog.md #118
- chore: extend contributor guide with info about PR merging automation #211
- feat: add marketing and social media design to areas if contributions #20
- feat: add supported by section on landing page #558
I'm finally tackling the writing for /website
issue #350 in Q1 of 2022. I am still working on the rough drafts for adding intro copy to the new tools, tutorials, and concepts landing pages. I'm also doing new intro copy to the Docs for the new Homepage we're adding to the Docs.
Next update I will likely have a Draft
PR link that I can append to show progress visually too. My goal is to have preview links to help community members better visualize current proposed changes in place.
- fixing incorrect docs label in issue template: this one was good to take care of because the new Docs issue template had the incorrect label in it! Now that it's fixed, new issues will be tagged correctly with the correct Docs label.
That's it for now. See you in 2 weeks! -A.Q.