chore: new docs blog post sharing Q1 Docs Report #1527
Conversation
quetzalliwrites
added
area/docs
quetzalliwrites
requested review from
derberg,
AceTheCreator,
thulieblack and
akshatnema
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Want to regain momentum with my Docs reports and make them more data driven this year. Since I'm making nicer reports, I will be turning them into blog posts to help give the community even more visibility into Docs progress. ✨ |
✅ Deploy Preview for asyncapi-website ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-1527--asyncapi-website.netlify.app/ |
pages/blog/2023-Q1-docs-report.md
Outdated
| tags: | ||
| - Documentation | ||
| - Communication | ||
| cover: /img/posts/gsod-2022/SeasonofDocs_Logo.webp |
There was a problem hiding this comment.
Accepting ideas/recommendations for best cover photo idea 😄
There was a problem hiding this comment.
From my perspective, since the blog covers all aspects of AsyncAPI documentation then the banner should definitely have that Ale's-documentation style vibes. 😊
There was a problem hiding this comment.
btw @alequetzalli only 18 applications, weren't you on your 50th interview sometime last year😂🤭
There was a problem hiding this comment.
- Yeah, I think I will make one of the mermaid diagrams of this report into the banner image! I think I will pick the diagram that summarizes the quarter work.
- Yes, last year I was far too lenient 😄😅... this year I realized that the best way to identify candidates for a writing program is have them take the time to write an application. If candidates don't take the time or passion to write a thorough application then they're not the right candidates for a writing program.😄🔥
|
@thulieblack @derberg @AceTheCreator I would like to prioritize this blog post going out soon this week because I don't want reports to be waiting around before we publish them. Please take the time to review and address the questions I left in the PR 😄 |
|
Lgtm!!! A well-done job, sensei 🙇🏾♂️ |
quetzalliwrites
requested review from
mcturco and
magicmatatjahu
as code owners
Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com>
|
did i do it right? 😄🧐 the blog post itself works fine: https://deploy-preview-1527--asyncapi-website.netlify.app/blog/2023-q1-docs-report
|
|
Ok if y'all agree then I look forward to Thulie merging this week 🔥 |
|
yo @derberg please approve the PR for merging please😊😊 |
There was a problem hiding this comment.
Approving this PR but tbh, I think it won't get merged after @derberg review. @alequetzalli is the codeowner of the MD files in the repo and since she initialized this PR, Github will ask asyncapi-bot-eve to review the PR. So, quite a confusion on this 🤔.
|
Exactly, we are now in a position where this PR has to be merged while removing the approval conditions in the repo settings which will be done by @derberg. My point is should we add @thulieblack as a markdown reviewer for the PRs? cc: @alequetzalli @derberg |
I think yes as Community Manager should be in control of what gets accepted under blog. But this is separate discussion and not a quick fix we should apply here. I can just temporarily merge with admin rights this single PR, just lemme know if you want to publish this blog today and I can do it |
|
The blog needs to be merged today if possible |
|
merged @akshatnema please open separate issue to discuss codeowners file structure |
The 2023 Q1 AsyncAPI Docs Report is an overview of the work we have done in the first quarter of this year: