chore(blog): add May community spotlight #4111
Conversation
iambami
requested review from
TRohit20,
quetzalliwrites and
thulieblack
as code owners
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
WalkthroughA new markdown blog post has been added featuring an in-depth interview with Aayush, a prominent contributor and leader in the AsyncAPI community. The article documents his journey, contributions, mentorship experiences, and future goals within the project. Changes
Suggested labels
Suggested reviewers
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (4)
markdown/blog/community-spotlight-aayush.md (4)
8-8: Add or remove the emptycoverfield.
Thecover:property is currently blank. Either specify the path to the cover image or remove this field to prevent publishing issues.
17-18: Enhance descriptive language.
Consider replacing “super interesting” with a stronger adjective (e.g., “fascinating” or “captivating”) to improve reader engagement.
65-65: Correct missing space after comma.
There's no space after the comma in “contributors too,open new issues”. Update to “contributors too, open new issues” for proper spacing.🧰 Tools
🪛 LanguageTool
[uncategorized] ~65-~65: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...s. Start helping other contributors too,open new issues, suggest enhancements, fix b...(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)
[style] ~65-~65: ‘Yeah’ is rather colloquial language. To make your writing more formal, re-evaluate if it is necessary in this context.
Context: ...ce to be an SNKP mentee, then a mentor. So yeah, that's the path I suggest for anyone w...(SO_YEAH)
93-93: Use proper heading instead of bold text.
MarkdownLint flagged emphasis used instead of heading (MD036). Convert this line to a heading, for example:- **Have You Ever - AsyncAPI Bingo** + ## Have You Ever - AsyncAPI Bingo🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
93-93: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/community-spotlight-aayush.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/community-spotlight-aayush.md
[style] ~23-~23: Consider using an extreme adjective for ‘interesting’.
Context: ...sh! I saw the map of your journey, it’s super interesting. Your name was even nominated by [Thuli...
(EXTREME_ADJECTIVES)
[grammar] ~24-~24: It seems that an auxiliary verb is missing at the beginning.
Context: ...tart with Google Summer of Code, right? You started as a regular contributor?** ***Aayush:...
(PRP_VB_QUESTION)
[style] ~28-~28: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...Google Summer of Code.* **Bami: That's amazing! Could you give us a quick background a...
(AWESOME)
[style] ~28-~28: If you’re making a request, consider inserting ‘please’ or switching up your phrasing to sound more courteous and respectful.
Context: ...mmer of Code.* **Bami: That's amazing! Could you give us a quick background about yourself, w...
(COULD_YOU_PLEASE)
[style] ~30-~30: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...organizations like Textile and Jenkins. I got into AsyncAPI because I wanted to l...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~30-~30: Consider using an alternative to strengthen your wording.
Context: ... Jenkins. I got into AsyncAPI because I wanted to learn about event-driven architectur...
(WANT_KEEN)
[style] ~30-~30: This phrase is redundant. Consider writing “started”.
Context: ...ven architecture and TypeScript. When I first started, the ecosystem was huge and a bit overw...
(FIRST_BEGAN)
[grammar] ~30-~30: Make sure that a verb is not missing between ‘a’ and ‘bit’. (Ellipsis of a verb is possible in a sentence that uses coordination.)
Context: ...t started, the ecosystem was huge and a bit overwhelming. I decided to begin with the CLI projec...
(DT_NN_VBG)
[style] ~37-~37: ‘out of place’ might be wordy. Consider a shorter alternative.
Context: ...ed basic questions, nobody made me feel out of place. That encouragement kept me going. Also...
(EN_WORDINESS_PREMIUM_OUT_OF_PLACE)
[style] ~53-~53: Consider a different adverb to strengthen your wording.
Context: ...ainer and later a mentor myself. It was always on my checklist to become a mentor and ...
(ALWAYS_CONSTANTLY)
[style] ~57-~57: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...k is exciting, the community support is amazing, and it's fascinating to see so many co...
(AWESOME)
[uncategorized] ~65-~65: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...s. Start helping other contributors too,open new issues, suggest enhancements, fix b...
(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)
[style] ~65-~65: ‘Yeah’ is rather colloquial language. To make your writing more formal, re-evaluate if it is necessary in this context.
Context: ...ce to be an SNKP mentee, then a mentor. So yeah, that's the path I suggest for anyone w...
(SO_YEAH)
[typographical] ~71-~71: Consider adding a comma but only if you want to indicate a pause in casual speech.
Context: .... That really helped.* **Bami: Got it. So now to a lighter question: What’s one m...
(SO_COMMA)
[style] ~73-~73: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...naged to complete it on time. That felt amazing.* **Bami: Nice! If you were to give sh...
(AWESOME)
[style] ~85-~85: Consider using a synonym to be more concise.
Context: ...ub voting automation for TSC elections. Lots of fun projects ahead!* **Bami: Nice! Spe...
(A_LOT_OF)
[typographical] ~96-~96: If specifying a range, consider using an en dash instead of a hyphen.
Context: ...ayush:** No, not the whole night, maybe 5-6 hours but not overnight.* **Bami: Have...
(HYPHEN_TO_EN)
[uncategorized] ~96-~96: A comma might be missing here.
Context: ...h:** No, not the whole night, maybe 5-6 hours but not overnight.* **Bami: Have you e...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[style] ~114-~114: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...-gornicki-a621914/) once reviewed my PR very quickly and I was amazed.* **Bami: Have you ev...
(EN_WEAK_ADJECTIVE)
[uncategorized] ~114-~114: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...21914/) once reviewed my PR very quickly and I was amazed.* **Bami: Have you ever l...
(COMMA_COMPOUND_SENTENCE)
[uncategorized] ~131-~131: The preposition “about” seems more likely in this position.
Context: ... of fun stuff going on, and I’m excited for what's ahead,"* he said. Bami: Awesome...
(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)
[style] ~133-~133: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ..."* he said. Bami: Awesome, you’ve been an amazing guest. Thank you so much for sharing yo...
(AWESOME)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/community-spotlight-aayush.md
93-93: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
⏰ Context from checks skipped due to timeout of 180000ms (2)
- GitHub Check: Pages changed - asyncapi-website
- GitHub Check: Lighthouse CI
🔇 Additional comments (1)
markdown/blog/community-spotlight-aayush.md (1)
1-137: Overall: Engaging community spotlight.
The article is well-structured, informative, and celebrates Aayush’s journey effectively. Once these minor fixes are applied, it’s ready to publish.🧰 Tools
🪛 LanguageTool
[style] ~23-~23: Consider using an extreme adjective for ‘interesting’.
Context: ...sh! I saw the map of your journey, it’s super interesting. Your name was even nominated by [Thuli...(EXTREME_ADJECTIVES)
[grammar] ~24-~24: It seems that an auxiliary verb is missing at the beginning.
Context: ...tart with Google Summer of Code, right? You started as a regular contributor?** ***Aayush:...(PRP_VB_QUESTION)
[style] ~28-~28: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...Google Summer of Code.* **Bami: That's amazing! Could you give us a quick background a...(AWESOME)
[style] ~28-~28: If you’re making a request, consider inserting ‘please’ or switching up your phrasing to sound more courteous and respectful.
Context: ...mmer of Code.* **Bami: That's amazing! Could you give us a quick background about yourself, w...(COULD_YOU_PLEASE)
[style] ~30-~30: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...organizations like Textile and Jenkins. I got into AsyncAPI because I wanted to l...(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~30-~30: Consider using an alternative to strengthen your wording.
Context: ... Jenkins. I got into AsyncAPI because I wanted to learn about event-driven architectur...(WANT_KEEN)
[style] ~30-~30: This phrase is redundant. Consider writing “started”.
Context: ...ven architecture and TypeScript. When I first started, the ecosystem was huge and a bit overw...(FIRST_BEGAN)
[grammar] ~30-~30: Make sure that a verb is not missing between ‘a’ and ‘bit’. (Ellipsis of a verb is possible in a sentence that uses coordination.)
Context: ...t started, the ecosystem was huge and a bit overwhelming. I decided to begin with the CLI projec...(DT_NN_VBG)
[style] ~37-~37: ‘out of place’ might be wordy. Consider a shorter alternative.
Context: ...ed basic questions, nobody made me feel out of place. That encouragement kept me going. Also...(EN_WORDINESS_PREMIUM_OUT_OF_PLACE)
[style] ~53-~53: Consider a different adverb to strengthen your wording.
Context: ...ainer and later a mentor myself. It was always on my checklist to become a mentor and ...(ALWAYS_CONSTANTLY)
[style] ~57-~57: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...k is exciting, the community support is amazing, and it's fascinating to see so many co...(AWESOME)
[uncategorized] ~65-~65: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...s. Start helping other contributors too,open new issues, suggest enhancements, fix b...(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)
[style] ~65-~65: ‘Yeah’ is rather colloquial language. To make your writing more formal, re-evaluate if it is necessary in this context.
Context: ...ce to be an SNKP mentee, then a mentor. So yeah, that's the path I suggest for anyone w...(SO_YEAH)
[typographical] ~71-~71: Consider adding a comma but only if you want to indicate a pause in casual speech.
Context: .... That really helped.* **Bami: Got it. So now to a lighter question: What’s one m...(SO_COMMA)
[style] ~73-~73: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...naged to complete it on time. That felt amazing.* **Bami: Nice! If you were to give sh...(AWESOME)
[style] ~85-~85: Consider using a synonym to be more concise.
Context: ...ub voting automation for TSC elections. Lots of fun projects ahead!* **Bami: Nice! Spe...(A_LOT_OF)
[typographical] ~96-~96: If specifying a range, consider using an en dash instead of a hyphen.
Context: ...ayush:** No, not the whole night, maybe 5-6 hours but not overnight.* **Bami: Have...(HYPHEN_TO_EN)
[uncategorized] ~96-~96: A comma might be missing here.
Context: ...h:** No, not the whole night, maybe 5-6 hours but not overnight.* **Bami: Have you e...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[style] ~114-~114: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...-gornicki-a621914/) once reviewed my PR very quickly and I was amazed.* **Bami: Have you ev...(EN_WEAK_ADJECTIVE)
[uncategorized] ~114-~114: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...21914/) once reviewed my PR very quickly and I was amazed.* **Bami: Have you ever l...(COMMA_COMPOUND_SENTENCE)
[uncategorized] ~131-~131: The preposition “about” seems more likely in this position.
Context: ... of fun stuff going on, and I’m excited for what's ahead,"* he said. Bami: Awesome...(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)
[style] ~133-~133: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ..."* he said. Bami: Awesome, you’ve been an amazing guest. Thank you so much for sharing yo...(AWESOME)
🪛 markdownlint-cli2 (0.17.2)
93-93: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4111 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 22 22
Lines 778 778
Branches 144 144
=========================================
Hits 778 778 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (2)
markdown/blog/community-spotlight-aayush.md (2)
3-3:⚠️ Potential issueCorrect the frontmatter publish date for the May spotlight.
The frontmatter date is set to2025-04-28T06:00:00+01:00but should reflect the May release (e.g.,2025-05-28T06:00:00+01:00).
24-24:⚠️ Potential issueFix malformed Markdown link for Thulie’s profile.
The link contains an extra]before the closing parenthesis. Apply this diff to correct it:- **Bami: Nice to meet you, Aayush! I saw the map of your journey, it’s super interesting. Your name was even nominated by [Thulie](https://www.linkedin.com/in/v-thulisile-sibanda/]) initially. + **Bami: Nice to meet you, Aayush! I saw the map of your journey, it’s super interesting. Your name was even nominated by [Thulie](https://www.linkedin.com/in/v-thulisile-sibanda/) initially.🧰 Tools
🪛 LanguageTool
[style] ~24-~24: Consider using an extreme adjective for ‘interesting’.
Context: ...sh! I saw the map of your journey, it’s super interesting. Your name was even nominated by [Thuli...(EXTREME_ADJECTIVES)
🧹 Nitpick comments (2)
markdown/blog/community-spotlight-aayush.md (2)
9-9: Provide or remove the emptycoverfield.
Thecover:key is empty. To avoid broken image links or build warnings, either supply a valid cover image path or remove thecoverfield if not needed.
24-24: Use a stronger adjective.
The phrase “super interesting” is generic. Consider a more descriptive adjective (e.g., “fascinating” or “captivating”) to better capture Aayush’s journey.🧰 Tools
🪛 LanguageTool
[style] ~24-~24: Consider using an extreme adjective for ‘interesting’.
Context: ...sh! I saw the map of your journey, it’s super interesting. Your name was even nominated by [Thuli...(EXTREME_ADJECTIVES)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting
📒 Files selected for processing (1)
markdown/blog/community-spotlight-aayush.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/community-spotlight-aayush.md
[style] ~24-~24: Consider using an extreme adjective for ‘interesting’.
Context: ...sh! I saw the map of your journey, it’s super interesting. Your name was even nominated by [Thuli...
(EXTREME_ADJECTIVES)
[grammar] ~25-~25: It seems that an auxiliary verb is missing at the beginning.
Context: ...tart with Google Summer of Code, right? You started as a regular contributor?** ***Aayush:...
(PRP_VB_QUESTION)
[style] ~29-~29: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...Google Summer of Code.* **Bami: That's amazing! Could you give us a quick background a...
(AWESOME)
[style] ~29-~29: If you’re making a request, consider inserting ‘please’ or switching up your phrasing to sound more courteous and respectful.
Context: ...mmer of Code.* **Bami: That's amazing! Could you give us a quick background about yourself, w...
(COULD_YOU_PLEASE)
[style] ~31-~31: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...organizations like Textile and Jenkins. I got into AsyncAPI because I wanted to l...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~31-~31: Consider using an alternative to strengthen your wording.
Context: ... Jenkins. I got into AsyncAPI because I wanted to learn about event-driven architectur...
(WANT_KEEN)
[style] ~31-~31: This phrase is redundant. Consider writing “started”.
Context: ...ven architecture and TypeScript. When I first started, the ecosystem was huge and a bit overw...
(FIRST_BEGAN)
[grammar] ~31-~31: Make sure that a verb is not missing between ‘a’ and ‘bit’. (Ellipsis of a verb is possible in a sentence that uses coordination.)
Context: ...t started, the ecosystem was huge and a bit overwhelming. I decided to begin with the CLI projec...
(DT_NN_VBG)
[style] ~38-~38: ‘out of place’ might be wordy. Consider a shorter alternative.
Context: ...ed basic questions, nobody made me feel out of place. That encouragement kept me going. Also...
(EN_WORDINESS_PREMIUM_OUT_OF_PLACE)
[style] ~54-~54: Consider a different adverb to strengthen your wording.
Context: ...ainer and later a mentor myself. It was always on my checklist to become a mentor and ...
(ALWAYS_CONSTANTLY)
[style] ~58-~58: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...k is exciting, the community support is amazing, and it's fascinating to see so many co...
(AWESOME)
[uncategorized] ~66-~66: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...s. Start helping other contributors too,open new issues, suggest enhancements, fix b...
(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)
[style] ~66-~66: ‘Yeah’ is rather colloquial language. To make your writing more formal, re-evaluate if it is necessary in this context.
Context: ...ce to be an SNKP mentee, then a mentor. So yeah, that's the path I suggest for anyone w...
(SO_YEAH)
[typographical] ~72-~72: Consider adding a comma but only if you want to indicate a pause in casual speech.
Context: .... That really helped.* **Bami: Got it. So now to a lighter question: What’s one m...
(SO_COMMA)
[style] ~74-~74: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...naged to complete it on time. That felt amazing.* **Bami: Nice! If you were to give sh...
(AWESOME)
[style] ~86-~86: Consider using a synonym to be more concise.
Context: ...ub voting automation for TSC elections. Lots of fun projects ahead!* **Bami: Nice! Spe...
(A_LOT_OF)
[typographical] ~97-~97: If specifying a range, consider using an en dash instead of a hyphen.
Context: ...ayush:** No, not the whole night, maybe 5-6 hours but not overnight.* **Bami: Have...
(HYPHEN_TO_EN)
[uncategorized] ~97-~97: A comma might be missing here.
Context: ...h:** No, not the whole night, maybe 5-6 hours but not overnight.* **Bami: Have you e...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[style] ~115-~115: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...-gornicki-a621914/) once reviewed my PR very quickly and I was amazed.* **Bami: Have you ev...
(EN_WEAK_ADJECTIVE)
[uncategorized] ~115-~115: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...21914/) once reviewed my PR very quickly and I was amazed.* **Bami: Have you ever l...
(COMMA_COMPOUND_SENTENCE)
[uncategorized] ~132-~132: The preposition “about” seems more likely in this position.
Context: ... of fun stuff going on, and I’m excited for what's ahead,"* he said. Bami: Awesome...
(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)
[style] ~134-~134: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ..."* he said. Bami: Awesome, you’ve been an amazing guest. Thank you so much for sharing yo...
(AWESOME)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/community-spotlight-aayush.md
94-94: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
⏰ Context from checks skipped due to timeout of 180000ms (1)
- GitHub Check: Lighthouse CI
iambami
requested review from
Mayaleeeee,
anshgoyalevil,
asyncapi-bot-eve,
derberg and
sambhavgupta0705
as code owners
akshatnema
changed the title
akshatnema
changed the title
|
@TRohit20 please your review |
|
Hey @TRohit20 All names corrected. Can this be published tomorrow? cc @akshatnema |
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (1)
markdown/blog/community-spotlight-aayush.md (1)
24-26: Interviewer label still missing.
This question line is the only one without the “Bami:” prefix, breaking the established Q/A pattern and earlier review feedback.
🧹 Nitpick comments (1)
markdown/blog/community-spotlight-aayush.md (1)
88-91: Minor punctuation/flow issue.
The sentence “...just by pushing a PR I had to test everything from my private repo.” is missing a pause. Consider splitting or adding a comma after “PR” to improve readability.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/community-spotlight-aayush.md(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: asyncapi-bot
PR: asyncapi/website#0
File: :0-0
Timestamp: 2025-02-18T12:07:42.211Z
Learning: The following PR commands are supported in the asyncapi/website repository:
- `/please-take-a-look` or `/ptal`: Requests attention from reviewers who haven't reviewed the PR
- `/ready-to-merge` or `/rtm`: Triggers automerge when all conditions are met
- `/do-not-merge` or `/dnm`: Blocks automerge even if all conditions are met
- `/autoupdate` or `/au`: Adds autoupdate label to keep PR in sync with target branch
- `/update` or `/u`: One-time update of PR with latest changes from target branch
Learnt from: akshatnema
PR: asyncapi/website#3265
File: tests/fixtures/toolsObjectData.js:51-52
Timestamp: 2024-10-09T17:35:36.557Z
Learning: When reviewing code in the 'asyncapi/website' repository, akshatnema prefers that I do not provide committable code suggestions.
Learnt from: iambami
PR: asyncapi/website#4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
Learnt from: Siddhant-Pragyan-Sinha
PR: asyncapi/website#4074
File: markdown/blog/open-nest.md:11-12
Timestamp: 2025-04-28T01:13:59.084Z
Learning: For AsyncAPI blog posts, author photo filenames don't necessarily need to match the author's official name, as some authors may use pen names or nicknames (e.g., Aishat Muibudeen using "maya_picture.webp" for her avatar).
markdown/blog/community-spotlight-aayush.md (5)
Learnt from: iambami
PR: asyncapi/website#4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
Learnt from: Siddhant-Pragyan-Sinha
PR: asyncapi/website#4074
File: markdown/blog/open-nest.md:11-12
Timestamp: 2025-04-28T01:13:59.084Z
Learning: For AsyncAPI blog posts, author photo filenames don't necessarily need to match the author's official name, as some authors may use pen names or nicknames (e.g., Aishat Muibudeen using "maya_picture.webp" for her avatar).
Learnt from: akshatnema
PR: asyncapi/website#3265
File: tests/fixtures/toolsObjectData.js:51-52
Timestamp: 2024-10-09T17:35:36.557Z
Learning: When reviewing code in the 'asyncapi/website' repository, akshatnema prefers that I do not provide committable code suggestions.
Learnt from: akshatnema
PR: asyncapi/website#3262
File: components/Avatar.tsx:35-44
Timestamp: 2024-10-11T10:46:58.882Z
Learning: In Next.js, when avoiding nested `<a>` tags due to hydration issues, use accessible non-link elements like `<button>` or `<span>` with appropriate roles, `tabIndex`, and event handlers to maintain accessibility and SEO.
Learnt from: akshatnema
PR: asyncapi/website#3378
File: scripts/markdown/check-markdown.js:1-1
Timestamp: 2024-11-25T18:34:51.303Z
Learning: When reviewing `scripts/markdown/check-markdown.js`, optimizations should be addressed in separate issues and not included in the current pull request.
🪛 LanguageTool
markdown/blog/community-spotlight-aayush.md
[style] ~24-~24: Consider using an extreme adjective for ‘interesting’.
Context: ...sh! I saw the map of your journey, it’s super interesting. Your name was even nominated by [V. Th...
(EXTREME_ADJECTIVES)
[style] ~29-~29: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...Google Summer of Code.* **Bami: That's amazing! Could you give us a quick background a...
(AWESOME)
[style] ~29-~29: If you’re making a request, consider inserting ‘please’ or switching up your phrasing to sound more courteous and respectful.
Context: ...mmer of Code.* **Bami: That's amazing! Could you give us a quick background about yourself, w...
(COULD_YOU_PLEASE)
[style] ~31-~31: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...and Jenkins. I got into AsyncAPI because I wanted to l...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~31-~31: Consider using an alternative to strengthen your wording.
Context: ...ins.io/). I got into AsyncAPI because I wanted to learn about event-driven architectur...
(WANT_KEEN)
[style] ~31-~31: This phrase is redundant. Consider writing “started”.
Context: ...ven architecture and TypeScript. When I first started, the ecosystem was huge and a bit overw...
(FIRST_BEGAN)
[style] ~38-~38: ‘out of place’ might be wordy. Consider a shorter alternative.
Context: ...ed basic questions, nobody made me feel out of place. That encouragement kept me going. Also...
(EN_WORDINESS_PREMIUM_OUT_OF_PLACE)
[style] ~54-~54: Consider a different adverb to strengthen your wording.
Context: ...ainer and later a mentor myself. It was always on my checklist to become a mentor and ...
(ALWAYS_CONSTANTLY)
[style] ~58-~58: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...k is exciting, the community support is amazing, and it's fascinating to see so many co...
(AWESOME)
[style] ~86-~86: Consider using a synonym to be more concise.
Context: ...ub voting automation for TSC elections. Lots of fun projects ahead!* **Bami: Nice! Spe...
(A_LOT_OF)
[style] ~115-~115: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...-gornicki-a621914/) once reviewed my PR very quickly, and I was amazed.* **Bami: Have you e...
(EN_WEAK_ADJECTIVE)
[style] ~134-~134: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ..."* he said. Bami: Awesome, you’ve been an amazing guest. Thank you so much for sharing yo...
(AWESOME)
⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
- GitHub Check: Redirect rules - asyncapi-website
- GitHub Check: Header rules - asyncapi-website
- GitHub Check: Pages changed - asyncapi-website
- GitHub Check: Test NodeJS PR - ubuntu-latest
- GitHub Check: Test NodeJS PR - macos-13
- GitHub Check: Test NodeJS PR - windows-latest
- GitHub Check: Lighthouse CI
🔇 Additional comments (4)
markdown/blog/community-spotlight-aayush.md (4)
1-16: Confirm publish date & missingcoverAlt.
The front-matter says this post will publish on 2025-07-11, yet the PR title still refers to the “May” spotlight. If July is the real go-live date that’s fine, but please double-check with the comms calendar.
While you’re here, consider addingcoverAlt:for accessibility – most recent posts include it.
11-14: Verify author LinkedIn URL.
The slugatinuke-Bami-kayode-5b838b1b7differs from the variant used elsewhere (atinuke-oluwabamikemi-kayode-5b838b1b7). Make sure the link actually resolves and that we use a single canonical profile.
78-103: Inconsistent spelling of “Samir/Sameer”.
Line 78 lists “Samir Amzani”, while line 103 references “Sameer”. Please confirm whether these refer to the same contributor and use a single, correct spelling.
9-9: Ensure cover image is present in repository.
/img/posts/marketing-images/aayush-spotlight.webpshould exist in the repo before merge to avoid 404s.
|
Hey @TRohit20 @akshatnema Can you give your final review, please? |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-4111--asyncapi-website.netlify.app/ |
TRohit20
left a comment
TRohit20
left a comment
There was a problem hiding this comment.
LGTM, Great work, Bami. Thank you !
|
@TRohit20 next time please don't use the squash and merge button but /rtm. Thanks |
9 participants
Hey folks,
It's the community spotlight story again 🤗
Kindly go through it and add your suggestions. I will be working on the suggestions.
@TRohit20 @AayushSaini101 @thulieblack
Summary by CodeRabbit