docs(community): update latest community documentation

[asyncapi-bot]

Updated community documentation is available and this PR introduces update to community folder on the website

Summary by CodeRabbit

Release Notes

• Documentation
  • Reorganized mentorship program documentation with improved structure and navigation
  • Added new program insights dashboard featuring retention metrics, mentor engagement data, and mentee-to-mentor pipeline tracking
  • Enhanced program overviews with leadership information, program goals, and statistics sections
  • Updated mentorship program pages with expanded timelines, FAQs, and contact information
  • Consolidated program content for improved clarity and accessibility

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	9a88031
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/690b28b2e2f11600087b36b5
😎 Deploy Preview	https://deploy-preview-4539--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle 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]

Walkthrough

Documentation reorganization for AsyncAPI mentorship programs: deletion of year-specific README files (2022–2024), restructuring project ideas pages with expanded metadata and sections, complete rewrite of main mentorship README with new governance and leadership sections, addition of new insights page containing metrics and program data, and updates to program index and GSoC pages.

Changes

Cohort / File(s)	Change Summary
Deleted Year-Specific README Files asyncapi-mentoring-initiatives.md, asyncapi-mentorship-2022-README.md, asyncapi-mentorship-2023-README.md, asyncapi-mentorship-2024-README.md, summerofcode-2023-README.md, summerofcode-2024-README.md	Removed entire documentation pages containing program timelines, status headers, and accepted projects tables for specific mentorship years.
Enhanced Project Ideas Pages asyncapi-mentorship-2022-project-ideas.md, asyncapi-mentorship-2023-project-ideas.md, asyncapi-mentorship-2024-project-ideas.md, summerofcode-2024-asyncapi-gsoc-ideas-page.md	Expanded and restructured project listings from draft/table format to comprehensive narrative format with consistent metadata (outcome, skills, difficulty, mentor/mentee, length), added status badges, Timeline sections, and FAQ sections.
New Documentation Files summerofcode-2023-asyncapi-gsoc-ideas-page.md, insights.md	Added new GSoC 2023 ideas page and comprehensive insights page containing mentee retention metrics, program performance data, mentor engagement statistics, and mentee-to-mentor pipeline analysis.
Main Mentorship Documentation Rewrites asyncapi-mentorship-README.md, index.md	Replaced year-based archival data with current Program Goals, Leadership, Statistics, and Key Definitions sections; restructured index from single paragraph to multi-section hub with support resources, available programs table, and historical impact data.
Updated GSoC Pages summerofcode-2025-asyncapi-gsoc-ideas-page.md, summerofcode-README.md	Added program status banners and final-project checkmarks to 2025 GSoC page; updated mentor listings and project metadata. Minor heading level and formatting adjustments to SummerOfCode README.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

• Areas requiring extra attention:
  • Verification of content accuracy during the restructuring and deletion of year-specific documentation—confirm no critical historical data was unintentionally lost
  • Cross-reference checks between the new insights.md metrics and the restructured project ideas pages to ensure consistency
  • Validation of all mentor/mentee names and links updated across multiple project ideas files
  • Confirmation that the reorganization of main README sections preserves all necessary program governance information and eligibility requirements
  • Review of the new index page structure to ensure proper discoverability of all program information

Suggested reviewers

• thulieblack
• TRohit20
• derberg
• bandantonio
• akshatnema
• asyncapi-bot-eve

Poem

🐰 Hopping through docs with care and grace,
Mentorship tales find their rightful place,
Old pages tucked, new insights bloom,
Leadership shines in each bright room,
Projects polished, future bright,
A warren of wisdom—oh, what a sight! ✨

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the primary change: updating community documentation. It captures the main scope of the PR which involves restructuring and enhancing the mentorship program documentation across multiple files.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-community-docs-ddf3ba0e7c42d45bbf4ee2d61946fc82f28202ec

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (8688dc0) to head (9a88031).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4539   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          780       780           
  Branches       144       144           
=========================================
  Hits           780       780           

☔ 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]

⚡️ Lighthouse report for the changes in this PR:

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

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

[coderabbitai]

Actionable comments posted: 9

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

markdown/docs/community/050-mentorship-program/summerofcode-2024-asyncapi-gsoc-ideas-page.md (1)

1-52: Handles exist, but we need to verify the name-handle pairings and mentor-mentee relationships against official GSoC 2024 records.

Incorrect mentee GitHub handle identified for Project 4.

The document lists Nikhil Chaudhari with GitHub handle @nikhil-3112 for the MermaidJS Diagrams project. However, search results indicate the actual GitHub handle for the mentee working on this project is @nikhilkalburgi, not @nikhil-3112. Update the handle accordingly.

All other mentee names and GitHub handles verified as accurate:

• Esther Xiao (@FelicixAwe) for Spectral autofix
• Vishvamsinh Vaghela (@vishvamsinh28) for Script Stability Enhancement
• Mintu Gogoi (@Gmin2) and Yuan Yuan (@lmgyuan) for AsyncAPI Generator maintainership
• All handles confirmed to exist and mentor-mentee pairings align with AsyncAPI GSoC 2024 program records.

🧹 Nitpick comments (3)

markdown/docs/community/050-mentorship-program/summerofcode-2023-asyncapi-gsoc-ideas-page.md (1)

80-80: Minor grammar suggestion: replace "similar way as" with "similarly".

Line 80 uses "in a similar way as," which is slightly wordy. Consider simplifying to "similarly" for conciseness, as suggested by static analysis.

Apply this diff:

-Create an endpoint `help/{command}` to return instructions of given command to the user. For example, `help/generate` should return available parameters such as available templates etc. The endpoint should be done in a similar way as in our main CLI, so the main help endpoint should return all available endpoints and particular ones like `help/generate` should return details about given command.
+Create an endpoint `help/{command}` to return instructions of given command to the user. For example, `help/generate` should return available parameters such as available templates etc. The endpoint should be done similarly to our main CLI, so the main help endpoint should return all available endpoints and particular ones like `help/generate` should return details about given command.

markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2023-project-ideas.md (1)

122-130: Add mentor information to project 11.

Project 11 (lines 122-130) lists only mentors but has no mentee information. Verify whether this project was completed without a mentee assignment or if mentee data is missing.

markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2024-project-ideas.md (1)

100-148: Clarify mentee assignment status for projects 9-13.

Projects 9-13 (lines 100-148) list only mentor(s) without mentee information. Determine whether:

1. These projects were not filled during this mentorship cycle
2. Mentee information is pending/incomplete
3. These are open-ended projects waiting for assignment

This should be clearly documented or noted in the file to avoid confusion for readers.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8688dc0 and 9a88031.

📒 Files selected for processing (16)

• markdown/docs/community/050-mentorship-program/asyncapi-mentoring-initiatives.md (0 hunks)
• markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2022-README.md (0 hunks)
• markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2022-project-ideas.md (1 hunks)
• markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2023-README.md (0 hunks)
• markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2023-project-ideas.md (1 hunks)
• markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2024-README.md (0 hunks)
• markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2024-project-ideas.md (1 hunks)
• markdown/docs/community/050-mentorship-program/asyncapi-mentorship-README.md (1 hunks)
• markdown/docs/community/050-mentorship-program/index.md (1 hunks)
• markdown/docs/community/050-mentorship-program/insights.md (1 hunks)
• markdown/docs/community/050-mentorship-program/summerofcode-2023-README.md (0 hunks)
• markdown/docs/community/050-mentorship-program/summerofcode-2023-asyncapi-gsoc-ideas-page.md (1 hunks)
• markdown/docs/community/050-mentorship-program/summerofcode-2024-README.md (0 hunks)
• markdown/docs/community/050-mentorship-program/summerofcode-2024-asyncapi-gsoc-ideas-page.md (1 hunks)
• markdown/docs/community/050-mentorship-program/summerofcode-2025-asyncapi-gsoc-ideas-page.md (2 hunks)
• markdown/docs/community/050-mentorship-program/summerofcode-README.md (2 hunks)

💤 Files with no reviewable changes (6)

• markdown/docs/community/050-mentorship-program/summerofcode-2023-README.md
• markdown/docs/community/050-mentorship-program/summerofcode-2024-README.md
• markdown/docs/community/050-mentorship-program/asyncapi-mentoring-initiatives.md
• markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2023-README.md
• markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2024-README.md
• markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2022-README.md

🧰 Additional context used

🪛 LanguageTool

markdown/docs/community/050-mentorship-program/summerofcode-2025-asyncapi-gsoc-ideas-page.md

[uncategorized] ~56-~56: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ensions, Spectral Linting, Testing, and Open Source Contribution. - 🧩 Difficulty: Medi...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[uncategorized] ~76-~76: The official name of this software platform is spelled with a capital “H”.
Context: ... Required:** Typescript, Node js, Jest, Github actions - 🧩 Difficulty: Medium/Har...

(GITHUB)

---

[uncategorized] ~86-~86: The official name of this software platform is spelled with a capital “H”.
Context: ...ed:** Typescript, Node js, E2E Testing, Github actions - 🧩 Difficulty: Medium/Har...

(GITHUB)

markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2023-project-ideas.md

[style] ~80-~80: To elevate your writing, try using a synonym here.
Context: ...ation, and deployment. Currently, it is hard to get started with Glee as a new user....

(HARD_TO)

---

[grammar] ~206-~206: Use a hyphen to join words.
Context: ...tch (or update existing ones) using drag and drop blocks in Studio, similar to th...

(QB_NEW_EN_HYPHEN)

---

[grammar] ~206-~206: Use a hyphen to join words.
Context: ...(or update existing ones) using drag and drop blocks in Studio, similar to the cu...

(QB_NEW_EN_HYPHEN)

markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2024-project-ideas.md

[grammar] ~78-~78: Ensure spelling is correct
Context: ...Length:** 350 Hours ## 7) [Integrating EDAVisualiser Application Focus View into VS Code Asy...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

---

[grammar] ~80-~80: Ensure spelling is correct
Context: ...s. The project involves integrating the EDAVisualiser library, implementing a configuration s...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

markdown/docs/community/050-mentorship-program/summerofcode-2023-asyncapi-gsoc-ideas-page.md

[style] ~80-~80: Consider replacing this phrase with the adverb “similarly” to avoid wordiness.
Context: ...plates etc. The endpoint should be done in a similar way as in our main CLI, so the main help en...

(IN_A_X_MANNER)

markdown/docs/community/050-mentorship-program/summerofcode-2024-asyncapi-gsoc-ideas-page.md

[uncategorized] ~91-~91: The official name of this software platform is spelled with a capital “H”.
Context: ...(https://github.com/14Richa)** in our .github, ...

(GITHUB)

🪛 markdownlint-cli2 (0.18.1)

markdown/docs/community/050-mentorship-program/index.md

50-50: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

⏰ 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: Automerge PR autoapproved by a bot
• GitHub Check: Redirect rules - asyncapi-website
• GitHub Check: Header rules - asyncapi-website
• GitHub Check: Pages changed - asyncapi-website
• GitHub Check: Lighthouse CI
• GitHub Check: Test NodeJS PR - macos-13
• GitHub Check: Test NodeJS PR - windows-latest

🔇 Additional comments (10)

markdown/docs/community/050-mentorship-program/summerofcode-2025-asyncapi-gsoc-ideas-page.md (2)

1-100: Documentation update looks good overall.

The restructured GSoC 2025 ideas page effectively incorporates program status indicators, final-project checkmarks, mentor/mentee pairings, and consistent formatting across all nine projects. The changes align well with the pattern established in prior year documentation. Once the minor style and grammatical issues noted above are corrected, this will be ready.

---

98-99: The mentor name has been verified against the GitHub profile for user devilkiller-ag. The API confirms the name is correctly listed as "Ashmit JaiSarita Gupta" in the document, matching the GitHub profile exactly. No correction is needed.

Likely an incorrect or invalid review comment.

markdown/docs/community/050-mentorship-program/summerofcode-README.md (1)

8-8: Heading normalization looks good.

The change from a smaller heading to ## Introduction improves markdown structure consistency. No issues identified.

markdown/docs/community/050-mentorship-program/index.md (1)

50-50: Note placeholder or citation needed for total participants figure.

Line 50 states "Total participants across all programs: 136+" but this figure should be verifiable from the "Program Impact by Year" table above. Verify that this total is accurate and consider adding a note explaining how it was calculated (e.g., sum of column totals).

markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2022-project-ideas.md (1)

10-12: Clarify or update TSC membership note.

Line 12 contains a note about "7 mentors from TSC and 2 mentees from the TSC, giving us 23 remaining TSC members able to vote." This appears to be historical context from 2022. Confirm whether this note is still relevant or if it should be updated/removed for the current documentation.

markdown/docs/community/050-mentorship-program/asyncapi-mentorship-README.md (2)

32-37: Update program cycles table with 2025 information if available.

The "Program Cycles and Archive" table (lines 32-37) currently lists 2022-2024 with 2024 marked as "Completed." If the 2025 program is active or in progress, consider adding it to this table with the current status and links to project ideas.

---

203-203: GitHub Discussions link is valid and accessible.

The URL https://github.com/asyncapi/community/discussions returns HTTP 200, confirming it is correct and accessible. However, verification that the discussions are actively monitored for mentorship-related issues requires manual inspection of the discussions forum and community management practices, which cannot be determined from URL validation alone.

markdown/docs/community/050-mentorship-program/summerofcode-2024-asyncapi-gsoc-ideas-page.md (1)

89-101: Link verification successful, but process monitoring requires manual confirmation.

The external reference at line 101 is valid: the GitHub discussions link resolves with HTTP/2 200. However, confirming that the team actively monitors and processes issues with the "GSoC 2024" prefix requires manual verification of your team's issue tracking workflows—this cannot be validated through automated means.

markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2023-project-ideas.md (1)

78-86: No issues found—multi-mentor projects are consistently formatted.

Verification confirms that all 16 multi-mentor projects across mentorship program pages use uniform formatting with pipe-separated mentors, followed by clearly designated mentee assignments on the next line. The structure is consistent across 2022, 2023, 2024, and GSoC pages, with no ambiguity in mentor-to-mentee relationships.

markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2024-project-ideas.md (1)

78-87: No issues found—spelling and mentee assignment are correct.

The AsyncAPI project uses "EDAVisualiser" (with an "s"), which is exactly what appears in lines 78–87. The mentee assignment is also already present: Milan D Vijay (@ibishal) is listed on line 87. The LanguageTool suggestion was a false positive.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Verify 2025 mentorship program documentation exists.

Line 79 references ./asyncapi-mentorship-2025-README as the Ideas List for current applications. Ensure this file exists in the repository. If the 2025 program is not yet launched or documented, this reference may need to be updated or conditionally shown based on program status.

---

🏁 Script executed:

#!/bin/bash
# Check if 2025 mentorship README exists
if [ -f "markdown/docs/community/050-mentorship-program/asyncapi-mentorship-2025-README.md" ]; then
  echo "✓ File exists: asyncapi-mentorship-2025-README.md"
else
  echo "✗ File not found: asyncapi-mentorship-2025-README.md"
  echo "Checking for alternative naming patterns..."
  find markdown/docs/community/050-mentorship-program -name "*2025*" -type f
fi

Length of output: 189

---

Fix broken link reference at line 79 for 2025 Ideas List.

The 2025 GSoC project ideas were published in the community repository under the mentorship directory, but the specific file ./asyncapi-mentorship-2025-README referenced at line 79 does not exist in the repository. The only related 2025 file found is summerofcode-2025-asyncapi-gsoc-ideas-page.md.

Update line 79 to reference the correct file path, or if a dedicated 2025 AsyncAPI Mentorship README is planned but not yet created, clarify whether the link should point to the GSoC ideas page instead or be marked as coming soon.

🤖 Prompt for AI Agents

In markdown/docs/community/050-mentorship-program/asyncapi-mentorship-README.md
around lines 78 to 82, the link to the 2025 Ideas List points to a non-existent
file (`./asyncapi-mentorship-2025-README`); update that link to the actual file
`./summerofcode-2025-asyncapi-gsoc-ideas-page.md` (or, if a dedicated mentorship
README will be created later, replace the link text with a “coming soon” note
and remove the broken href) so the reference resolves correctly.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Verify all referenced program documentation files exist.

The "Available Programs" table (lines 25-30) references several program documentation pages including:

• ./seasonofdocs-2023-README (line 27)
• ./winterofcode-2023-README (line 28)
• ./openforce/README (line 29)
• ./hacktoberfest/README (line 30)

Ensure these files exist in the repository and that the links are not broken. If any of these programs are not currently active or documented, consider removing them from this hub page or marking them as archived.

---

🏁 Script executed:

#!/bin/bash
# Check if all referenced program files exist
files=(
  "markdown/docs/community/050-mentorship-program/seasonofdocs-2023-README.md"
  "markdown/docs/community/050-mentorship-program/winterofcode-2023-README.md"
  "markdown/docs/community/050-mentorship-program/openforce/README.md"
  "markdown/docs/community/050-mentorship-program/hacktoberfest/README.md"
  "markdown/docs/community/050-mentorship-program/asyncapi-mentorship-README.md"
  "markdown/docs/community/050-mentorship-program/summerofcode-README.md"
)

echo "Checking if all program files exist..."
for file in "${files[@]}"; do
  if [ -f "$file" ]; then
    echo "✓ $file"
  else
    echo "✗ MISSING: $file"
  fi
done

Length of output: 503

---

🏁 Script executed:

#!/bin/bash
# Search for openforce and hacktoberfest files anywhere in the repo
echo "Searching for openforce files..."
find markdown/docs/community/050-mentorship-program -type f -name "*openforce*" 2>/dev/null || echo "No openforce files found"

echo ""
echo "Searching for hacktoberfest files..."
find markdown/docs/community/050-mentorship-program -type f -name "*hacktoberfest*" 2>/dev/null || echo "No hacktoberfest files found"

echo ""
echo "Listing all files in the mentorship-program directory:"
ls -la markdown/docs/community/050-mentorship-program/

Length of output: 275

---

🏁 Script executed:

#!/bin/bash
# Find the actual mentorship-program directory and verify file status
echo "Finding mentorship-program directories..."
find . -type d -name "*mentorship*" 2>/dev/null | head -20

echo ""
echo "Searching for openforce anywhere in repo..."
find . -type f -o -type d -name "*openforce*" 2>/dev/null | head -20

echo ""
echo "Searching for hacktoberfest anywhere in repo..."
find . -type f -o -type d -name "*hacktoberfest*" 2>/dev/null | head -20

Length of output: 2819

---

---

🏁 Script executed:

```shell
#!/bin/bash
# Check correct path and list all files
echo "Checking mentorship-program directory contents..."
ls -la ./git/markdown/docs/community/050-mentorship-program/

echo ""
echo "Verifying specific files with correct path..."
files=(
  "./git/markdown/docs/community/050-mentorship-program/seasonofdocs-2023-README.md"
  "./git/markdown/docs/community/050-mentorship-program/winterofcode-2023-README.md"
  "./git/markdown/docs/community/050-mentorship-program/openforce/README.md"
  "./git/markdown/docs/community/050-mentorship-program/hacktoberfest/README.md"
  "./git/markdown/docs/community/050-mentorship-program/asyncapi-mentorship-README.md"
  "./git/markdown/docs/community/050-mentorship-program/summerofcode-README.md"
)

for file in "${files[@]}"; do
  if [ -f "$file" ]; then
    echo "✓ EXISTS: $file"
  else
    echo "✗ MISSING: $file"
  fi
done

Length of output: 734

---

Fix broken links to missing program documentation files (lines 29-30).

The "Available Programs" table contains links to two non-existent documentation files:

• ./openforce/README (line 29) — file does not exist
• ./hacktoberfest/README (line 30) — file does not exist

Either create these documentation files or remove these programs from the table if they are not currently active in the mentorship hub.

🤖 Prompt for AI Agents

In markdown/docs/community/050-mentorship-program/index.md around lines 25 to
30, the "Available Programs" table links to ./openforce/README and
./hacktoberfest/README which do not exist; either add the missing documentation
files at those paths with appropriate content (README files for OpenForce and
Hacktoberfest) and ensure the links are correct, or remove the two table rows
(OpenForce and Hacktoberfest) from the table so there are no broken links and
update any related index/navigation if necessary.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Verify top recurring mentor GitHub handles are current.

Lines 54-65 list top recurring mentors with GitHub handles and years active. Ensure these handles are current and that the years active reflect accurate program participation. Note: Line 58 references "@Souvikns" while elsewhere in the documentation you see "Souvik De" referenced as "@Souvikns"—verify casing consistency.

---

🏁 Script executed:

#!/bin/bash
# Verify recurring mentor GitHub handles exist
mentors=("derberg" "souvikns" "acethecreator" "akshatnema" "ivangsa" "Mayaleeeee" "sambhavgupta0705" "thulieblack")

for mentor in "${mentors[@]}"; do
  result=$(curl -s "https://api.github.com/users/$mentor" | grep "\"login\"" | head -1)
  echo "Handle: $mentor -> $result"
done

Length of output: 379

---

Update mentor GitHub handle casing to match official account logins.

The GitHub handles exist and are valid, but the markdown contains casing inconsistencies:

• Line 56: Update acethecreator → AceTheCreator
• Line 58: Update souvikns → Souvikns

While GitHub URLs are case-insensitive, the documentation should reflect accurate handle casing. The remaining handles (derberg, akshatnema, ivangsa, Mayaleeeee, sambhavgupta0705, thulieblack) are correct.

🤖 Prompt for AI Agents

In markdown/docs/community/050-mentorship-program/insights.md around lines 54 to
65, update the GitHub handle casing for two mentors: change the handle for Azeez
Elegbede from acethecreator to AceTheCreator and change the handle for Souvik De
from souvikns to Souvikns; update both the link display text and the GitHub URL
segments accordingly so the markdown reflects the official account casing.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Potential typo in mentee name.

Line 77 lists "Ashmit JaiSarita Guptap" with surname "Guptap" (extra 'p'). Line 61 in the same file lists "Ashmit JaiSarita Gupta" without the extra 'p'. Verify the correct spelling and ensure consistency across all documentation pages.

---

🏁 Script executed:

#!/bin/bash
# Check GitHub profile to verify correct name spelling
curl -s https://api.github.com/users/devilkiller-ag | grep -i "name\|login"

Length of output: 99

---

---

🏁 Script executed:

```shell
#!/bin/bash
# Verify both line 61 and line 77 in the insights.md file
rg -n "Ashmit JaiSarita Gup" markdown/docs/community/050-mentorship-program/insights.md

Length of output: 131

---

---

🏁 Script executed:

```shell
#!/bin/bash
# Search for all instances of Ashmit JaiSarita and devilkiller-ag in the file
rg -n "devilkiller-ag\|Ashmit JaiSarita" markdown/docs/community/050-mentorship-program/insights.md

Length of output: 0

---

---

🏁 Script executed:

```shell
#!/bin/bash
# Search for devilkiller-ag using simpler approach
rg -n "devilkiller-ag" markdown/docs/community/050-mentorship-program/insights.md

Length of output: 189

---

---

🏁 Script executed:

```shell
#!/bin/bash
# View lines 55-65 to see what's at line 61
sed -n '55,65p' markdown/docs/community/050-mentorship-program/insights.md

Length of output: 747

---

---

🏁 Script executed:

```shell
#!/bin/bash
# View lines 75-80 to see full context of the typo
sed -n '75,80p' markdown/docs/community/050-mentorship-program/insights.md

Length of output: 371

---

Fix typo in mentor name at line 77.

Line 77 contains a typo: "Ashmit JaiSarita Guptap" should be "Ashmit JaiSarita Gupta" (remove extra 'p'). GitHub profile confirms the correct spelling is "Gupta".

🤖 Prompt for AI Agents

In markdown/docs/community/050-mentorship-program/insights.md around lines 76 to
77, there's a typo in the mentor name "Ashmit JaiSarita Guptap"; update the name
to "Ashmit JaiSarita Gupta" (remove the trailing 'p') so the entry matches the
correct GitHub profile spelling.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Project 5 is missing mentee information and completion marker.

Projects 1–4 each include a mentee field and a ✅ completion checkmark in their titles, indicating finalized projects. Project 5 lacks both, which creates an inconsistency suggesting either incomplete data or different status. For consistency with the other four projects, either add the mentee name and completion marker, or clarify in documentation why this project differs.

If a mentee should be listed, apply this diff:

 - 👩🏿‍🏫 **Mentor(s):** [David Pereira](https://github.com/BOLT04)
+- 👩🏿‍🏫 **Mentee:** [Mentee Name](GitHub URL)
 - ⏳ **Length:** 175 Hours

And update the title:

-## 5) [Add `help/{command}` endpoint: Server API](https://github.com/asyncapi/server-api/issues/144)
+## 5) [Add `help/{command}` endpoint: Server API](https://github.com/asyncapi/server-api/issues/144) ✅

---

🏁 Script executed:

#!/bin/bash
# Extract and display all 5 projects with their metadata to verify consistency claims

echo "=== EXTRACTING ALL 5 GSOC PROJECT IDEAS ==="
cat markdown/docs/community/050-mentorship-program/summerofcode-2023-asyncapi-gsoc-ideas-page.md | sed -n '12,88p'

Length of output: 5597

---

Review comment is verified as correct; Project 5 lacks mentee field and completion marker.

The actual file contents confirm the review comment's findings: Projects 1–4 each include a mentee and a ✅ completion marker in the title, while Project 5 is missing both. This is an objective inconsistency that requires correction. The developer should either supply the missing mentee information and checkmark, or explicitly document why Project 5 has a different status.

🧰 Tools

🪛 LanguageTool

[style] ~80-~80: Consider replacing this phrase with the adverb “similarly” to avoid wordiness.
Context: ...plates etc. The endpoint should be done in a similar way as in our main CLI, so the main help en...

(IN_A_X_MANNER)

🤖 Prompt for AI Agents

In
markdown/docs/community/050-mentorship-program/summerofcode-2023-asyncapi-gsoc-ideas-page.md
around lines 78 to 88, Project 5 is missing the mentee attribution and the
completion checkmark present on Projects 1–4; update the Project 5 heading to
include the mentee (e.g., "— Mentee: <name>") and add the ✅ completion marker to
match the format used earlier, or if it intentionally differs, add a short
parenthetical note explaining why this project lacks a mentee/completion marker
so the inconsistency is documented.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix grammatical error in checkbox note.

"are project" should be "are projects".

-> Note: Projects with checkboxes are project that made it to the final.
+> Note: Projects with checkboxes are projects that made it to the final.

🤖 Prompt for AI Agents

In
markdown/docs/community/050-mentorship-program/summerofcode-2025-asyncapi-gsoc-ideas-page.md
around line 12, fix the grammatical error in the note: change "Projects with
checkboxes are project that made it to the final." to use the plural noun
"projects" (i.e., "are projects that made it to the final.") so the sentence
reads correctly.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Hyphenate compound adjective modifying "Contribution".

"Open Source Contribution" should be "Open-Source Contribution" when used as a compound adjective.

-- 🛠️ **Skills Required:** TypeScript/JavaScript, VS Code Extensions, Spectral Linting, Testing, and Open Source Contribution.
+- 🛠️ **Skills Required:** TypeScript/JavaScript, VS Code Extensions, Spectral Linting, Testing, and Open-Source Contribution.

📝 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

	- 🛠️ **Skills Required:** TypeScript/JavaScript, VS Code Extensions, Spectral Linting, Testing, and Open Source Contribution.
	- 🛠️ **Skills Required:** TypeScript/JavaScript, VS Code Extensions, Spectral Linting, Testing, and Open-Source Contribution.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~56-~56: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ensions, Spectral Linting, Testing, and Open Source Contribution. - 🧩 Difficulty: Medi...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

🤖 Prompt for AI Agents

In
markdown/docs/community/050-mentorship-program/summerofcode-2025-asyncapi-gsoc-ideas-page.md
around line 56, the phrase "Open Source Contribution" used as a compound
adjective should be hyphenated; update that line to read "Open-Source
Contribution" so the compound adjective is correctly formed.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Capitalize GitHub platform name.

"Github actions" should be "GitHub Actions".

-- 🛠️ **Skills Required:** Typescript, Node js, Jest, Github actions
+- 🛠️ **Skills Required:** Typescript, Node.js, Jest, GitHub Actions

📝 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

	- 🛠️ **Skills Required:** Typescript, Node js, Jest, Github actions
	- 🛠️ **Skills Required:** Typescript, Node.js, Jest, GitHub Actions

🧰 Tools

🪛 LanguageTool

[uncategorized] ~76-~76: The official name of this software platform is spelled with a capital “H”.
Context: ... Required:** Typescript, Node js, Jest, Github actions - 🧩 Difficulty: Medium/Har...

(GITHUB)

🤖 Prompt for AI Agents

In
markdown/docs/community/050-mentorship-program/summerofcode-2025-asyncapi-gsoc-ideas-page.md
around line 76, the platform name "Github actions" is incorrectly cased; update
it to "GitHub Actions" and ensure both words are capitalized exactly as the
proper product name, e.g., "GitHub Actions", preserving the surrounding
formatting and punctuation.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Capitalize GitHub platform name.

"Github actions" should be "GitHub Actions".

-- 🛠️ **Skills Required:** Typescript, Node js, E2E Testing, Github actions
+- 🛠️ **Skills Required:** Typescript, Node.js, E2E Testing, GitHub Actions

📝 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

	- 🛠️ **Skills Required:** Typescript, Node js, E2E Testing, Github actions
	- 🛠️ **Skills Required:** Typescript, Node.js, E2E Testing, GitHub Actions

🧰 Tools

🪛 LanguageTool

[uncategorized] ~86-~86: The official name of this software platform is spelled with a capital “H”.
Context: ...ed:** Typescript, Node js, E2E Testing, Github actions - 🧩 Difficulty: Medium/Har...

(GITHUB)

🤖 Prompt for AI Agents

In
markdown/docs/community/050-mentorship-program/summerofcode-2025-asyncapi-gsoc-ideas-page.md
around line 86, update the platform name capitalization: change "Github actions"
to "GitHub Actions" in the Skills Required line so the product name is correctly
cased.