docs: replace all mentions and links of alequetzalli to quetzalliwrites #3393
Conversation
bandantonio
requested review from
quetzalliwrites,
derberg,
akshatnema,
magicmatatjahu,
Mayaleeeee,
asyncapi-bot-eve,
thulieblack and
anshgoyalevil
as code owners
WalkthroughThe pull request includes updates to various documentation files to replace all instances of the contributor's name "Alejandra Quetzalli" with "Quetzalli Writes." This change is reflected across multiple Markdown files, the Changes
Assessment against linked issues
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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
CodeRabbit Configuration File (
|
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
asyncapi-bot
requested review from
devilkiller-ag,
sambhavgupta0705,
BhaswatiRoy,
J0SAL,
TRohit20 and
VaishnaviNandakumar
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3393 +/- ##
=======================================
Coverage 67.77% 67.77%
=======================================
Files 21 21
Lines 664 664
=======================================
Hits 450 450
Misses 214 214 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-3393--asyncapi-website.netlify.app/ |
![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
🧹 Outside diff range and nitpick comments (4)
markdown/blog/april-2023.md (1)
16-16: Consider updating the nickname reference for consistencyThe paragraph uses "Ale" as a nickname while using "Quetzalli Writes" in formal references. For consistency with the rebranding effort, consider updating "Ale" to "Quetzalli" or removing the nickname entirely.
markdown/blog/2024-Q1-docs-report.md (1)
18-18: Add missing article "the"Consider adding the article "the" before "AsyncAPI Initiative" for better grammar:
-collaborate with other areas in AsyncAPI Initiative. +collaborate with other areas in the AsyncAPI Initiative.🧰 Tools
🪛 LanguageTool
[uncategorized] ~18-~18: You might be missing the article “the” here.
Context: ...ibutors collaborate with other areas in AsyncAPI Initiative. ## Overview During Q1 2024...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
markdown/blog/google-season-of-docs-2022.md (1)
22-22: Consider using en dashes for date rangesFor better typography, consider replacing hyphens with en dashes in date ranges.
Apply these changes:
-31 Jan - 11 Feb 2022 +31 Jan – 11 Feb 2022 -14 Feb - 25 Feb 2022 +14 Feb – 25 Feb 2022 -28 Feb - 11 March 2022 +28 Feb – 11 March 2022Also applies to: 59-59
🧰 Tools
🪛 LanguageTool
[typographical] ~22-~22: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...ber from my [Gist Docs update for 31 Jan - 11 Feb 2022](https://gist.github.com/que...(DASH_RULE)
markdown/blog/release-notes-3.0.0.md (1)
362-362: Fix markdown linting issue: remove spaces inside link text.The current format has spaces inside the link text which triggers the MD039 linting rule.
Apply this diff to fix the markdown linting issue:
-[Quetzalli Writes](https://github.com/quetzalliwrites) +[QuetzalliWrites](https://github.com/quetzalliwrites)🧰 Tools
🪛 Markdownlint
362-362: null
Spaces inside link text(MD039, no-space-in-links)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (21)
.all-contributorsrc(1 hunks)README.md(1 hunks)assets/docs/fragments/contribution-notes.md(1 hunks)config/orbitData.json(1 hunks)markdown/blog/2022Q1-summary.md(3 hunks)markdown/blog/2023-April-docs-report.md(3 hunks)markdown/blog/2023-Q1-docs-report.md(2 hunks)markdown/blog/2023-Q4-docs-report.md(2 hunks)markdown/blog/2023-july-docs-report.md(1 hunks)markdown/blog/2023-june-docs-report.md(1 hunks)markdown/blog/2023-may-docs-report.md(1 hunks)markdown/blog/2024-Q1-docs-report.md(1 hunks)markdown/blog/2024-february-summary.md(1 hunks)markdown/blog/april-2023.md(1 hunks)markdown/blog/beyond-boundaries.md(1 hunks)markdown/blog/changes-coming-docs.md(1 hunks)markdown/blog/conference-2022.md(1 hunks)markdown/blog/google-season-of-docs-2022.md(4 hunks)markdown/blog/release-notes-3.0.0.md(1 hunks)markdown/blog/socketio-part1.md(1 hunks)markdown/blog/socketio-part2.md(1 hunks)
✅ Files skipped from review due to trivial changes (4)
- README.md
- assets/docs/fragments/contribution-notes.md
- config/orbitData.json
- markdown/blog/socketio-part1.md
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2022Q1-summary.md
[uncategorized] ~150-~150: Loose punctuation mark.
Context: ...oup of people to work on docs, checked. ✅ Our [new docs informa...
(UNLIKELY_OPENING_PUNCTUATION)
markdown/blog/2024-Q1-docs-report.md
[uncategorized] ~18-~18: You might be missing the article “the” here.
Context: ...ibutors collaborate with other areas in AsyncAPI Initiative. ## Overview During Q1 2024...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
markdown/blog/google-season-of-docs-2022.md
[typographical] ~22-~22: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...ber from my [Gist Docs update for 31 Jan - 11 Feb 2022](https://gist.github.com/que...
(DASH_RULE)
[typographical] ~59-~59: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...ns here in [AsyncAPI Docs update (31 Jan - 11 Feb 2022)](https://gist.github.com/qu...
(DASH_RULE)
[typographical] ~59-~59: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...4a3b56e2), [AsyncAPI Docs update (14 Feb - 25 Feb 2022)](https://gist.github.com/qu...
(DASH_RULE)
[typographical] ~59-~59: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...b477), and [AsyncAPI Docs update (28 Feb - 11 March 2022)](https://gist.github.com/...
(DASH_RULE)
🪛 Markdownlint
markdown/blog/google-season-of-docs-2022.md
96-96: null
Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
markdown/blog/release-notes-3.0.0.md
362-362: null
Spaces inside link text
(MD039, no-space-in-links)
🔇 Additional comments (28)
markdown/blog/2023-may-docs-report.md (2)
Line range hint 16-17: Verify rebranding in imported fragments.
The file imports two fragments that might contain author references. Let's verify these have been updated as well.
#!/bin/bash
# Description: Check imported fragments for any remaining old name references
# Check the imported fragment files
rg -i "alequetzalli" "assets/docs/fragments/contribution-notes.md" "assets/docs/fragments/talk-to-me.md"10-12: Verify the existence and consistency of the new avatar image.
The author information has been correctly updated to reflect the new branding. However, let's ensure the new avatar image exists and is properly referenced.
✅ Verification successful
Avatar image exists and branding is consistent
The new avatar image canela-quetzalli.webp exists in the correct location at public/img/avatars/, and the rebranding to "Quetzalli Writes" has been consistently applied across the codebase. Only one outdated reference was found in an issue title within dashboard.json, which is not part of the content files.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the existence of the new avatar image and check for any remaining old references
# Check if the new avatar image exists
fd "canela-quetzalli.webp" public/
# Look for any remaining references to the old name
rg -i "alequetzalli" .
Length of output: 314
Script:
#!/bin/bash
# Let's verify the image path and check for any references to both old and new branding
# Check if the image exists in the correct location
fd "canela-quetzalli.webp" .
# Check for any references to the new branding
rg -i "quetzalli-writes|quetzalli writes" .
# Check the structure of public/img/avatars directory
fd . "public/img/avatars" || ls -la public/img/avatars 2>/dev/null || find . -path "*/img/avatars" -type d
Length of output: 10929
markdown/blog/2023-july-docs-report.md (1)
10-12: LGTM! Author information updated correctly.
The changes align with the PR objectives to update the author's information consistently.
Let's verify the referenced resources exist:
✅ Verification successful
Resources verified successfully
The verification confirms:
- The new avatar image
canela-quetzalli.webpexists at the correct location - No remaining references to the old name were found in markdown files
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the new avatar image exists and there are no remaining old references
# Check if the new avatar image exists
fd "canela-quetzalli.webp" public/img/avatars/
# Verify no remaining references to old name
rg -i "alejandra|alequetzalli" --type md
Length of output: 130
markdown/blog/2024-february-summary.md (1)
16-16: LGTM! Verify the LinkedIn profile link.
The name update aligns with the rebranding request. The sentence structure and attribution are maintained correctly.
Let's verify the LinkedIn profile link is active and points to the correct profile:
✅ Verification successful
LinkedIn profile link format is correct and follows standard conventions
The LinkedIn profile URL follows the expected format https://www.linkedin.com/in/quetzalli-writes and matches LinkedIn's standard URL pattern for personal profiles.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the LinkedIn profile link format and accessibility
# Note: This only checks the URL format as actual HTTP requests to LinkedIn may be blocked
# Extract and verify the LinkedIn URL format
echo "Checking LinkedIn URL format..."
if rg -q 'https://www\.linkedin\.com/in/quetzalli-writes(/)?$' ; then
echo "LinkedIn URL format is valid"
else
echo "LinkedIn URL format may need review"
fi
Length of output: 201
markdown/blog/april-2023.md (1)
16-16: Verify the LinkedIn profile link
The LinkedIn profile link has been updated to reflect the rebranding. Let's verify it's working correctly.
markdown/blog/2024-Q1-docs-report.md (1)
18-18: LGTM!
The self-reference update is consistent with the rebranding effort.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~18-~18: You might be missing the article “the” here.
Context: ...ibutors collaborate with other areas in AsyncAPI Initiative. ## Overview During Q1 2024...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
markdown/blog/changes-coming-docs.md (2)
20-20: LGTM! Author introduction updates are consistent.
The personal introduction changes maintain consistency with the front matter updates while preserving the warm and engaging tone of the content.
Also applies to: 24-24, 26-26
10-12: Verify resource availability.
The author attribution changes look good and align with the rebranding effort.
Let's verify the resources exist:
✅ Verification successful
Resource verification completed successfully
The changes are consistent with the broader rebranding effort across the codebase:
- The new avatar image
canela-quetzalli.webpexists in the correct location - The new name "Quetzalli Writes" is consistently used across multiple blog posts and configuration files
- No references to the old avatar name were found
- The LinkedIn profile link format follows the standard pattern used in other files
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the existence of the new avatar image
# Check if the new avatar image exists
fd "canela-quetzalli.webp" public/img/avatars/
# Verify the old image is not referenced elsewhere
rg "canela-ale.webp"
Length of output: 108
Script:
#!/bin/bash
# Let's verify if there are any other references to the old or new author name
# across the codebase to ensure consistency
# Search for old name variations
rg -i "alejandra quetzalli"
# Search for new name
rg -i "quetzalli writes"
# Check for any other avatar references
rg -i "canela.*\.webp"
Length of output: 9291
markdown/blog/2023-Q4-docs-report.md (3)
21-21: LGTM! Author reference updated correctly
The self-reference update is consistent with the rebranding effort while maintaining the original context and tone of the document.
Line range hint 1-150: Verify no remaining instances of the old username
Let's ensure no references to the old username remain in the document:
✅ Verification successful
Since the search for the old username "alequetzalli" returned no results, and the document uses the new name "Quetzalli Writes" consistently, I can provide the final response:
No instances of old username found in the document
The document has been properly updated to use the new name "Quetzalli Writes" throughout, including the author attribution and content. No traces of the old username were found in any URLs or references.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Search for any remaining instances of the old username in the document
# Search for any instances of "alequetzalli" (case-insensitive)
rg -i "alequetzalli" markdown/blog/2023-Q4-docs-report.md
# Search for any URLs that might contain the old username
rg -i "https?://[^\s)]+alequetzalli[^\s)]+" markdown/blog/2023-Q4-docs-report.md
Length of output: 140
10-12: Verify the updated resources are accessible
The author information has been updated correctly. Let's verify the resources:
markdown/blog/2023-April-docs-report.md (3)
10-12: LGTM! Author details updated correctly.
The frontmatter changes accurately reflect the rebranding from "Alejandra Quetzalli" to "Quetzalli Writes", including the name, photo path, and LinkedIn profile link.
26-26: LGTM! Content updates maintain consistency.
All references to the author have been properly updated while preserving the original context and meaning of the content.
Also applies to: 29-29, 31-31, 34-34, 40-40, 58-58
11-11: Verify the new avatar image exists.
Please ensure that the new avatar image file /img/avatars/canela-quetzalli.webp has been added to the repository.
✅ Verification successful
Avatar image exists and no old references found
The new avatar image /img/avatars/canela-quetzalli.webp exists in the correct location and there are no remaining references to the old name in markdown files.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the existence of the new avatar image and check for any remaining old references
# Check if the new avatar image exists
fd "canela-quetzalli.webp" public/img/avatars/
# Check for any remaining references to the old name
rg -i "alejandra quetzalli|alequetzalli" --type md
Length of output: 140
markdown/blog/2023-june-docs-report.md (1)
10-12: LGTM! The author information has been updated correctly.
The changes align with the PR objectives to update references from "alequetzalli" to "quetzalliwrites".
Let's verify the new assets and links:
✅ Verification successful
The author information update is consistent and valid
The verification confirms:
- The new avatar image exists at the correct path:
public/img/avatars/canela-quetzalli.webp - The new LinkedIn profile URL
linkedin.com/in/quetzalli-writesis used consistently across multiple blog posts - No lingering references to the old name variations or LinkedIn profile were found
- The changes align with the broader rebranding effort
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the existence of the new avatar image and LinkedIn profile
# Check if the new avatar image exists in the repository
fd "canela-quetzalli.webp" "public/img/avatars/"
# Check if this image is referenced in other files that might need updating
rg "canela-ale\.webp" --type md
# Verify the LinkedIn profile URL is consistently updated across all files
rg "linkedin\.com/in/alejandra-quetzalli" --type md
Length of output: 175
Script:
#!/bin/bash
# Let's do a broader search to find any remaining references to the old name/profile
# that might need updating
# Search for any mentions of the old name variations
rg -i "alejandra.?quetzalli|alequetzalli" --type md
# Search for any old LinkedIn profile patterns
rg "linkedin\.com/in/ale(jandra)?-?quetzalli" --type md
# Check for any other files referencing the old avatar image pattern
rg "canela-ale" --type md
# Let's also verify the new LinkedIn profile is used consistently
rg "linkedin\.com/in/quetzalli-writes" --type md
Length of output: 2914
markdown/blog/conference-2022.md (1)
152-156: LGTM! Verify GitHub profile links.
The profile entry for Quetzalli Writes follows the consistent structure and correctly implements the rebranding.
Let's verify the GitHub profile and avatar links:
✅ Verification successful
GitHub profile and avatar links verified successfully
Both the GitHub profile quetzalliwrites and the avatar URL are accessible and working correctly.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify that the GitHub profile exists and the avatar URL is accessible
# Check if the GitHub profile exists
gh api users/quetzalliwrites --jq '.login' || echo "GitHub profile not found"
# Check if the avatar URL is accessible
curl -s -I "https://avatars.githubusercontent.com/quetzalliwrites" | head -n 1 | grep "HTTP/[0-9.]* 200" || echo "Avatar URL not accessible"
Length of output: 175
markdown/blog/2023-Q1-docs-report.md (2)
92-92: LGTM! Author references updated consistently
The content references have been updated to use "Quetzalli" consistently, maintaining the original context and meaning of the text.
Also applies to: 94-94
10-12: Verify the new avatar image exists
The author information has been updated correctly, but we should verify that the new image file exists at the specified path.
✅ Verification successful
Avatar image path is valid ✓
The referenced avatar image file canela-quetzalli.webp exists at the correct path /img/avatars/ in the public directory.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check if the new avatar image exists in the public directory
fd -t f "canela-quetzalli.webp" public/img/avatars/
Length of output: 92
markdown/blog/beyond-boundaries.md (1)
77-77: LGTM! Name and GitHub handle updated correctly.
The change correctly updates the mentor's name to "Quetzalli Writes" and the corresponding GitHub handle to "quetzalliwrites" in the mentorship projects table, aligning with the rebranding effort.
Let's verify there are no other occurrences of the old name in this file:
✅ Verification successful
No remaining occurrences of old name found - change is complete
The verification shows that there are no remaining instances of "alequetzalli" or "Alejandra Quetzalli" in the file, confirming that the rebranding has been properly implemented.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for any remaining instances of the old name/handle
# Note: Using case-insensitive search to catch any variations
echo "Checking for any remaining instances of 'alequetzalli' or 'Alejandra Quetzalli'..."
rg -i "alequetzalli|alejandra.?quetzalli" "markdown/blog/beyond-boundaries.md"
Length of output: 265
markdown/blog/google-season-of-docs-2022.md (3)
96-96: LGTM! Signature updated correctly
The signature has been updated to match the new branding while maintaining the same style.
🧰 Tools
🪛 Markdownlint
96-96: null
Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
22-22: Verify Gist link accessibility
The Gist links have been updated to reflect the new username.
Let's verify the accessibility of the updated Gist links:
#!/bin/bash
# Description: Verify Gist links are accessible and no old references remain
# Extract and verify all Gist URLs
rg -o 'https://gist\.github\.com/[^/)]+' . | while read -r url; do
echo "Checking $url..."
curl -s -I "$url" | head -n 1
done
# Double-check for any remaining old Gist references
rg -i "gist\.github\.com/alequetzalli" .Also applies to: 59-59
🧰 Tools
🪛 LanguageTool
[typographical] ~22-~22: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...ber from my [Gist Docs update for 31 Jan - 11 Feb 2022](https://gist.github.com/que...
(DASH_RULE)
10-12: Verify new author assets and links
The author metadata changes align with the rebranding objectives.
Let's verify the new image path and LinkedIn profile URL:
✅ Verification successful
Author metadata changes verified successfully
The verification shows that:
- The new image path
public/img/avatars/canela-quetzalli.webpexists in the repository - The LinkedIn profile URL format is consistent with other blog posts
- The author rebranding from "alequetzalli" to "quetzalliwrites" is consistently applied across the codebase, with only one remaining reference to the old handle in a historical bug report (
dashboard.json)
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the existence of the new author image and profile links
# Check if the new image exists in the public directory
fd -t f "canela-quetzalli.webp"
# Search for any remaining old references to ensure complete migration
rg -i "alequetzalli" .
Length of output: 2252
Script:
#!/bin/bash
# Let's try a different approach to verify the image and references
# Check for the image in public directory and any other common static asset directories
fd "canela-quetzalli.webp" -t f
# Look for any remaining references to the old username
rg -i "alequetzalli" --type md --type yaml --type json
# Check for any other instances of the new username to ensure consistency
rg -i "quetzalli-writes|quetzalliwrites" --type md --type yaml --type json
Length of output: 9702
markdown/blog/2022Q1-summary.md (4)
123-124: LGTM! Name and link updates are consistent
The changes correctly update the contributor's name and add appropriate link references while maintaining the original context about GSoD mentorship.
Also applies to: 126-126
150-150: LGTM! Name and link updates are consistent
The change correctly updates the contributor's name and adds the appropriate link reference while maintaining the original context about GSoD efforts.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~150-~150: Loose punctuation mark.
Context: ...oup of people to work on docs, checked. ✅ Our [new docs informa...
(UNLIKELY_OPENING_PUNCTUATION)
167-167: LGTM! Name and link updates are consistent
The change correctly updates the contributor's name and adds the appropriate link reference in the list of acknowledgments.
172-172: LGTM! Link references are properly defined
The changes correctly update the name reference and add well-structured link definitions at the bottom of the file. The spacing is maintained for proper markdown rendering.
Also applies to: 175-177
.all-contributorsrc (1)
64-67: LGTM! Contributor information updated correctly.
The changes accurately reflect the rebranding from "alequetzalli" to "quetzalliwrites" while maintaining the integrity of other contributor information.
Let's verify there are no remaining references to the old username in the codebase:
markdown/blog/release-notes-3.0.0.md (1)
362-362: LGTM! Name update aligns with rebranding.
The change correctly updates the contributor's name from "alequetzalli" to "Quetzalli Writes" while maintaining the proper link to their GitHub profile.
🧰 Tools
🪛 Markdownlint
362-362: null
Spaces inside link text
(MD039, no-space-in-links)
| - name: Quetzalli Writes | ||
| photo: /img/avatars/canela-quetzalli.webp | ||
| link: https://www.linkedin.com/in/quetzalli-writes/ |
There was a problem hiding this comment.
💡 Codebase verification
Image path needs to be updated
The avatar image exists but is located at /public/img/avatars/canela-quetzalli.webp while the markdown references it at /img/avatars/canela-quetzalli.webp. Update the path to include the public prefix.
🔗 Analysis chain
Verify the existence of the new avatar image
The author information has been updated correctly. However, let's verify that the new avatar image exists in the repository.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check if the new avatar image exists
fd -t f "canela-quetzalli.webp" img/avatars/
Length of output: 144
Script:
#!/bin/bash
# Let's first check if the image directory exists and its location
fd -t d "avatars"
# Then search for the image file across the repository
fd -t f "canela-quetzalli.webp"
# Also check for any similar image names
fd -t f "quetzalli"
Length of output: 171
There was a problem hiding this comment.
Not relevant, as public is the default location for different static assets. The static-site generator uses this location and appends the public prefix automatically
There was a problem hiding this comment.
@bandantonio, understood. Thank you for the clarification.
✏️ Learnings added
Learnt from: bandantonio
PR: asyncapi/website#3393
File: markdown/blog/2024-Q1-docs-report.md:10-12
Timestamp: 2024-11-13T20:34:17.145Z
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/...`).
Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.
Description
Personal rebranding for @quetzalliwrites 😀
Related issue(s)
Fixes #3389
Closes #3176
Summary by CodeRabbit