Skip to content

Conversation

@iambami
Copy link
Contributor

@iambami iambami commented Jun 4, 2025

Hey folks,

We have the next community spotlight blog up for review. The plan is to batch create these blogs and post them in the allocated time.

Please give it a review.

@thulieblack @AceTheCreator @derberg @Mayaleeeee

Summary by CodeRabbit

  • New Features
    • Published a Community Spotlight blog post featuring Aishat Muibudeen (Maya) about her journey from first contributions to leading design at AsyncAPI.
    • Covers her early contributions, leadership of the design working group, building the AsyncAPI Design System, founding OpenNest-Africa, mentorship experiences, a "Have You Ever?" segment, and final thoughts encouraging newcomers.

@netlify
Copy link

netlify bot commented Jun 4, 2025

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 53ff0e9
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/69750463f34eaf00089aef45
😎 Deploy Preview https://deploy-preview-4152--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 Jun 4, 2025

Walkthrough

Added a new community spotlight blog post interviewing Aishat Muibudeen (Maya) about her open source entry in 2022, contributions to AsyncAPI (conference site, design system), mentorship and maintainership roles, and founding OpenNest-Africa.

Changes

Cohort / File(s) Change Summary
New blog post
markdown/blog/community-spotlight-maya.md
Added an interview article profiling Aishat Muibudeen (Maya) covering her open source journey, initial AsyncAPI contributions, leadership in design initiatives, mentorship/maintainership work, and founding of OpenNest-Africa.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

ready-to-merge

Suggested reviewers

  • derberg
  • TRohit20
  • Mayaleeeee
  • quetzalliwrites
  • akshatnema

In a burrow of ideas I nibble and play,
Maya hopped forward, lighting the way.
From curious hops to leadership springs,
She gardens community — bright, brave things.
Hop on, contribute, and dance in the day! 🐇

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title "chore(blog): add Maya's community spotlight blog" succinctly and accurately summarizes the primary change (adding a community spotlight blog post for Maya). It is a short, single-line description using a clear conventional-commit scope ("chore(blog)"), making the intent and scope easy for reviewers and history scans to understand.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


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

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

@codecov
Copy link

codecov bot commented Jun 4, 2025

Codecov Report

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

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #4152   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          796       796           
  Branches       146       146           
=========================================
  Hits           796       796           

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

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: 2

🧹 Nitpick comments (3)
markdown/blog/community-spotlight-maya.md (3)

22-22: Style: Remove redundant “of”
Consider using “Outside AsyncAPI” instead of “Outside of AsyncAPI” for a more concise phrasing.

🧰 Tools
🪛 LanguageTool

[style] ~22-~22: This phrase is redundant. Consider using “Outside”.
Context: ...ember of the Code of Conduct Committee. Outside of AsyncAPI, I’m also the founder of [Open...

(OUTSIDE_OF)


26-26: Tone: Replace informal expression
The exclamation “That’s awesome!” feels informal. Consider a more neutral alternative such as “That’s impressive!” to maintain consistency with the professional tone.

🧰 Tools
🪛 LanguageTool

[style] ~26-~26: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...st Steps in Open Source **Bami: That’s awesome! Now, take us back to where it all bega...

(AWESOME)


39-41: Grammar: Clarify conjunction usage
In “how I ask for help and find support,” consider “how I asked for help and found support” to maintain tense consistency and parallel structure.

🧰 Tools
🪛 LanguageTool

[style] ~40-~40: This phrase is redundant. Consider using “outside”.
Context: ...k. I reached out to mentors and friends outside of AsyncAPI for support. One of my mentors...

(OUTSIDE_OF)


[grammar] ~40-~40: The word ‘help’ is a conjunction. In formal texts, use “to”.
Context: ...st in design, but in how I ask for help and find support within the spaces I’m part...

(HELP_AND_VB)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c0ef93d and 6fc0c46.

📒 Files selected for processing (1)
  • markdown/blog/community-spotlight-maya.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/community-spotlight-maya.md

[uncategorized] ~19-~19: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...aya shares her fascinating journey from open source newbie to core contributor and founder ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[style] ~22-~22: This phrase is redundant. Consider using “Outside”.
Context: ...ember of the Code of Conduct Committee. Outside of AsyncAPI, I’m also the founder of [Open...

(OUTSIDE_OF)


[style] ~26-~26: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...st Steps in Open Source **Bami: That’s awesome! Now, take us back to where it all bega...

(AWESOME)


[style] ~27-~27: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...e, but I was eager to join a community. I reached out to the recruiter, explained...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[uncategorized] ~27-~27: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... I was over the moon. My first official open source contribution!* ## Leading the Design C...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[style] ~40-~40: This phrase is redundant. Consider using “outside”.
Context: ...k. I reached out to mentors and friends outside of AsyncAPI for support. One of my mentors...

(OUTSIDE_OF)


[grammar] ~40-~40: The word ‘help’ is a conjunction. In formal texts, use “to”.
Context: ...st in design, but in how I ask for help and find support within the spaces I’m part...

(HELP_AND_VB)


[grammar] ~45-~45: The pronoun ‘She’ is usually used with a third-person or a past tense verb.
Context: ...By 2024, during the HerToberfest by She Code Africa (SCA), I took everything I had ...

(HE_VERB_AGR)


[uncategorized] ~45-~45: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ce we wish we had. And now we nurture it so others can find their place, too.* ## ...

(COMMA_COMPOUND_SENTENCE_2)


[uncategorized] ~54-~54: Possible missing comma found.
Context: ...You Ever? **Bami: I think that is all. Now the fun fact. There’s a lot of fun fact...

(AI_HYDRA_LEO_MISSING_COMMA)


[grammar] ~54-~54: Consider using the plural verb form for the plural noun “facts”.
Context: ... I think that is all. Now the fun fact. There’s a lot of fun facts, but we can do “Have...

(THERE_IS_A_LOT_OF)


[uncategorized] ~59-~59: Consider adding a comma between these interjections.
Context: ...o be API-related o.** Maya: Oh no, no no no. **Bami: Have you ever created a PR...

(OK_OK_COMMA)


[uncategorized] ~63-~63: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...a:** No, I thought I did break something but Lukasz told me I did not, so no, I’ve n...

(COMMA_COMPOUND_SENTENCE_2)


[typographical] ~65-~65: Should there be a question mark at the end of this sentence?
Context: ...mmunity?** Maya: Yeah, I mean, yeah. Several times. Yes, a lot. **Bami: Ama...

(MISSING_QUESTION_MARK2)


[style] ~67-~67: It might be better to use ‘time’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...ing your design work? Now “eureka” is a time where it’s just super exciting for you.** ***...

(WHEN_WHERE)


[style] ~70-~70: Consider using a synonym to be more concise.
Context: ...a meeting in your pajamas?** Maya: A lot of times I do. **Bami: Have you ever been...

(A_LOT_OF)


[misspelling] ~74-~74: ‘Everyday’ is an adjective. Did you mean “every day”?
Context: ...n something new from other contributors everyday.* **Bami: Have you ever gotten frustrat...

(EVERYDAY_EVERY_DAY)


[style] ~77-~77: The expression “way too much” can be considered informal. Consider replacing the phrase to sound more professional.
Context: ...Have you ever been called out for doing way too much?** *Maya: No, I told you. I know my...

(WAY_TOO_MUCH)


[style] ~78-~78: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...elf, I know what I want. What I can and can not do. Plus the community members are cool...

(CAN_NOT_PREMIUM)


[uncategorized] ~78-~78: Possible missing comma found.
Context: ...what I want. What I can and can not do. Plus the community members are cool people. ...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~80-~80: Possible missing comma found.
Context: ...** *Maya: You’re welcome. And thank you too. It's been a pleasure being on this...

(AI_HYDRA_LEO_MISSING_COMMA)


[duplication] ~86-~86: Possible typo: you repeated a word.
Context: ...’23), Design System, Leading the Design Community - Community Project: Founder, Open Nest Africa - St...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~92-~92: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ts Maya’s story is a reflection of how open source welcomes all kinds of contributors. Wit...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~93-~93: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...www.asyncapi.com/en) and begin your own open source journey.

(EN_COMPOUND_ADJECTIVE_INTERNAL)

⏰ Context from checks skipped due to timeout of 180000ms (1)
  • GitHub Check: Lighthouse CI
🔇 Additional comments (5)
markdown/blog/community-spotlight-maya.md (5)

1-17: Frontmatter: Missing cover value
The cover: field is currently empty, which will result in no header image being displayed. Either remove the empty field or supply a valid image path (e.g., /img/blog/community-spotlight-maya/cover.webp).


29-33: The narrative here flows well and aligns with project style guidelines.


34-38: Clear explanation of the design system—no changes needed.


47-51: Solid closing of the interview—no edits required.


82-88: The summary bullet points are clear and correctly formatted.

🧰 Tools
🪛 LanguageTool

[duplication] ~86-~86: Possible typo: you repeated a word.
Context: ...’23), Design System, Leading the Design Community - Community Project: Founder, Open Nest Africa - St...

(ENGLISH_WORD_REPEAT_RULE)

Comment on lines 42 to 46
## The Birth of Open Nest Africa

**Bami: That’s so insightful. Now tell us about your own initiative, OpenNest-Africa. What inspired it?**
***Maya:** OpenNest-Africa was born out of something I deeply understood, how hard it can be to find your footing in open source, especially when you’re just starting out and don’t have a technical background. My journey with AsyncAPI changed that for me. I found a space where I could contribute, lead, and grow, through design, through community, and through care. That experience opened my eyes, and I wanted to create something that could open doors for others too. In 2022, I participated in SheCodeAfrica’s HerFest, our team placed second in the GitHub project category, and that was a turning point. I realized I had the skills, clarity, and vision to help others get started in open source, too. By 2024, during the HerToberfest by She Code Africa (SCA), I took everything I had learned, from contribution models to inclusive community design, and co-founded OpenNest-Africa with three other incredible women. Though it started in Africa, OpenNest-Africa is a global initiative. We created it for beginners everywhere, whether you’re technical, non-technical, or just curious - to find guidance, support, and a community that feels safe and welcoming. We built the space we wish we had. And now we nurture it so others can find their place, too.*

Copy link
Contributor

@coderabbitai coderabbitai bot Jun 4, 2025

Choose a reason for hiding this comment

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

⚠️ Potential issue

Inconsistent project naming
The initiative appears as both “Open-Nest-Africa” and “Open Nest Africa.” Use the official branding “Open Nest Africa” (spaces, no hyphens) throughout for consistency.

🧰 Tools
🪛 LanguageTool

[grammar] ~45-~45: The pronoun ‘She’ is usually used with a third-person or a past tense verb.
Context: ...By 2024, during the HerToberfest by She Code Africa (SCA), I took everything I had ...

(HE_VERB_AGR)


[uncategorized] ~45-~45: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ce we wish we had. And now we nurture it so others can find their place, too.* ## ...

(COMMA_COMPOUND_SENTENCE_2)

🤖 Prompt for AI Agents
In markdown/blog/community-spotlight-maya.md around lines 42 to 46, the project
name is inconsistently written as "OpenNest-Africa" and "Open Nest Africa."
Replace all instances with the official branding "Open Nest Africa," using
spaces and no hyphens, to ensure consistency throughout the document.

Copy link
Member

Choose a reason for hiding this comment

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

This is worth looking into @iambami

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!

TRohit20
TRohit20 previously approved these changes Jun 30, 2025
Copy link
Collaborator

@TRohit20 TRohit20 left a comment

Choose a reason for hiding this comment

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

LGTM

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.

Please always add cover images to your blogs other wise the tests will never pass

@thulieblack thulieblack changed the title chore(blog):community-spotlight-maya chore(blog): add Maya's community spotlight blog Jul 8, 2025
@iambami
Copy link
Contributor Author

iambami commented Jul 8, 2025

Noted @thulieblack

There is no picture because I'm just batch creating the stories, and I didn’t know the cover image would affect the tests.

@sambhavgupta0705
Copy link
Member

@iambami are we proceeding with this one

@thulieblack
Copy link
Member

cover image is still missing cc @TRohit20

Co-authored-by: Antonio <bandantonio@users.noreply.github.com>
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 (5)
markdown/blog/community-spotlight-maya.md (5)

19-19: Use official name: “Open Nest Africa” (spaces, no hyphen)

Brand consistency; keep the existing link slug.

-...founder of [OpenNest-Africa](https://opencollective.com/open-nest-africa).
+...founder of [Open Nest Africa](https://opencollective.com/open-nest-africa).

23-23: Fix brand name here as well

-...founder of [OpenNest-Africa](https://opencollective.com/open-nest-africa).*
+...founder of [Open Nest Africa](https://opencollective.com/open-nest-africa).*

49-51: Standardize “Open Nest Africa” throughout this section

-**Bami: That’s so insightful. Now tell us about your own initiative, OpenNest-Africa. What inspired it?**
+**Bami: That’s so insightful. Now tell us about your own initiative, Open Nest Africa. What inspired it?**
@@
-***Maya:** OpenNest-Africa was born out of something I deeply understood, ...
+***Maya:** Open Nest Africa was born out of something I deeply understood, ...
@@
-...and co-founded OpenNest-Africa with three other incredible women.
+...and co-founded Open Nest Africa with three other incredible women.
@@
-Though it started in Africa, OpenNest-Africa is a global initiative.
+Though it started in Africa, Open Nest Africa is a global initiative.

118-118: Summary item: fix brand name

-- Community Project: Founder, OpenNest-Africa
+- Community Project: Founder, Open Nest Africa

61-66: Fix MD028 (blank line inside blockquote) breaking lint

There’s an un-prefixed blank line inside the blockquote (line 64). Prefix it with “>” to keep a contiguous block.

 > **Bami: I think that is all. Now the fun fact. There’s a lot of fun facts, but we can do “Have you ever?” Ten questions.**
- 
+>
 > ***Maya:** Okay.*
 > 
 > **Bami: Have you ever fixed bugs? Do you fix bugs? You’re not a developer.**
🧹 Nitpick comments (6)
markdown/blog/community-spotlight-maya.md (6)

51-51: Brand name consistency: “She Code Africa”

Two variants appear (“SheCodeAfrica” and “She Code Africa”). Please align to the official “She Code Africa”.

-In 2022, I participated in SheCodeAfrica’s HerFest,  our team placed second...
+In 2022, I participated in She Code Africa’s HerFest, our team placed second...

87-87: Microcopy: “time where” → “time when” (reads smoother)

-> **Bami: Have you ever had a eureka moment while doing your design work? Now “eureka” is a time where it’s just super exciting for you.**
+> **Bami: Have you ever had a eureka moment while doing your design work? By “eureka,” I mean a time when it’s just super exciting for you.**

99-99: “everyday” (adj.) → “every day” (adv.)

-> ***Maya:** Yes, I have. As a matter of fact, I learn something new from other contributors everyday.*
+> ***Maya:** Yes, I have. As a matter of fact, I learn something new from other contributors every day.*

107-107: Spell as “cannot”

-... What I can and can not do. Plus the community members are cool people. So no.*
+... What I can and cannot do. Plus the community members are cool people. So no.*

111-111: Add terminal period inside italics

-> ***Maya:** You’re welcome. And thank you too. It's been a pleasure being on this call*
+> ***Maya:** You’re welcome. And thank you too. It's been a pleasure being on this call.*

45-45: Punctuation: missing space after comma

-... Ace, really kept me grounded,he helped me stay focused ...
+... Ace, really kept me grounded, he helped me stay focused ...
📜 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 f04f341 and aac8044.

📒 Files selected for processing (1)
  • markdown/blog/community-spotlight-maya.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/community-spotlight-maya.md

64-64: Blank line inside blockquote

(MD028, no-blanks-blockquote)

⏰ 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
🔇 Additional comments (2)
markdown/blog/community-spotlight-maya.md (2)

3-3: Publish date likely stale—please confirm target go-live

PR thread said August publish. Today is September 11, 2025. If publishing now, update the date to the intended go-live to keep ordering and feeds correct.

Apply when ready:

-date: 2025-08-08T06:00:00+01:00
+date: 2025-09-12T06:00:00+01:00

10-10: Cover asset present — no action required.
Verified public/img/posts/marketing-images/maya-story.webp exists and is referenced in markdown/blog/community-spotlight-maya.md (line 10).

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.

Looks pretty good to me

bandantonio
bandantonio previously approved these changes Sep 12, 2025
TRohit20
TRohit20 previously approved these changes Sep 16, 2025
@thulieblack thulieblack dismissed stale reviews from TRohit20 and bandantonio via a94720d September 17, 2025 09:15
@thulieblack
Copy link
Member

@sambhavgupta0705 your approval please and thank you

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/community-spotlight-maya.md (1)

19-19: Use official naming: “Open Nest Africa” (spaces, no hyphen).

This was flagged earlier and some instances remain. Keep link slugs unchanged.

-...founder of [OpenNest-Africa](https://opencollective.com/open-nest-africa).
+...founder of [Open Nest Africa](https://opencollective.com/open-nest-africa).
-Outside of AsyncAPI, I’m also the founder of [OpenNest-Africa](https://opencollective.com/open-nest-africa).*
+Outside AsyncAPI, I’m also the founder of [Open Nest Africa](https://opencollective.com/open-nest-africa).*
-**Bami: That’s so insightful. Now tell us about your own initiative, OpenNest-Africa. What inspired it?**
+**Bami: That’s so insightful. Now tell us about your own initiative, Open Nest Africa. What inspired it?**
-***Maya:** OpenNest-Africa was born out of something I deeply understood, ...
+***Maya:** Open Nest Africa was born out of something I deeply understood, ...
-- Community Project: Founder, OpenNest-Africa
+- Community Project: Founder, Open Nest Africa

Also applies to: 23-23, 49-51, 118-118

🧹 Nitpick comments (7)
markdown/blog/community-spotlight-maya.md (7)

45-45: Punctuation: add separator after “grounded”.

-... kept me grounded,he helped me stay focused ...
+... kept me grounded—he helped me stay focused ...

87-87: Wording: “time where” → “time when”.

-... Now “eureka” is a time where it’s just super exciting for you.**
+... Now “eureka” is a time when it’s just super exciting for you.**

99-99: Grammar: “everyday” (adj.) → “every day” (adv.).

-... I learn something new from other contributors everyday.*
+... I learn something new from other contributors every day.*

107-107: Grammar: prefer “cannot”; tighten commas.

-... What I can and can not do. Plus the community members are cool people. So no.*
+... What I can and cannot do. Plus, the community members are cool people. So, no.*

61-112: Fix MD028 (no blank lines inside blockquotes) and improve Q&A spacing.

Current blank lines inside the blockquote trigger markdownlint and can render unpredictably. Make each Q/A pair a self‑contained blockquote (no internal blank line), and separate pairs with a normal blank line (outside the blockquote).

Example applied to the first two pairs:

-> **Bami: I think that is all. Now the fun fact. There’s a lot of fun facts, but we can do “Have you ever?” Ten questions.**
->
-> ***Maya:** Okay.*
+> **Bami: I think that is all. Now the fun fact. There’s a lot of fun facts, but we can do “Have you ever?” Ten questions.**
+> ***Maya:** Okay.*

-> **Bami: Have you ever fixed bugs? Do you fix bugs? You’re not a developer.**
->
-> ***Maya:** I think I have, on my portfolio when I was doing it on VS Code.*
+
+> **Bami: Have you ever fixed bugs? Do you fix bugs? You’re not a developer.**
+> ***Maya:** I think I have, on my portfolio when I was doing it on VS Code.*

Please apply the same pattern down to line 112, then run markdownlint locally to confirm MD028 is gone.


111-111: Minor punctuation: end sentence with a period.

-> ***Maya:** You’re welcome. And thank you too. It's been a pleasure being on this call*
+> ***Maya:** You’re welcome. And thank you too. It's been a pleasure being on this call.*

124-124: Canonical link: drop “/en” locale if not needed.

If the site auto‑localizes, prefer the root URL.

-Explore opportunities at [asyncapi.com](https://www.asyncapi.com/en) and begin your own open source journey.
+Explore opportunities at [asyncapi.com](https://www.asyncapi.com) and begin your own open source journey.
📜 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 aac8044 and a94720d.

📒 Files selected for processing (1)
  • markdown/blog/community-spotlight-maya.md (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-06-03T06:48:09.304Z
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/community-spotlight-maya.md
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/community-spotlight-maya.md

64-64: Blank line inside blockquote

(MD028, no-blanks-blockquote)

⏰ 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). (5)
  • GitHub Check: Redirect rules - asyncapi-website
  • GitHub Check: Header rules - asyncapi-website
  • GitHub Check: Pages changed - asyncapi-website
  • GitHub Check: Test NodeJS PR - macos-13
  • GitHub Check: Test NodeJS PR - windows-latest
🔇 Additional comments (1)
markdown/blog/community-spotlight-maya.md (1)

1-17: Frontmatter & cover image verified.

  • Date: 2025-09-08T06:00:00+01:00 — matches guidance to reflect the actual publish date; if you intend to publish after 2025-09-17, update the date to the merge/publish day to preserve chronological order.
  • Cover image exists at public/img/posts/marketing-images/maya-story.webp and is referenced in frontmatter as /img/posts/marketing-images/maya-story.webp.

@thulieblack
Copy link
Member

@sambhavgupta0705 ping pong

Copy link
Collaborator

@TRohit20 TRohit20 left a comment

Choose a reason for hiding this comment

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

@sambhavgupta0705 / @derberg could one of you please approve the PR ?

The blog has been approved but sitting stale for a while now.

CC @thulieblack (please lmk if there's some blocker i am unaware of to help on)

@princerajpoot20
Copy link
Member

@TRohit20 Done

@thulieblack
Copy link
Member

/rtm

@asyncapi-bot asyncapi-bot merged commit d0593b8 into asyncapi:master Jan 25, 2026
20 checks passed
@github-project-automation github-project-automation bot moved this from To Be Triaged to Done in Website - Kanban Jan 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

8 participants