chore(blog): add Hugo's community spotlight blog #4296
Conversation
iambami
requested review from
Mayaleeeee,
TRohit20,
akshatnema,
anshgoyalevil,
asyncapi-bot-eve,
derberg,
sambhavgupta0705 and
thulieblack
as code owners
WalkthroughA new markdown blog post, "Evolving with AsyncAPI: Insights from Hugo Guerrero," has been added. This article features an interview with Hugo Guerrero, discussing his background, involvement with AsyncAPI, community advice, and perspectives on the future of AsyncAPI. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
asyncapi-bot
requested review from
CBID2,
ashmitjsg,
bandantonio and
vishvamsinh28
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4296 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 22 22
Lines 778 778
Branches 144 144
=========================================
Hits 778 778 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-4296--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: 0
🧹 Nitpick comments (6)
markdown/blog/community-spotlight-hugo.md (6)
20-22: Hyphenate compound adjective and finish the sentence
Style/grammar tweaks for the opening paragraph:-In this edition of our Community Spotlight, we’re excited to feature [Hugo Guerrero](https://www.linkedin.com/in/hugoguerrero/), a seasoned software developer, open source contributor, technical marketer, and advocate for better developer experience in the world of APIs and event-driven architecture. With over two decades of industry experience, Hugo brings both depth and clarity to AsyncAPI’s growing ecosystem. Currently the Head of Technical Marketing at [Kong Inc.](https://www.linkedin.com/company/konghq/) +In this edition of our Community Spotlight, we’re excited to feature [Hugo Guerrero](https://www.linkedin.com/in/hugoguerrero/), a seasoned software developer, **open-source** contributor, technical marketer, and advocate for better developer experience in the world of APIs and event-driven architecture. +With over two decades of industry experience, Hugo brings both depth and clarity to AsyncAPI’s growing ecosystem. He is currently the Head of Technical Marketing at [Kong Inc.](https://www.linkedin.com/company/konghq/).
46-46: Subject–verb agreement-While working on enterprise architecture, I realized asynchronous communication, pub/sub patterns is essential to building scalable systems. +While working on enterprise architecture, I realized asynchronous communication—pub/sub patterns—**are** essential to building scalable systems.
50-50: Tone & punctuation refinement-***Hugo:** Events. Getting to talk about AsyncAPI and seeing people realize the value it brings, especially its vendor-neutral nature is incredibly fulfilling. That moment of realization, where they see the possibilities, is the best.* +***Hugo:** Events. **Discussing** AsyncAPI and seeing people realize the value it brings—especially its vendor-neutral nature—is incredibly fulfilling. That moment of realization, when they see the possibilities, is the best.*
90-90: Correct missing initial capital-...contributors, and adopters bring it to life. hat’s what I expect for the future.* +...contributors, and adopters bring it to life. **That’s** what I expect for the future.*
96-96: Pluralise “scene” and split long sentence-**Bami: That's right, we have a lot of folks in the community who are working behind the scene, stay tuned for more community spotlight in the coming months. It’s been a pleasure chatting with you Hugo. Thank you so much for your time and all you do for the AsyncAPI community. I look forward to talking to you soon.** +**Bami: That's right. We have many folks in the community working behind the scenes. Stay tuned for more community spotlights in the coming months. It’s been a pleasure chatting with you, Hugo. Thank you for your time and all you do for the AsyncAPI community. I look forward to talking to you soon.**
82-84: Avoid using bold emphasis as pseudo-heading (MD036)
Lines 82-84 are bolded but not actual headings. Consider converting them to normal paragraphs or blockquotes to satisfy markdown-lint.-**Bami: Like “what color is the sky?”** - -**Hugo: We were singing and dancing on the stage, so you can imagine.** +> **Bami:** “What color is the sky?” +> +> **Hugo:** We were singing and dancing on the stage, so you can imagine.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/community-spotlight-hugo.md(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: iambami
PR: asyncapi/website#4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
Learnt from: asyncapi-bot
PR: asyncapi/website#0
File: :0-0
Timestamp: 2025-02-18T12:07:42.211Z
Learning: The following PR commands are supported in the asyncapi/website repository:
- `/please-take-a-look` or `/ptal`: Requests attention from reviewers who haven't reviewed the PR
- `/ready-to-merge` or `/rtm`: Triggers automerge when all conditions are met
- `/do-not-merge` or `/dnm`: Blocks automerge even if all conditions are met
- `/autoupdate` or `/au`: Adds autoupdate label to keep PR in sync with target branch
- `/update` or `/u`: One-time update of PR with latest changes from target branch
Learnt from: Siddhant-Pragyan-Sinha
PR: asyncapi/website#4074
File: markdown/blog/open-nest.md:11-12
Timestamp: 2025-04-28T01:13:59.084Z
Learning: For AsyncAPI blog posts, author photo filenames don't necessarily need to match the author's official name, as some authors may use pen names or nicknames (e.g., Aishat Muibudeen using "maya_picture.webp" for her avatar).
📚 Learning: for asyncapi community spotlight blog posts, the frontmatter date should reflect the actual publicat...
Learnt from: iambami
PR: asyncapi/website#4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
Applied to files:
markdown/blog/community-spotlight-hugo.md
🪛 LanguageTool
markdown/blog/community-spotlight-hugo.md
[uncategorized] ~20-~20: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...rrero/), a seasoned software developer, open source contributor, technical marketer, and ad...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~46-~46: Consider an alternative for the overused word “exactly”.
Context: ...ke developers' lives easier, and that’s exactly what AsyncAPI aims to do. I started by ...
(EXACTLY_PRECISELY)
[style] ~50-~50: This phrase can be considered informal. To elevate your writing, consider using a more professional alternative.
Context: ...ncAPI?** *Hugo: Events. Getting to talk about AsyncAPI and seeing people realize the ...
(TALK_ABOUT_DISCUSS)
[style] ~80-~80: You used “that” more than once. Consider replacing one of them with a similar word.
Context: ...he time, I’m not doing that anymore but that was fun.* **Bami: Like “what color is ...
(THAT_REPETITION)
[style] ~96-~96: Consider using a synonym to be more concise.
Context: ...orward.* **Bami: That's right, we have a lot of folks in the community who are working ...
(A_LOT_OF)
[uncategorized] ~100-~100: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ted in years of hands-on experience and open source values. His journey reminds us that mea...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~102-~102: Opting for a less wordy alternative here may improve the clarity of your writing.
Context: ... the AsyncAPI Governance Board, Hugo is not only influencing the future of the specification but also helping steer the community toward a more inclu...
(NOT_ONLY_ALSO)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/community-spotlight-hugo.md
82-82: 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). (1)
- GitHub Check: Lighthouse CI
🔇 Additional comments (1)
markdown/blog/community-spotlight-hugo.md (1)
3-3: Verify publication date in front-matter
dateis set to 2025-09-10, which is in the future relative to the PR creation (Aug 2025). Per the Community-Spotlight convention (see retrieved learning), the date should match the actual publication date. Please confirm the intended publish date before merge.
|
|
||
| --- | ||
|
|
||
| In this edition of our Community Spotlight, we’re excited to feature [Hugo Guerrero](https://www.linkedin.com/in/hugoguerrero/), a seasoned software developer, open source contributor, technical marketer, and advocate for better developer experience in the world of APIs and event-driven architecture. With over two decades of industry experience, Hugo brings both depth and clarity to AsyncAPI’s growing ecosystem. Currently the Head of Technical Marketing at [Kong Inc.](https://www.linkedin.com/company/konghq/) |
There was a problem hiding this comment.
| In this edition of our Community Spotlight, we’re excited to feature [Hugo Guerrero](https://www.linkedin.com/in/hugoguerrero/), a seasoned software developer, open source contributor, technical marketer, and advocate for better developer experience in the world of APIs and event-driven architecture. With over two decades of industry experience, Hugo brings both depth and clarity to AsyncAPI’s growing ecosystem. Currently the Head of Technical Marketing at [Kong Inc.](https://www.linkedin.com/company/konghq/) | |
| In this edition of our Community Spotlight, we’re excited to feature [Hugo Guerrero](https://www.linkedin.com/in/hugoguerrero/), a seasoned software developer, open source contributor, technical marketer, and advocate for better developer experience in the world of APIs and event-driven architecture. With over two decades of industry experience, Hugo brings both depth and clarity to AsyncAPI’s growing ecosystem. Currently, he’s the Head of Technical Marketing at [Kong Inc.](https://www.linkedin.com/company/konghq/) |
CBID2
left a comment
CBID2
left a comment
There was a problem hiding this comment.
Aside from minor grammar issues, it looks good so far.
|
Done @CBID2 Thank you |
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
markdown/blog/community-spotlight-hugo.md (1)
20-21: Minor punctuation nitpick
Sentence at Line 20 ends without a period. Consider adding one for completeness.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/community-spotlight-hugo.md(1 hunks)
🧰 Additional context used
🧠 Learnings (3)
📓 Common learnings
Learnt from: iambami
PR: asyncapi/website#4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
Learnt from: asyncapi-bot
PR: asyncapi/website#0
File: :0-0
Timestamp: 2025-02-18T12:07:42.211Z
Learning: The following PR commands are supported in the asyncapi/website repository:
- `/please-take-a-look` or `/ptal`: Requests attention from reviewers who haven't reviewed the PR
- `/ready-to-merge` or `/rtm`: Triggers automerge when all conditions are met
- `/do-not-merge` or `/dnm`: Blocks automerge even if all conditions are met
- `/autoupdate` or `/au`: Adds autoupdate label to keep PR in sync with target branch
- `/update` or `/u`: One-time update of PR with latest changes from target branch
Learnt from: Siddhant-Pragyan-Sinha
PR: asyncapi/website#4074
File: markdown/blog/open-nest.md:11-12
Timestamp: 2025-04-28T01:13:59.084Z
Learning: For AsyncAPI blog posts, author photo filenames don't necessarily need to match the author's official name, as some authors may use pen names or nicknames (e.g., Aishat Muibudeen using "maya_picture.webp" for her avatar).
📚 Learning: for asyncapi community spotlight blog posts, the frontmatter date should reflect the actual publicat...
Learnt from: iambami
PR: asyncapi/website#4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
Applied to files:
markdown/blog/community-spotlight-hugo.md
📚 Learning: in the asyncapi codebase, batch processing operations (like in the dashboard script and check-editli...
Learnt from: anshgoyalevil
PR: asyncapi/website#3557
File: scripts/markdown/check-editlinks.js:58-59
Timestamp: 2025-01-08T15:15:00.759Z
Learning: In the AsyncAPI codebase, batch processing operations (like in the Dashboard script and check-editlinks.js) follow a sequential pattern using await in loops, which is the preferred approach for maintaining consistency across the codebase.
Applied to files:
markdown/blog/community-spotlight-hugo.md
🪛 LanguageTool
markdown/blog/community-spotlight-hugo.md
[style] ~46-~46: Consider an alternative for the overused word “exactly”.
Context: ...ke developers' lives easier, and that’s exactly what AsyncAPI aims to do. I started by ...
(EXACTLY_PRECISELY)
[style] ~50-~50: This phrase can be considered informal. To elevate your writing, consider using a more professional alternative.
Context: ...ncAPI?** *Hugo: Events. Getting to talk about AsyncAPI and seeing people realize the ...
(TALK_ABOUT_DISCUSS)
[style] ~80-~80: You used “that” more than once. Consider replacing one of them with a similar word.
Context: ...he time, I’m not doing that anymore but that was fun.* **Bami: Like “what color is ...
(THAT_REPETITION)
[style] ~96-~96: Consider using a synonym to be more concise.
Context: ...orward.* **Bami: That's right, we have a lot of folks in the community who are working ...
(A_LOT_OF)
[style] ~102-~102: Opting for a less wordy alternative here may improve the clarity of your writing.
Context: ... the AsyncAPI Governance Board, Hugo is not only influencing the future of the specification but also helping steer the community toward a more inclu...
(NOT_ONLY_ALSO)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/community-spotlight-hugo.md
82-82: 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). (2)
- GitHub Check: Test NodeJS PR - windows-latest
- GitHub Check: Test NodeJS PR - macos-13
🔇 Additional comments (2)
markdown/blog/community-spotlight-hugo.md (2)
3-3: Confirm front-matter date matches intended publication date
Per previous spotlights, thedatefield should reflect the actual go-live date, not the month being highlighted.2025-09-10is in the future relative to the current month (August 2025). Please verify the planned publication schedule and adjust if the post will be published earlier.
10-10: Verify cover image path exists in repository
/img/posts/marketing-images/hugo-spotlight.webpmust be present in the static assets directory; otherwise Netlify deploy will 404.
| **Bami: Tell us a bit about your background and how you first encountered AsyncAPI?** | ||
|
|
||
| ***Hugo:** "My name is Hugo Guerrero. I'm from Mexico and currently based in Massachusetts, USA. I’ve been in software development since 1996 — over 25 years in roles ranging from developer to architect to consultant."* | ||
|
|
||
| Hugo's journey began with an electronic systems engineering background, but his passion for software development and architecture quickly led him into enterprise tooling, API management, and event-driven systems. His career spans both the **open source** and **enterprise software** worlds, and he’s currently focused on **Technical Marketing** and **Developer Advocacy**. | ||
|
|
||
| ***Hugo:** “Technical marketing is all about bridging product capabilities with real developer needs, helping unblock them and showcasing how to use new features effectively.”* | ||
|
|
||
| ## How Hugo Found AsyncAPI | ||
|
|
||
| While working on event-driven products and tools such as Kafka and JMS, Hugo came across AsyncAPI through the work of [Fran Mendez](https://www.linkedin.com/in/fmvilas/) and the wider initiative. Around the same time, he was contributing to a CNCF project called [Microcks](https://github.com/microcks/microcks), which started to adopt AsyncAPI to better support various bindings like Kafka and JMS. | ||
|
|
||
| ***Hugo:** I came across AsyncAPI a few years ago when I was exploring event-driven architectures. At the time, everyone knew OpenAPI for REST APIs, but there was a gap when it came to asynchronous communication. AsyncAPI filled that gap, and did it in a developer-friendly, open way.* | ||
|
|
||
| From early contributions on examples and specification discussions to supporting AsyncAPI within Micro and his enterprise tooling, Hugo's involvement has steadily deepened. | ||
|
|
||
| ## From Curiosity to Contribution | ||
|
|
||
| **Bami: What drew you to AsyncAPI and event-driven architecture?** | ||
|
|
||
| ***Hugo:** While working on enterprise architecture, I realized asynchronous communication, pub/sub patterns is essential to building scalable systems. AsyncAPI offered a structured, open way to document and support those patterns. It just clicked for me. I’ve always believed that tools should make developers' lives easier, and that’s exactly what AsyncAPI aims to do. I started by advocating for it in my talks and writing tutorials, but soon realized I could contribute more directly, especially by sharing feedback from the field and helping build awareness across the industry. It wasn’t just the technology though. The community was (and is!) incredibly open, diverse, and mission-driven. That really inspired me to get involved more deeply.* | ||
|
|
||
| **Bami: What’s been the most rewarding part of contributing to AsyncAPI?** | ||
|
|
||
| ***Hugo:** Events. Getting to talk about AsyncAPI and seeing people realize the value it brings, especially its vendor-neutral nature is incredibly fulfilling. That moment of realization, where they see the possibilities, is the best.* | ||
|
|
||
| **Bami: Fantastic! Are there any AsyncAPI tools or initiatives you’re especially proud of?** | ||
|
|
||
| ***Hugo:** I love the specification, of course, but also the Playground, Editor, and Generators. These tools make the ecosystem practical and accessible, especially for new users trying to understand EDA.* | ||
|
|
||
| **Bami: What challenges have you faced with AsyncAPI?** | ||
|
|
||
| ***Hugo:** The mindset shift from synchronous to asynchronous thinking can be tough. Terminology like "producer/consumer" or managing topics isn’t always intuitive. Also, support across languages and tools is still growing, and when it’s missing, you sometimes have to build your own.* | ||
|
|
||
| *But that’s also a call to action: more contributions help fill those gaps.* |
There was a problem hiding this comment.
Unbalanced emphasis markers break Markdown rendering
Lines containing speaker labels for Hugo use ***Hugo:** (three opening asterisks, two closing). This leaves one italic marker unclosed, causing the rest of the document to render in italics on many Markdown engines.
-***Hugo:** "My name is ...
+> **Hugo:** “My name is ...- Use a blockquote (
>) to indicate dialogue (consistent with other AsyncAPI interviews). - Use symmetrical
**pairs for bold; drop the extra*.
Apply the same change to all occurrences on Lines 28, 32, 38, 46, 50, 54, 58, 72, 80, 90.
📝 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.
| **Bami: Tell us a bit about your background and how you first encountered AsyncAPI?** | |
| ***Hugo:** "My name is Hugo Guerrero. I'm from Mexico and currently based in Massachusetts, USA. I’ve been in software development since 1996 — over 25 years in roles ranging from developer to architect to consultant."* | |
| Hugo's journey began with an electronic systems engineering background, but his passion for software development and architecture quickly led him into enterprise tooling, API management, and event-driven systems. His career spans both the **open source** and **enterprise software** worlds, and he’s currently focused on **Technical Marketing** and **Developer Advocacy**. | |
| ***Hugo:** “Technical marketing is all about bridging product capabilities with real developer needs, helping unblock them and showcasing how to use new features effectively.”* | |
| ## How Hugo Found AsyncAPI | |
| While working on event-driven products and tools such as Kafka and JMS, Hugo came across AsyncAPI through the work of [Fran Mendez](https://www.linkedin.com/in/fmvilas/) and the wider initiative. Around the same time, he was contributing to a CNCF project called [Microcks](https://github.com/microcks/microcks), which started to adopt AsyncAPI to better support various bindings like Kafka and JMS. | |
| ***Hugo:** I came across AsyncAPI a few years ago when I was exploring event-driven architectures. At the time, everyone knew OpenAPI for REST APIs, but there was a gap when it came to asynchronous communication. AsyncAPI filled that gap, and did it in a developer-friendly, open way.* | |
| From early contributions on examples and specification discussions to supporting AsyncAPI within Micro and his enterprise tooling, Hugo's involvement has steadily deepened. | |
| ## From Curiosity to Contribution | |
| **Bami: What drew you to AsyncAPI and event-driven architecture?** | |
| ***Hugo:** While working on enterprise architecture, I realized asynchronous communication, pub/sub patterns is essential to building scalable systems. AsyncAPI offered a structured, open way to document and support those patterns. It just clicked for me. I’ve always believed that tools should make developers' lives easier, and that’s exactly what AsyncAPI aims to do. I started by advocating for it in my talks and writing tutorials, but soon realized I could contribute more directly, especially by sharing feedback from the field and helping build awareness across the industry. It wasn’t just the technology though. The community was (and is!) incredibly open, diverse, and mission-driven. That really inspired me to get involved more deeply.* | |
| **Bami: What’s been the most rewarding part of contributing to AsyncAPI?** | |
| ***Hugo:** Events. Getting to talk about AsyncAPI and seeing people realize the value it brings, especially its vendor-neutral nature is incredibly fulfilling. That moment of realization, where they see the possibilities, is the best.* | |
| **Bami: Fantastic! Are there any AsyncAPI tools or initiatives you’re especially proud of?** | |
| ***Hugo:** I love the specification, of course, but also the Playground, Editor, and Generators. These tools make the ecosystem practical and accessible, especially for new users trying to understand EDA.* | |
| **Bami: What challenges have you faced with AsyncAPI?** | |
| ***Hugo:** The mindset shift from synchronous to asynchronous thinking can be tough. Terminology like "producer/consumer" or managing topics isn’t always intuitive. Also, support across languages and tools is still growing, and when it’s missing, you sometimes have to build your own.* | |
| *But that’s also a call to action: more contributions help fill those gaps.* | |
| **Bami: Tell us a bit about your background and how you first encountered AsyncAPI?** | |
| > **Hugo:** “My name is Hugo Guerrero. I'm from Mexico and currently based in Massachusetts, USA. I’ve been in software development since 1996 — over 25 years in roles ranging from developer to architect to consultant.” | |
| Hugo's journey began with an electronic systems engineering background, but his passion for software development and architecture quickly led him into enterprise tooling, API management, and event-driven systems. His career spans both the **open source** and **enterprise software** worlds, and he’s currently focused on **Technical Marketing** and **Developer Advocacy**. | |
| ***Hugo:** “Technical marketing is all about bridging product capabilities with real developer needs, helping unblock them and showcasing how to use new features effectively.”* |
🧰 Tools
🪛 LanguageTool
[style] ~46-~46: Consider an alternative for the overused word “exactly”.
Context: ...ke developers' lives easier, and that’s exactly what AsyncAPI aims to do. I started by ...
(EXACTLY_PRECISELY)
[style] ~50-~50: This phrase can be considered informal. To elevate your writing, consider using a more professional alternative.
Context: ...ncAPI?** *Hugo: Events. Getting to talk about AsyncAPI and seeing people realize the ...
(TALK_ABOUT_DISCUSS)
🤖 Prompt for AI Agents
In markdown/blog/community-spotlight-hugo.md from lines 26 to 60, the speaker
labels for Hugo use unbalanced emphasis markers with three opening asterisks and
two closing, causing broken Markdown rendering. Replace these with symmetrical
double asterisks for bold text and use blockquote syntax (>) for dialogue lines
to match the style of other AsyncAPI interviews. Apply these changes
consistently to all specified lines to fix the formatting and ensure proper
rendering.
| **Bami: Amazing! Thank you so much. We are moving to the fun part now. What’s a fun or surprising fact about you that people may not know?** | ||
|
|
||
| ***Hugo:** Back in high school, I was into musical theatre, singing, dancing, performing on stage! I don’t do it anymore, but it was a big part of my youth. A very different kind of spotlight! Obviously I was young and agile at the time, I’m not doing that anymore but that was fun.* | ||
|
|
||
| **Bami: Like “what color is the sky?”** | ||
|
|
||
| **Hugo: We were singing and dancing on the stage, so you can imagine.** |
There was a problem hiding this comment.
🛠️ Refactor suggestion
MD036: emphasis used in place of a heading
**Bami: Like “what color is the sky?”** is picked up by markdown-lint because it follows a blank line and resembles a heading. If this is dialogue, keep it inside the dialogue blockquote to avoid the lint warning:
-
-**Bami: Like “what color is the sky?”**
+> **Bami:** “Like ‘what color is the sky?’”📝 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.
| **Bami: Amazing! Thank you so much. We are moving to the fun part now. What’s a fun or surprising fact about you that people may not know?** | |
| ***Hugo:** Back in high school, I was into musical theatre, singing, dancing, performing on stage! I don’t do it anymore, but it was a big part of my youth. A very different kind of spotlight! Obviously I was young and agile at the time, I’m not doing that anymore but that was fun.* | |
| **Bami: Like “what color is the sky?”** | |
| **Hugo: We were singing and dancing on the stage, so you can imagine.** | |
| **Bami: Amazing! Thank you so much. We are moving to the fun part now. What’s a fun or surprising fact about you that people may not know?** | |
| ***Hugo:** Back in high school, I was into musical theatre, singing, dancing, performing on stage! I don’t do it anymore, but it was a big part of my youth. A very different kind of spotlight! Obviously I was young and agile at the time, I’m not doing that anymore but that was fun.* | |
| > **Bami:** “Like ‘what color is the sky?’” | |
| **Hugo: We were singing and dancing on the stage, so you can imagine.** |
🧰 Tools
🪛 LanguageTool
[style] ~80-~80: You used “that” more than once. Consider replacing one of them with a similar word.
Context: ...he time, I’m not doing that anymore but that was fun.* **Bami: Like “what color is ...
(THAT_REPETITION)
🪛 markdownlint-cli2 (0.17.2)
82-82: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
🤖 Prompt for AI Agents
In markdown/blog/community-spotlight-hugo.md around lines 78 to 84, the line
'**Bami: Like “what color is the sky?”**' is incorrectly formatted with emphasis
markers that markdown-lint interprets as a heading. To fix this, remove the
emphasis markers and ensure this dialogue line remains inside the existing
dialogue blockquote or paragraph structure to prevent the lint warning about
emphasis used as a heading.
|
This pull request has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation. There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
4 participants
Hey folks,
Our next community spotlight is @hguerrero, and the draft is ready for review. Your feedback is appreciated. Thank you.
@derberg @thulieblack @TRohit20 @akshatnema @antoniogarrote @CBID2
Summary by CodeRabbit