Skip to content

Conversation

@AceTheCreator
Copy link
Member

@AceTheCreator AceTheCreator commented Jul 30, 2025

This PR is a summary article for the 2024 AsyncAPI Mentorship Program. It captures the journey, achievements, challenges, and future strategic direction of the program, setting the stage for the upcoming "AsyncAPI Maintainership Program.

Summary by CodeRabbit

  • New Features
    • Published a new blog post: "AsyncAPI Mentorship Program 2024 - Wrap Up," offering a detailed retrospective, key achievements, challenges, future plans, and community recognition related to the 2024 mentorship program.

@netlify
Copy link

netlify bot commented Jul 30, 2025

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 75d6df3
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/688cf7f5da23c8000837c8d3
😎 Deploy Preview https://deploy-preview-4292--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 30, 2025

Walkthrough

A new blog post summarizing the 2024 AsyncAPI Mentorship Program has been added. The post reflects on the program's evolution, achievements, challenges, and future directions, and includes recognition for contributors. No changes were made to existing code or public entities.

Changes

Cohort / File(s) Change Summary
Blog Post Addition
markdown/blog/2024-mentorship-program-summary.md
Added a comprehensive retrospective blog post on the 2024 AsyncAPI Mentorship Program, covering its progress, challenges, outcomes, and acknowledgments.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

ready-to-merge

Suggested reviewers

  • derberg
  • thulieblack
  • akshatnema
  • quetzalliwrites
  • anshgoyalevil

Poem

🐇
A new blog post hops into view,
With stories of mentors and mentees too.
Reflections, thanks, and lessons learned,
Toward maintainership, the program turned.
With avatars bright and spirits high,
The AsyncAPI community reaches for the sky!
🌱✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need 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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@codecov
Copy link

codecov bot commented Jul 30, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (e6cbd73) to head (75d6df3).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #4292   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          778       778           
  Branches       144       144           
=========================================
  Hits           778       778           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@asyncapi-bot
Copy link
Contributor

asyncapi-bot commented Jul 30, 2025

⚡️ Lighthouse report for the changes in this PR:

Category Score
🔴 Performance 38
🟢 Accessibility 98
🟢 Best practices 92
🟢 SEO 100
🔴 PWA 33

Lighthouse ran on https://deploy-preview-4292--asyncapi-website.netlify.app/

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
markdown/blog/2024-mentorship-program-summary.md (2)

159-159: Tighten wording & drop “truly amazing” cliché

Consider a crisper sentence:

-And to our inspiring contributors: you journeyed through trials and triumphs, not only concluding the program with stellar results but also crafting truly amazing work.
+To our inspiring contributors: you navigated trials and triumphs, finished with stellar results, and produced outstanding work.

14-14: Remove trailing whitespace in YAML front-matter

Line 14 ends with an extra space after “Preacher”. This shows up in git-diff noise and some linters warn.

-    byline: AsyncAPI Preacher␠
+    byline: AsyncAPI Preacher
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4712109 and 834bfcc.

📒 Files selected for processing (1)
  • markdown/blog/2024-mentorship-program-summary.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: 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.
markdown/blog/2024-mentorship-program-summary.md (1)

Learnt from: iambami
PR: #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.

🪛 LanguageTool
markdown/blog/2024-mentorship-program-summary.md

[style] ~159-~159: Opting for a less wordy alternative here may improve the clarity of your writing.
Context: ... journeyed through trials and triumphs, not only concluding the program with stellar results but also crafting truly amazing work. Your dedication lig...

(NOT_ONLY_ALSO)


[style] ~159-~159: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...stellar results but also crafting truly amazing work. Your dedication lights the way fo...

(AWESOME)

🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2024-mentorship-program-summary.md

202-202: Bare URL used

(MD034, no-bare-urls)


203-203: Blank line inside blockquote

(MD028, no-blanks-blockquote)


204-204: Bare URL used

(MD034, no-bare-urls)

⏰ 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). (3)
  • GitHub Check: Test NodeJS PR - macos-13
  • GitHub Check: Test NodeJS PR - windows-latest
  • GitHub Check: Lighthouse CI
🔇 Additional comments (1)
markdown/blog/2024-mentorship-program-summary.md (1)

3-3: Confirm publication date is correct

Front-matter date is set to 2025-08-01. Double-check this aligns with the actual planned publish date so that the post appears in the right chronological order on the site.

Comment on lines 202 to 204
> Photo by Andrea Piacquadio: https://www.pexels.com/photo/amazed-formal-male-looking-at-laptop-screen-3760809/

> Photo from independent.co.uk : https://www.independent.co.uk/life-style/health-and-families/tired-fatigue-symptoms-reason-help-tips-b2669575.html No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix markdown-lint errors: remove blank line inside blockquote & replace bare URLs with links

markdownlint flags MD028 (blank line) and MD034 (bare URLs). Both will fail CI. Patch:

-> Photo by Andrea Piacquadio: https://www.pexels.com/photo/amazed-formal-male-looking-at-laptop-screen-3760809/
-
-> Photo from independent.co.uk : https://www.independent.co.uk/life-style/health-and-families/tired-fatigue-symptoms-reason-help-tips-b2669575.html
+> Photo by [Andrea Piacquadio](https://www.pexels.com/photo/amazed-formal-male-looking-at-laptop-screen-3760809/)
+> Photo from independent.co.uk: [Tiredness article](https://www.independent.co.uk/life-style/health-and-families/tired-fatigue-symptoms-reason-help-tips-b2669575.html)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
> Photo by Andrea Piacquadio: https://www.pexels.com/photo/amazed-formal-male-looking-at-laptop-screen-3760809/
> Photo from independent.co.uk : https://www.independent.co.uk/life-style/health-and-families/tired-fatigue-symptoms-reason-help-tips-b2669575.html
> Photo by [Andrea Piacquadio](https://www.pexels.com/photo/amazed-formal-male-looking-at-laptop-screen-3760809/)
> Photo from independent.co.uk: [Tiredness article](https://www.independent.co.uk/life-style/health-and-families/tired-fatigue-symptoms-reason-help-tips-b2669575.html)
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

202-202: Bare URL used

(MD034, no-bare-urls)


203-203: Blank line inside blockquote

(MD028, no-blanks-blockquote)


204-204: Bare URL used

(MD034, no-bare-urls)

🤖 Prompt for AI Agents
In markdown/blog/2024-mentorship-program-summary.md around lines 202 to 204,
remove the blank line inside the blockquote to fix the MD028 markdownlint error
and replace the bare URLs with proper markdown links to fix the MD034 error.
Format the URLs as clickable links with descriptive text instead of plain URLs.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
markdown/blog/2024-mentorship-program-summary.md (1)

159-159: Wording nitpick

LanguageTool flags “truly amazing work.” Consider a crisper alternative such as “exceptional work” to keep the tone professional.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 834bfcc and 70850da.

📒 Files selected for processing (1)
  • markdown/blog/2024-mentorship-program-summary.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.
markdown/blog/2024-mentorship-program-summary.md (3)

Learnt from: iambami
PR: #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: akshatnema
PR: #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.

Learnt from: akshatnema
PR: #3262
File: components/navigation/BlogPostItem.tsx:95-119
Timestamp: 2024-10-11T11:32:30.226Z
Learning: In the BlogPostItem component (components/navigation/BlogPostItem.tsx), nesting <a> tags inside the parent Link component leads to hydration issues; therefore, we should avoid nesting <a> tags inside Link components in this component.

🪛 LanguageTool
markdown/blog/2024-mentorship-program-summary.md

[style] ~159-~159: Opting for a less wordy alternative here may improve the clarity of your writing.
Context: ... journeyed through trials and triumphs, not only concluding the program with stellar results but also crafting truly amazing work. Your dedication lig...

(NOT_ONLY_ALSO)


[style] ~159-~159: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...stellar results but also crafting truly amazing work. Your dedication lights the way fo...

(AWESOME)

🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2024-mentorship-program-summary.md

203-203: Bare URL used

(MD034, no-bare-urls)


204-204: Bare URL used

(MD034, no-bare-urls)

⏰ 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). (1)
  • GitHub Check: Test NodeJS PR - windows-latest

Comment on lines +203 to +204
> Photo by Andrea Piacquadio: https://www.pexels.com/photo/amazed-formal-male-looking-at-laptop-screen-3760809/
> Photo from independent.co.uk : https://www.independent.co.uk/life-style/health-and-families/tired-fatigue-symptoms-reason-help-tips-b2669575.html No newline at end of file
Copy link
Contributor

@coderabbitai coderabbitai bot Jul 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix MD034: replace bare URLs with markdown links

markdownlint fails on bare URLs here (MD034). Convert each to a descriptive markdown link, e.g.:

> Photo by [Andrea Piacquadio](https://www.pexels.com/photo/amazed-formal-male-looking-at-laptop-screen-3760809/)

Do the same for the second citation to unblock CI.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

203-203: Bare URL used

(MD034, no-bare-urls)


204-204: Bare URL used

(MD034, no-bare-urls)

🤖 Prompt for AI Agents
In markdown/blog/2024-mentorship-program-summary.md around lines 203 to 204, the
bare URLs violate markdownlint rule MD034. Replace each bare URL with a markdown
link by wrapping the link text in brackets and the URL in parentheses, for
example, change the first line to "Photo by [Andrea
Piacquadio](https://www.pexels.com/photo/amazed-formal-male-looking-at-laptop-screen-3760809/)"
and similarly convert the second citation to a markdown link format.

Copy link
Member

@CBID2 CBID2 Aug 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is something to consider @AceTheCreator.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!

Copy link
Collaborator

@bandantonio bandantonio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AceTheCreator Aside from two minor comments, this is an amazing work! Thank you!


The 2024 cohort brought to light that even our highly capable volunteer mentors, especially those new to the program, aren't always immediately proficient in every aspect of mentorship. We noted with surprise that some initially struggled with critical tasks like defining project goals, setting milestones, and establishing communication frequencies. Without these clear frameworks, evaluating both technical progress and behavioral growth became challenging for us.

Another unexpected development was the unfortunate reality of mentor withdrawals. While we typically anticipate and prepare for mentees dropping out due to personal reasons, a mentor's early departure was unprecedented for us.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[suggestion]: It would be helpful to mention the mentor that ended up leaving and how it impacted the cohort. That way readers can understand why their departure was a shock.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it's necessary to mention who the original mentors were, as they stepped away due to personal reasons that I won’t be disclosing in this article. Their departure didn’t affect the program's success, as we had incredible mentors step in and seamlessly carry things forward.

Copy link
Member

@CBID2 CBID2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @AceTheCreator! :) The blog post is of to a great start! :) I pointed out some typos and added some questions that can help you improve it even more. Keep it up! 👍🏾

@bandantonio
Copy link
Collaborator

@CBID2 Your suggestions are way too formal. Remember, this is a blog post, not an airplane's documentation or instructions. The main goal of a blog post is not just to inform, but also connect with the community, so the writing style should be more casual, friendly, vibrant, and engaging. Each of our community members has their unique writing style and that's great! This is what makes each blog post special even if there is some informality or imperfect word choice.

@AceTheCreator FYI ^^ Please keep the post engaging. I would rather fix grammar-related things, like some of the articles and links and left everything else as is.

@CBID2
Copy link
Member

CBID2 commented Jul 31, 2025

@CBID2 Your suggestions are way too formal. Remember, this is a blog post, not an airplane's documentation or instructions. The main goal of a blog post is not just to inform, but also connect with the community, so the writing style should be more casual, friendly, vibrant, and engaging. Each of our community members has their unique writing style and that's great! This is what makes each blog post special even if there is some informality or imperfect word choice.

@AceTheCreator FYI ^^ Please keep the post engaging. I would rather fix grammar-related things, like some of the articles and links and left everything else as is.

Noted @bandantonio. I'll go through my comments tomorrow and find a way to make them more grammar-focused and how they can be more engaging😊

AceTheCreator and others added 2 commits July 31, 2025 16:19
Co-authored-by: Antonio <bandantonio@users.noreply.github.com>
Co-authored-by: Antonio <bandantonio@users.noreply.github.com>
Copy link
Member

@thulieblack thulieblack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor changes

Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com>
AceTheCreator and others added 7 commits August 1, 2025 09:56
Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com>
Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com>
Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com>
Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com>
Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com>
Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com>
Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com>
@AceTheCreator
Copy link
Member Author

Commited your suggested changes @thulieblack 👍🏾

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (1)
markdown/blog/2024-mentorship-program-summary.md (1)

203-204: Bare URLs still violate markdownlint MD034

markdownlint will keep failing until the two bare URLs inside the block-quote are converted to proper markdown links.
Replace each plain URL with the [text](url) format (e.g., Photo by [Andrea Piacquadio](https://… )).

🧹 Nitpick comments (1)
markdown/blog/2024-mentorship-program-summary.md (1)

34-36: Typo: use “GitHub” instead of “Github”

The brand is capital-H, so the anchor text should read “GitHub Discussion”.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 621e6ce and ff128e2.

📒 Files selected for processing (1)
  • markdown/blog/2024-mentorship-program-summary.md (1 hunks)
🧰 Additional context used
🧠 Learnings (5)
📓 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.
📚 Learning: for asyncapi community spotlight blog posts, the frontmatter date should reflect the actual publicat...
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.

Applied to files:

  • markdown/blog/2024-mentorship-program-summary.md
📚 Learning: when reviewing `scripts/markdown/check-markdown.js`, optimizations should be addressed in separate i...
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.

Applied to files:

  • markdown/blog/2024-mentorship-program-summary.md
📚 Learning: in the `blogpostitem` component (`components/navigation/blogpostitem.tsx`), nesting `` tags insid...
Learnt from: akshatnema
PR: asyncapi/website#3262
File: components/navigation/BlogPostItem.tsx:95-119
Timestamp: 2024-10-11T11:32:30.226Z
Learning: In the `BlogPostItem` component (`components/navigation/BlogPostItem.tsx`), nesting `<a>` tags inside the parent `Link` component leads to hydration issues; therefore, we should avoid nesting `<a>` tags inside `Link` components in this component.

Applied to files:

  • markdown/blog/2024-mentorship-program-summary.md
📚 Learning: in the markdown files for the asyncapi website, avatar image paths should be referenced without the ...
Learnt from: bandantonio
PR: asyncapi/website#3393
File: markdown/blog/2024-Q1-docs-report.md:10-12
Timestamp: 2024-11-13T20:34:18.998Z
Learning: In the markdown files for the AsyncAPI website, avatar image paths should be referenced without the `public` prefix (e.g., use `/img/avatars/...` instead of `/public/img/avatars/...`).

Applied to files:

  • markdown/blog/2024-mentorship-program-summary.md
🪛 LanguageTool
markdown/blog/2024-mentorship-program-summary.md

[style] ~159-~159: Opting for a less wordy alternative here may improve the clarity of your writing.
Context: ... journeyed through trials and triumphs, not only concluding the program with stellar results but also crafting truly amazing work. Your dedication lig...

(NOT_ONLY_ALSO)


[style] ~159-~159: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...stellar results but also crafting truly amazing work. Your dedication lights the way fo...

(AWESOME)

🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2024-mentorship-program-summary.md

203-203: Bare URL used

(MD034, no-bare-urls)


204-204: Bare URL used

(MD034, no-bare-urls)

⏰ 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). (2)
  • GitHub Check: Test NodeJS PR - macos-13
  • GitHub Check: Test NodeJS PR - windows-latest
🔇 Additional comments (1)
markdown/blog/2024-mentorship-program-summary.md (1)

39-44: Verify that images rendered with <Figure> have meaningful alt text

The custom <Figure> component receives src and caption, but no explicit alt.
Please ensure the component internally sets an alt attribute (or uses the caption) so screen-reader users get descriptive text.

Copy link
Member

@thulieblack thulieblack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (1)
markdown/blog/2024-mentorship-program-summary.md (1)

203-204: Bare URLs still violate markdown-lint rules (MD034)
This issue has been flagged in earlier review comments and will fail CI. Replace each raw URL with a markdown link.

🧹 Nitpick comments (2)
markdown/blog/2024-mentorship-program-summary.md (2)

1-4: Verify the front-matter date reflects the actual planned publication date
Previous reviews on the website repo emphasized that the date field should correspond to when the post goes live, not necessarily the cohort year being discussed. Double-check that 2025-08-01T06:00:00+01:00 is indeed the intended publish date.


115-156: Consider serving mentor & contributor avatars from local assets
All avatar URLs point to GitHub’s CDN. Relying on external domains can slow page loads and break offline builds. Hosting copies under /img/avatars/… (as done elsewhere in the site) keeps assets under your control and avoids mixed-content issues if the site is ever served over different protocols.

Also applies to: 161-197

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ff128e2 and 8b4a3e0.

📒 Files selected for processing (1)
  • markdown/blog/2024-mentorship-program-summary.md (1 hunks)
🧰 Additional context used
🧠 Learnings (6)
📓 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.
📚 Learning: for asyncapi community spotlight blog posts, the frontmatter date should reflect the actual publicat...
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.

Applied to files:

  • markdown/blog/2024-mentorship-program-summary.md
📚 Learning: when reviewing `scripts/markdown/check-markdown.js`, optimizations should be addressed in separate i...
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.

Applied to files:

  • markdown/blog/2024-mentorship-program-summary.md
📚 Learning: in the `blogpostitem` component (`components/navigation/blogpostitem.tsx`), nesting `` tags insid...
Learnt from: akshatnema
PR: asyncapi/website#3262
File: components/navigation/BlogPostItem.tsx:95-119
Timestamp: 2024-10-11T11:32:30.226Z
Learning: In the `BlogPostItem` component (`components/navigation/BlogPostItem.tsx`), nesting `<a>` tags inside the parent `Link` component leads to hydration issues; therefore, we should avoid nesting `<a>` tags inside `Link` components in this component.

Applied to files:

  • markdown/blog/2024-mentorship-program-summary.md
📚 Learning: in the markdown files for the asyncapi website, avatar image paths should be referenced without the ...
Learnt from: bandantonio
PR: asyncapi/website#3393
File: markdown/blog/2024-Q1-docs-report.md:10-12
Timestamp: 2024-11-13T20:34:18.998Z
Learning: In the markdown files for the AsyncAPI website, avatar image paths should be referenced without the `public` prefix (e.g., use `/img/avatars/...` instead of `/public/img/avatars/...`).

Applied to files:

  • markdown/blog/2024-mentorship-program-summary.md
📚 Learning: the asyncapi website modularization pr uses promise.allsettled for parallel execution of build tasks...
Learnt from: sagarkori143
PR: asyncapi/website#0
File: :0-0
Timestamp: 2025-06-20T14:47:22.389Z
Learning: The AsyncAPI website modularization PR uses Promise.allSettled for parallel execution of build tasks, which provides better performance and fault isolation compared to sequential execution.

Applied to files:

  • markdown/blog/2024-mentorship-program-summary.md
🪛 LanguageTool
markdown/blog/2024-mentorship-program-summary.md

[style] ~159-~159: Opting for a less wordy alternative here may improve the clarity of your writing.
Context: ... journeyed through trials and triumphs, not only concluding the program with stellar results but also crafting truly amazing work. Your dedication lig...

(NOT_ONLY_ALSO)


[style] ~159-~159: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...stellar results but also crafting truly amazing work. Your dedication lights the way fo...

(AWESOME)

🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2024-mentorship-program-summary.md

203-203: Bare URL used

(MD034, no-bare-urls)


204-204: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (1)
markdown/blog/2024-mentorship-program-summary.md (1)

39-44: Figure component missing explicit alt text
For accessibility, <Figure> should convey meaningful alternative text. The caption helps but many screen-readers still rely on an alt attribute. Confirm that the component internally maps caption to alt; if not, add an alt prop.

Copy link
Member

@sambhavgupta0705 sambhavgupta0705 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

@sambhavgupta0705
Copy link
Member

/rtm

Copy link
Member

@CBID2 CBID2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 😊

@AceTheCreator
Copy link
Member Author

/rtm

@asyncapi-bot asyncapi-bot merged commit 628b2ba into asyncapi:master Aug 1, 2025
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants