chore(blog): add singapore summary #4056
Conversation
iambami
requested review from
thulieblack,
quetzalliwrites,
TRohit20,
derberg,
akshatnema,
anshgoyalevil,
sambhavgupta0705,
Mayaleeeee and
asyncapi-bot-eve
as code owners
WalkthroughA new blog post has been added to the project, titled "Bringing Asynchronous APIs to the Forefront at APIDays Singapore." This post documents AsyncAPI's debut at the APIDays conference in Singapore in April 2025, summarizing the event's highlights, key presentations, community engagement, and future conference plans. The article includes images, speaker highlights, and calls to action for community involvement. No changes were made to existing code or functionality; the update is limited to the addition of this new content. Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Note ⚡️ AI Code Reviews for VS Code, Cursor, WindsurfCodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback. 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. 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
Documentation and Community
|
asyncapi-bot
requested review from
devilkiller-ag,
vishvamsinh28,
Aahil13 and
VaishnaviNandakumar
✅ 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 ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4056 +/- ##
=========================================
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:
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (1)
markdown/blog/2025-singapore-conf-summary.md (1)
138-144: Unify event list date formatting and punctuation
The list uses inconsistent colon placement, date separators, and trailing periods. Consider a uniform pattern such as:
- [City 🇳🇬: Month DD–DD, YYYY](url)(no trailing period).Example revised block:
- - [Munich 🇩🇪 :July 2–3, 2025.](https://conference.asyncapi.com/venue/Munich) - - [Lagos 🇳🇬 :July 18–19, 2025](https://conference.asyncapi.com/venue/Lagos) - - [London 🇬🇧 :September 22–24, 2025](https://conference.asyncapi.com/venue/London) - - [Bengaluru 🇮🇳 :October 8-9](https://conference.asyncapi.com/venue/Bangalore) - - [Online 🌐 :October 29, 2025](https://conference.asyncapi.com/venue/Online) - - [Paris 🇫🇷 :December 9–11, 2025](https://conference.asyncapi.com/venue/Paris) + - [Munich 🇩🇪: July 2–3, 2025](https://conference.asyncapi.com/venue/Munich) + - [Lagos 🇳🇬: July 18–19, 2025](https://conference.asyncapi.com/venue/Lagos) + - [London 🇬🇧: September 22–24, 2025](https://conference.asyncapi.com/venue/London) + - [Bengaluru 🇮🇳: October 8–9, 2025](https://conference.asyncapi.com/venue/Bangalore) + - [Online 🌐: October 29, 2025](https://conference.asyncapi.com/venue/Online) + - [Paris 🇫🇷: December 9–11, 2025](https://conference.asyncapi.com/venue/Paris)🧰 Tools
🪛 LanguageTool
[style] ~142-~142: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ue/Bangalore) - [Online 🌐 :October 29, 2025](https://conference.asyncapi.com/venue/...(MISSING_COMMA_AFTER_YEAR)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-singapore-conf-summary.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-singapore-conf-summary.md
[grammar] ~33-~33: ‘make’ has the past form ‘made’.
Context: ...eone and see the lightbulb go off. This maked us estatic to kick-off the AsyncAPI con...
(EN_IRREGULAR_VERB)
[grammar] ~33-~33: The word “kick-off” is a noun. The verb is spelled with a white space.
Context: ...htbulb go off. This maked us estatic to kick-off the AsyncAPI conference with Singapore....
(NOUN_VERB_CONFUSION)
[style] ~43-~43: ‘filled to capacity’ might be wordy. Consider a shorter alternative.
Context: ...th overwhelming interest. Sessions were filled to capacity, with attendees eager to explore the nu...
(EN_WORDINESS_PREMIUM_FILLED_TO_CAPACITY)
[uncategorized] ~130-~130: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...reminder: AsyncAPI is no longer just an open source project—it’s a global movement. Being i...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~142-~142: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ue/Bangalore) - [Online 🌐 :October 29, 2025](https://conference.asyncapi.com/venue/...
(MISSING_COMMA_AFTER_YEAR)
⏰ Context from checks skipped due to timeout of 180000ms (1)
- GitHub Check: Lighthouse CI
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (1)
markdown/blog/2025-singapore-conf-summary.md (1)
32-33:⚠️ Potential issueFix preposition in conference intro
The sentence uses “with Singapore” incorrectly. It should be “in Singapore” to accurately reflect the location.- This made us ecstatic to kick off the AsyncAPI conference with Singapore. + This made us ecstatic to kick off the AsyncAPI conference in Singapore.
🧹 Nitpick comments (2)
markdown/blog/2025-singapore-conf-summary.md (2)
137-143: Normalize roadmap list formatting
The event links list currently has inconsistent spacing, punctuation, and hyphen/dash usage. Consider the following adjustments for consistency:
- Add a space after each colon.
- Use en dashes (–) for date ranges.
- Remove trailing periods inside the link text.
Example diff:
- - [Munich 🇩🇪 :July 2–3, 2025.](https://conference.asyncapi.com/venue/Munich) + - [Munich 🇩🇪: July 2–3, 2025](https://conference.asyncapi.com/venue/Munich) - - [Lagos 🇳🇬 :July 18–19, 2025](https://conference.asyncapi.com/venue/Lagos) + - [Lagos 🇳🇬: July 18–19, 2025](https://conference.asyncapi.com/venue/Lagos) - - [London 🇬🇧 :September 22–24, 2025](https://conference.asyncapi.com/venue/London) + - [London 🇬🇧: September 22–24, 2025](https://conference.asyncapi.com/venue/London) - - [Bengaluru 🇮🇳 :October 8-9](https://conference.asyncapi.com/venue/Bangalore) + - [Bengaluru 🇮🇳: October 8–9, 2025](https://conference.asyncapi.com/venue/Bangalore) - - [Online 🌐 :October 29, 2025](https://conference.asyncapi.com/venue/Online) + - [Online 🌐: October 29, 2025](https://conference.asyncapi.com/venue/Online) - - [Paris 🇫🇷 :December 9–11, 2025](https://conference.asyncapi.com/venue/Paris) + - [Paris 🇫🇷: December 9–11, 2025](https://conference.asyncapi.com/venue/Paris)🧰 Tools
🪛 LanguageTool
[style] ~141-~141: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ue/Bangalore) - [Online 🌐 :October 29, 2025](https://conference.asyncapi.com/venue/...(MISSING_COMMA_AFTER_YEAR)
43-43: Consider simplifying “filled to capacity”
The phrase “filled to capacity” is somewhat wordy; you could streamline it to “Sessions were full” or “fully booked” for greater conciseness.🧰 Tools
🪛 LanguageTool
[style] ~43-~43: ‘filled to capacity’ might be wordy. Consider a shorter alternative.
Context: ...th overwhelming interest. Sessions were filled to capacity, with attendees eager to explore the nu...(EN_WORDINESS_PREMIUM_FILLED_TO_CAPACITY)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-singapore-conf-summary.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-singapore-conf-summary.md
[style] ~43-~43: ‘filled to capacity’ might be wordy. Consider a shorter alternative.
Context: ...th overwhelming interest. Sessions were filled to capacity, with attendees eager to explore the nu...
(EN_WORDINESS_PREMIUM_FILLED_TO_CAPACITY)
[uncategorized] ~129-~129: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...reminder: AsyncAPI is no longer just an open source project—it’s a global movement. Being i...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~141-~141: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ue/Bangalore) - [Online 🌐 :October 29, 2025](https://conference.asyncapi.com/venue/...
(MISSING_COMMA_AFTER_YEAR)
⏰ Context from checks skipped due to timeout of 180000ms (4)
- GitHub Check: Redirect rules - asyncapi-website
- GitHub Check: Header rules - asyncapi-website
- GitHub Check: Pages changed - asyncapi-website
- GitHub Check: Lighthouse CI
🔇 Additional comments (1)
markdown/blog/2025-singapore-conf-summary.md (1)
1-15: Frontmatter is correctly configured
Verified title, date, type, tags, cover image path, author metadata, and excerpt. All fields align with project conventions and look ready for publication.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (3)
markdown/blog/2025-singapore-conf-summary.md (3)
43-43: Simplify wording to reduce wordiness
The phrase “filled to capacity” can be more concise. For example:- Sessions were filled to capacity, with attendees eager to explore… + Sessions were packed, with attendees eager to explore…🧰 Tools
🪛 LanguageTool
[style] ~43-~43: ‘filled to capacity’ might be wordy. Consider a shorter alternative.
Context: ...th overwhelming interest. Sessions were filled to capacity, with attendees eager to explore the nu...(EN_WORDINESS_PREMIUM_FILLED_TO_CAPACITY)
140-140: Use en dash for date ranges consistency
In the events list, the date range “October 8-9, 2025” uses a hyphen. For consistency with other items (e.g., “July 2–3, 2025”), replace it with an en dash: “October 8–9, 2025.”
173-173: Adjust punctuation around the quoted clause
The clause ends with a comma inside the quote followed by an em dash. For clearer punctuation, consider moving the comma outside or rephrasing:- "We’d love to run a workshop or AsyncAPI session in our community,”—please reach out. + "We’d love to run a workshop or AsyncAPI session in our community"—please reach out.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-singapore-conf-summary.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-singapore-conf-summary.md
[style] ~43-~43: ‘filled to capacity’ might be wordy. Consider a shorter alternative.
Context: ...th overwhelming interest. Sessions were filled to capacity, with attendees eager to explore the nu...
(EN_WORDINESS_PREMIUM_FILLED_TO_CAPACITY)
[uncategorized] ~129-~129: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...reminder: AsyncAPI is no longer just an open source project—it’s a global movement. Being i...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~141-~141: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ue/Bangalore) - [Online 🌐: October 29, 2025](https://conference.asyncapi.com/venue/...
(MISSING_COMMA_AFTER_YEAR)
⏰ Context from checks skipped due to timeout of 180000ms (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
There was a problem hiding this comment.
@iambami, please limit the use of dashes and use the appropriate punctuation in your sentences. It's challenging to review the blog as it is.
Additionally, please reduce the image sizes using https://squoosh.app/.
Take the time to proofread the blog. We want to merge it quickly, but let's do it correctly.
Check your heading formatting, ensure the images are showing, and consider combining some paragraphs, such as "What This Means for Us" with "What's Next."
It's better to have a shorter but more detailed article.
Lastly, please check the preview #4056 (comment)
I will provide another round of feedback once you have made the changes.
What do you mean "and use the appropriate punctuation in your sentences"? An em dash (-) is not appropriate, or do you have something against it? Also, heading formatting, how? All my headings are on heading 2. Is there something we use here that I'm missing? Because you mention this same thing in the marketing report, PR, and I'm confused as to what needs formatting. Headings and subheadings take the appropriate and consistent headlines. Care to explain? @thulieblack |
|
Open the deployment preview and see how your article looks like, then you'll understand the review I just gave you #4056 (comment) The same with the marketing one @derberg already shared the same review and included the screenshot Here is a screenshot of your blog currently Why are there dashes on the headings maybe if you can explain the logic. There are missing images. |
|
What is wrong with this? 
|
|
Or this heading. Because I'm not sure what I'm supposed to format it to. 
|
There was a problem hiding this comment.
Actionable comments posted: 3
♻️ Duplicate comments (1)
markdown/blog/2025-singapore-conf-summary.md (1)
60-63: The caption "Tamimi presenting the Untapped Potentials of AsyncAPI Studio." already reflects the corrected grammar from previous reviews.
🧹 Nitpick comments (5)
markdown/blog/2025-singapore-conf-summary.md (5)
43-43: Optional: simplify phrase for brevity.
The phrase "filled to capacity" can be shortened for conciseness. For example:- Sessions were filled to capacity, with attendees eager to explore the nuances... + Sessions were full, with attendees eager to explore the nuances...This makes the sentence more direct without losing meaning.
🧰 Tools
🪛 LanguageTool
[style] ~43-~43: ‘filled to capacity’ might be wordy. Consider a shorter alternative.
Context: ...th overwhelming interest. Sessions were filled to capacity, with attendees eager to explore the nu...(EN_WORDINESS_PREMIUM_FILLED_TO_CAPACITY)
129-129: Add comma for compound question.
In the heading, insert a comma before "and" to separate the two clauses clearly:- ## What This Means for Us And What’s Next? + ## What This Means for Us, and What’s Next?🧰 Tools
🪛 LanguageTool
[uncategorized] ~129-~129: Use a comma before ‘And’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...f that story. ## What This Means for Us And What’s Next? This event was a reminder...(COMMA_COMPOUND_SENTENCE_2)
130-131: Hyphenate compound adjectives.
Please hyphenate the following for consistency:
- "open source project" → "open-source project"
- "real world challenges" → "real-world challenges"
Proposed diff:
- AsyncAPI is no longer just an open source project, it’s a global movement. Being in Singapore meant ... solve real world challenges. + AsyncAPI is no longer just an open-source project, it’s a global movement. Being in Singapore meant ... solve real-world challenges.🧰 Tools
🪛 LanguageTool
[uncategorized] ~131-~131: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...reminder: AsyncAPI is no longer just an open source project, it’s a global movement. Being ...(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~131-~131: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...d how our tools and standards can solve real world challenges. It also sets the tone for ...(EN_COMPOUND_ADJECTIVE_INTERNAL)
14-14: Hyphenate "first-ever" in excerpt.
In the excerpt, “first ever” should be hyphenated as “first-ever”:- …the first ever AsyncAPI presence at an APIDays event in Asia. + …the first-ever AsyncAPI presence at an APIDays event in Asia.
24-24: Adjust bold formatting around "Singapore".
Move the period outside the bold tags for consistency with other emphasis usage:- …somewhere new: **Singapore.** + …somewhere new: **Singapore**.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-singapore-conf-summary.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-singapore-conf-summary.md
[uncategorized] ~35-~35: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...ing Tomorrow's Intelligent Ecosystems," providing an excellent platform to introduce Asyn...
(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)
[style] ~43-~43: ‘filled to capacity’ might be wordy. Consider a shorter alternative.
Context: ...th overwhelming interest. Sessions were filled to capacity, with attendees eager to explore the nu...
(EN_WORDINESS_PREMIUM_FILLED_TO_CAPACITY)
[uncategorized] ~129-~129: Use a comma before ‘And’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...f that story. ## What This Means for Us And What’s Next? This event was a reminder...
(COMMA_COMPOUND_SENTENCE_2)
[uncategorized] ~131-~131: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...reminder: AsyncAPI is no longer just an open source project, it’s a global movement. Being ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~131-~131: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...d how our tools and standards can solve real world challenges. It also sets the tone for ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~143-~143: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ue/Bangalore) - [Online 🌐: October 29, 2025](https://conference.asyncapi.com/venue/...
(MISSING_COMMA_AFTER_YEAR)
[uncategorized] ~165-~165: There should be a space after a closing quote.
Context: ...op or AsyncAPI session in our community,”please reach out. We’d love to support you. U...
(NO_SPACE_CLOSING_QUOTE)
| ## First Time in Southeast Asia | ||
|
|
||
| There’s something special about firsts. The first version of a spec. The first contributor. The first working group. The first time you explain what “event-driven” means to someone and see the lightbulb go off. This made us ecstatic to kick off the AsyncAPI conference in Singapore. | ||
| On April 15–16, the AsyncAPI Conference was part of the [APIDays Singapore](https://www.apidays.global/singapore/) track. The event, themed "Where APIs Meet AI: Building Tomorrow's Intelligent Ecosystems," providing an excellent platform to introduce AsyncAPI to the vibrant Asia-Pacific developer community. |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Rewrite dangling participle for clarity.
The clause "providing an excellent platform" lacks a clear subject and reads as a dangling participle. Consider changing it to "provided an excellent platform" to improve grammar.
Proposed diff:
- The event, themed "Where APIs Meet AI: Building Tomorrow's Intelligent Ecosystems," providing an excellent platform to introduce AsyncAPI to the vibrant Asia-Pacific developer community.
+ The event, themed "Where APIs Meet AI: Building Tomorrow's Intelligent Ecosystems," provided an excellent platform to introduce AsyncAPI to the vibrant Asia-Pacific developer community.📝 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.
| On April 15–16, the AsyncAPI Conference was part of the [APIDays Singapore](https://www.apidays.global/singapore/) track. The event, themed "Where APIs Meet AI: Building Tomorrow's Intelligent Ecosystems," providing an excellent platform to introduce AsyncAPI to the vibrant Asia-Pacific developer community. | |
| On April 15–16, the AsyncAPI Conference was part of the [APIDays Singapore](https://www.apidays.global/singapore/) track. The event, themed "Where APIs Meet AI: Building Tomorrow's Intelligent Ecosystems," provided an excellent platform to introduce AsyncAPI to the vibrant Asia-Pacific developer community. |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~35-~35: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...ing Tomorrow's Intelligent Ecosystems," providing an excellent platform to introduce Asyn...
(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (11)
markdown/blog/2025-singapore-conf-summary.md (11)
30-34: Alt text handled via caption prop.
Per theFigurecomponent’s implementation, thecaptionprop is used as thealtattribute whenaltOnlyisn’t provided. No additionalaltprop is needed here.
41-45: Alt text handled via caption prop.
63-67: Alt text handled via caption prop.
73-77: Alt text handled via caption prop.
83-87: Alt text handled via caption prop.
96-101: Question bullets formatting is intentional.
As discussed, the mix of statement vs. question formats is correct per the author’s intent.
105-109: Alt text handled via caption prop.
116-120: Alt text handled via caption prop.
137-141: Alt text handled via caption prop.
126-127:⚠️ Potential issueFix sentence fragment.
The standalone “Conference designed to bring together…” reads as a fragment. Consider merging it with the preceding sentence or adding a verb:-It also sets the tone for the rest of 2025. ... global community building. -Conference designed to bring together developers... +It also sets the tone for the rest of 2025, setting the stage for conferences designed to bring together developers, architects, technical writers, DevRel folks, and API enthusiasts passionate about the future of event-driven APIs.
38-40:⚠️ Potential issueFix verb form for grammatical correctness.
The clause reads as a fragment due to the gerund “providing.” Change it to past tense:-On April 15–16, the AsyncAPI Conference was part of the [APIDays Singapore]... "Where APIs Meet AI..." providing an excellent platform to introduce AsyncAPI... +On April 15–16, the AsyncAPI Conference was part of the [APIDays Singapore]... "Where APIs Meet AI..." provided an excellent platform to introduce AsyncAPI...
🧹 Nitpick comments (6)
markdown/blog/2025-singapore-conf-summary.md (6)
14-14: Hyphenate compound adjective in excerpt.
Consider hyphenating "first-ever" in the excerpt to follow compound adjective style:-excerpt: "AsyncAPI kicked off its 2025 conference with a packed track at APIDays Singapore—the first ever AsyncAPI presence at an APIDays event in Asia." +excerpt: "AsyncAPI kicked off its 2025 conference with a packed track at APIDays Singapore—the first-ever AsyncAPI presence at an APIDays event in Asia."
111-115: Community growth bullet list reads well.
The metrics are informative, though consider consolidating “Slack community” mentions to avoid repetition.
130-136: Use en dash for date ranges.
For consistency, replace hyphens in date ranges with en dashes:-[Bengaluru 🇮🇳: October 8-9, 2025] +[Bengaluru 🇮🇳: October 8–9, 2025]Repeat similar changes for other multi-day ranges if needed.
🧰 Tools
🪛 LanguageTool
[style] ~134-~134: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ue/Bangalore) - [Online 🌐: October 29, 2025](https://conference.asyncapi.com/venue/...(MISSING_COMMA_AFTER_YEAR)
143-145: Warm closing is effective.
Consider adding a comma in “see you, Asia-Pacific!” for direct address clarity:-Until next time, see you Asia-Pacific! +Until next time, see you, Asia-Pacific!
156-156: Punctuation around quotes.
You may want to move the comma inside the closing quotation mark for US style consistency:-And if you're in Asia and thinking, "We’d love to run a workshop or AsyncAPI session in our community,” please reach out. +And if you're in Asia and thinking, "We’d love to run a workshop or AsyncAPI session in our community," please reach out.
157-157: Add comma for direct address.
Consider:-Until next time, see you Asia-Pacific! +Until next time, see you, Asia-Pacific!
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-singapore-conf-summary.md(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
markdown/blog/2025-singapore-conf-summary.md (1)
Learnt from: thulieblack
PR: asyncapi/website#4056
File: markdown/blog/2025-singapore-conf-summary.md:26-30
Timestamp: 2025-04-25T10:47:37.468Z
Learning: In the website's custom Figure component, the caption text is automatically used as alt text for images when no specific altOnly prop is provided. The component sets alt text using: const alt = altOnly || caption; This ensures basic image accessibility for screen readers.
🪛 LanguageTool
markdown/blog/2025-singapore-conf-summary.md
[uncategorized] ~122-~122: Use a comma before ‘And’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...xt-center" /> ## What This Means for Us And What’s Next? This event was a reminder...
(COMMA_COMPOUND_SENTENCE_2)
[uncategorized] ~124-~124: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...reminder: AsyncAPI is no longer just an open source project; it’s a global movement. Being ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~134-~134: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ue/Bangalore) - [Online 🌐: October 29, 2025](https://conference.asyncapi.com/venue/...
(MISSING_COMMA_AFTER_YEAR)
⏰ Context from checks skipped due to timeout of 180000ms (3)
- GitHub Check: Redirect rules - asyncapi-website
- GitHub Check: Header rules - asyncapi-website
- GitHub Check: Pages changed - asyncapi-website
🔇 Additional comments (18)
markdown/blog/2025-singapore-conf-summary.md (18)
8-8: Optimize cover image for web performance.
The cover image (/img/posts/marketing-images/singapore-conf/singapore-header.webp) looks great, but please ensure it's compressed and resized appropriately (e.g., via https://squoosh.app/) to minimize load times.
19-21: Clear and engaging opening question.
The use of curly quotation marks and emphasis on the guiding question is spot-on and aligns with the editorial style.
22-23: Strong narrative continuation.
The transition from the opening question to the historical context is clear and compelling.
24-25: Concise community-building message.
The phrasing effectively highlights AsyncAPI’s community focus and progression.
26-27: Sponsor acknowledgment is well-placed.
Crediting the APIDays Singapore team here appropriately highlights the partnership.
28-29: Solid reinforcement of APIDays partnership.
The sentence underscores the event’s significance and reads smoothly.
36-37: Consistent H2 section heading.
The “First Time in Southeast Asia” header uses appropriate hierarchy and clarity.
47-48: Audience enthusiasm effectively conveyed.
The paragraph captures the high interest and relevance succinctly.
49-50: Section header is clear and engaging.
Landing “What We Shared And What We Learned” sets expectations nicely.
51-58: Detailed recap of the opening talk.
The description of Naresh Jain’s session is informative and well-contextualized.
59-62: Clear summary of Tamimi Ahmad’s session.
The focus on AsyncAPI Studio capabilities is articulated clearly.
69-72: Effective explanation of Kafka security talk.
Hugo Guerrero’s key points are summarized accurately.
79-82: Concise preview of AsyncAPI v3 features.
Ankit Kumar’s segment is summarized with clarity and context.
89-94: Bulleted highlights are clear.
The list of key takeaways is well-structured and easy to scan.
103-104: Strong transition and conclusion of session insights.
This sentence nicely captures the pivotal nature of the conference moments.
122-123: Engaging section header.
The header effectively tees up the “What This Means for Us And What’s Next?” content.🧰 Tools
🪛 LanguageTool
[uncategorized] ~122-~122: Use a comma before ‘And’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...xt-center" /> ## What This Means for Us And What’s Next? This event was a reminder...(COMMA_COMPOUND_SENTENCE_2)
124-126: Solid framing of future outlook.
The paragraph conveys direction and momentum effectively.🧰 Tools
🪛 LanguageTool
[uncategorized] ~124-~124: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...reminder: AsyncAPI is no longer just an open source project; it’s a global movement. Being ...(EN_COMPOUND_ADJECTIVE_INTERNAL)
146-155: Call-to-action links are clear.
The list of next steps (Slack, Docs, Studio, GitHub) is concise and actionable.
|
@TRohit20 @akshatnema please review for merging. |
|
Hello folks, Are there any other changes we want to see on this PR? |
|
Will run a final review and make the necessary changes if any then approve in 24 hrs. Thank you @iambami |
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (1)
markdown/blog/2025-singapore-conf-summary.md (1)
38-40: 🛠️ Refactor suggestionFix dangling participle in event description
The sentence “The event, themed …, providing an excellent platform to introduce AsyncAPI…” is a fragment. Consider changing “providing” to “provided” so it reads as a complete sentence.- On April 15–16, the AsyncAPI Conference was part of the [APIDays Singapore](https://www.apidays.global/singapore/) track. The event, themed "Where APIs Meet AI: Building Tomorrow's Intelligent Ecosystems", providing an excellent platform to introduce AsyncAPI to the vibrant Asia-Pacific community. + On April 15–16, the AsyncAPI Conference was part of the [APIDays Singapore](https://www.apidays.global/singapore/) track. The event, themed "Where APIs Meet AI: Building Tomorrow's Intelligent Ecosystems", provided an excellent platform to introduce AsyncAPI to the vibrant Asia-Pacific community.🧰 Tools
🪛 LanguageTool
[uncategorized] ~39-~39: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...ing Tomorrow's Intelligent Ecosystems", providing an excellent platform to introduce Asyn...(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)
🧹 Nitpick comments (5)
markdown/blog/2025-singapore-conf-summary.md (5)
103-104: Improve sentence clarity and punctuation
This line joins two independent clauses with a comma, creating a run-on. Replace the comma after “act” with a semicolon (or split into two sentences) to improve readability.- We sensed not just curiosity, but a real readiness to act, this wasn’t just a learning moment; for many, it was a turning point. + We sensed not just curiosity, but a real readiness to act; this wasn’t just a learning moment. For many, it was a turning point.
122-122: Adjust heading punctuation and capitalization
In your heading, “And” doesn’t need to be uppercase. Also, titles usually omit commas before “and” or use lowercase for conjunctions. Consider:- ## What This Means for Us And What’s Next? + ## What This Means for Us and What’s Next?🧰 Tools
🪛 LanguageTool
[uncategorized] ~122-~122: Use a comma before ‘And’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...xt-center" /> ## What This Means for Us And What’s Next? This event was a reminder...(COMMA_COMPOUND_SENTENCE_2)
126-127: Resolve sentence fragment in closing section
The phrase “Conference designed to bring together developers…” lacks a subject and verb. It can be integrated into the previous sentence or rewritten. Example refactor:- It also sets the tone for the rest of 2025. With conferences scheduled for Munich, Lagos, London, Bengaluru, online, and Paris, this marked our first step in a year of global community building. Conference designed to bring together developers, architects, technical writers, DevRel folks, and API enthusiasts who are passionate about the future of event-driven APIs. + It also sets the tone for the rest of 2025: with conferences scheduled for Munich, Lagos, London, Bengaluru, online, and Paris, this marks our first step in a year of global community building designed to bring together developers, architects, technical writers, DevRel folks, and API enthusiasts who are passionate about the future of event-driven APIs.
97-101: Unify quotation mark styles in Q&A bullets
The bullets mix straight (") and curly (“”) quotes. For consistency, choose one style—ideally curly quotes—and ensure question marks are correctly placed only on questions.- - "Tell me more about AsyncAPI" - - “How do I introduce AsyncAPI into our hybrid systems?” - - “Can I use this with Kafka and MQTT?” - - “How do we contribute to the spec or tooling?” - - "How do other AsyncAPI adopters use AsyncAPI?" + - “Tell me more about AsyncAPI” + - “How do I introduce AsyncAPI into our hybrid systems?” + - “Can I use this with Kafka and MQTT?” + - “How do we contribute to the spec or tooling?” + - “How do other AsyncAPI adopters use AsyncAPI?”
133-133: Standardize date‐range formatting
The Bengaluru entry uses a hyphen (8-9), while others use an en dash (2–3). For consistency, switch to an en dash and ensure the date ranges are uniform:- - [Bengaluru 🇮🇳: October 8-9, 2025](https://conference.asyncapi.com/venue/Bangalore) + - [Bengaluru 🇮🇳: October 8–9, 2025](https://conference.asyncapi.com/venue/Bangalore)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-singapore-conf-summary.md(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
markdown/blog/2025-singapore-conf-summary.md (1)
Learnt from: thulieblack
PR: asyncapi/website#4056
File: markdown/blog/2025-singapore-conf-summary.md:26-30
Timestamp: 2025-04-25T10:47:37.468Z
Learning: In the website's custom Figure component, the caption text is automatically used as alt text for images when no specific altOnly prop is provided. The component sets alt text using: const alt = altOnly || caption; This ensures basic image accessibility for screen readers.
🪛 LanguageTool
markdown/blog/2025-singapore-conf-summary.md
[uncategorized] ~39-~39: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...ing Tomorrow's Intelligent Ecosystems", providing an excellent platform to introduce Asyn...
(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)
[uncategorized] ~122-~122: Use a comma before ‘And’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...xt-center" /> ## What This Means for Us And What’s Next? This event was a reminder...
(COMMA_COMPOUND_SENTENCE_2)
[uncategorized] ~124-~124: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...reminder: AsyncAPI is no longer just an open source project; it’s a global movement. Being ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~134-~134: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ue/Bangalore) - [Online 🌐: October 29, 2025](https://conference.asyncapi.com/venue/...
(MISSING_COMMA_AFTER_YEAR)
⏰ Context from checks skipped due to timeout of 180000ms (1)
- GitHub Check: Test NodeJS PR - macos-13
|
@iambami, please change the date to the 12th. |
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
markdown/blog/2025-singapore-conf-summary.md (1)
39-40: Fix dangling participle and punctuation around the event theme
The phrase “providing an excellent platform” reads as a dangling participle. Additionally, the comma should be inside the closing quote for the theme.
Proposed rewrite:- On April 15–16, the AsyncAPI Conference was part of the [APIDays Singapore](...) track. The event, themed "Where APIs Meet AI: Building Tomorrow's Intelligent Ecosystems", providing an excellent platform to introduce AsyncAPI to the vibrant Asia-Pacific community. + On April 15–16, the AsyncAPI Conference was part of the [APIDays Singapore](...) track. The event, themed "Where APIs Meet AI: Building Tomorrow's Intelligent Ecosystems," provided an excellent platform to introduce AsyncAPI to the vibrant Asia-Pacific community.🧰 Tools
🪛 LanguageTool
[uncategorized] ~39-~39: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...ing Tomorrow's Intelligent Ecosystems", providing an excellent platform to introduce Asyn...(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)
🧹 Nitpick comments (5)
markdown/blog/2025-singapore-conf-summary.md (5)
1-15: Consider adding aslugfield for SEO and routing consistency
While the filename serves as the URL, explicitly defining aslug:in the frontmatter (e.g.,slug: bringing-asyncapi-forefront-apidays-singapore) ensures consistent routing and metadata for your blog templates and improves SEO.
49-49: Title-case consistency: lowercase short conjunction in heading
In most title‐case conventions, short conjunctions like “and” are not capitalized. Consider updating:- ## What We Shared And What We Learned + ## What We Shared and What We Learned
122-122: Title-case consistency in the closing section heading
Similarly, update “And” to lowercase in the next H2:- ## What This Means for Us And What’s Next? + ## What This Means for Us and What’s Next?🧰 Tools
🪛 LanguageTool
[uncategorized] ~122-~122: Use a comma before ‘And’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...xt-center" /> ## What This Means for Us And What’s Next? This event was a reminder...(COMMA_COMPOUND_SENTENCE_2)
156-157: Consistent quotation punctuation in call-to-action
The comma following the closing quotation mark should be inside the quotes. Update to:- And if you're in Asia and thinking, "We’d love to run a workshop or AsyncAPI session in our community,” please reach out. + And if you're in Asia and thinking, "We’d love to run a workshop or AsyncAPI session in our community," please reach out.
158-159: Add missing comma for direct address
In “Until next time, see you Asia-Pacific!”, insert a comma before “Asia-Pacific” for correct vocative punctuation.- Until next time, see you Asia-Pacific! + Until next time, see you, Asia-Pacific!
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-singapore-conf-summary.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-singapore-conf-summary.md
[uncategorized] ~39-~39: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...ing Tomorrow's Intelligent Ecosystems", providing an excellent platform to introduce Asyn...
(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)
[uncategorized] ~122-~122: Use a comma before ‘And’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...xt-center" /> ## What This Means for Us And What’s Next? This event was a reminder...
(COMMA_COMPOUND_SENTENCE_2)
[uncategorized] ~124-~124: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...reminder: AsyncAPI is no longer just an open source project; it’s a global movement. Being ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~134-~134: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ue/Bangalore) - [Online 🌐: October 29, 2025](https://conference.asyncapi.com/venue/...
(MISSING_COMMA_AFTER_YEAR)
⏰ Context from checks skipped due to timeout of 180000ms (1)
- GitHub Check: Test NodeJS PR - macos-13
|
|
||
| This event was a reminder: AsyncAPI is no longer just an open source project; it’s a global movement. Being in Singapore meant expanding our reach, connecting with new markets, and hearing firsthand how our tools and standards can solve real-world challenges. | ||
|
|
||
| It also sets the tone for the rest of 2025. With conferences scheduled for Munich, Lagos, London, Bengaluru, online, and Paris, this marked our first step in a year of global community building. Conference designed to bring together developers, architects, technical writers, DevRel folks, and API enthusiasts who are passionate about the future of event-driven APIs. |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Resolve sentence fragment in closing paragraph
The clause “Conference designed to bring together developers…” lacks a clear subject. Merge it with the previous sentence or add a verb for clarity. For example:
It also sets the tone for the rest of 2025. With conferences scheduled for Munich, Lagos, London, Bengaluru, online, and Paris, this marked our first step in a year of global community building—a conference designed to bring together developers, architects, technical writers, DevRel folks, and API enthusiasts who are passionate about the future of event-driven APIs.
There was a problem hiding this comment.
These images are very large. Can't we limit the usage of images in blogs or use the existing images inside the repo? This will increase the size with time.
cc: @thulieblack @derberg
There was a problem hiding this comment.
Hey @akshatnema
The images were all resized using https://squoosh.app/.
And tbh, this PR has been sitting here for too long.
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (2)
markdown/blog/2025-singapore-conf-summary.md (2)
39-40:⚠️ Potential issueFix sentence fragment and punctuation
The phrase…Building Tomorrow's Intelligent Ecosystems", providing an excellent platform…
is both missing a comma after the closing quote and reads as a fragment. It should be a complete sentence:- On April 15–16, the AsyncAPI Conference was part of the [APIDays Singapore](https://www.apidays.global/singapore/) track. The event, themed "Where APIs Meet AI: Building Tomorrow's Intelligent Ecosystems", providing an excellent platform to introduce AsyncAPI to the vibrant Asia-Pacific community. + On April 15–16, the AsyncAPI Conference was part of the [APIDays Singapore](https://www.apidays.global/singapore/) track. The event, themed "Where APIs Meet AI: Building Tomorrow's Intelligent Ecosystems," provided an excellent platform to introduce AsyncAPI to the vibrant Asia-Pacific community.🧰 Tools
🪛 LanguageTool
[uncategorized] ~39-~39: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...ing Tomorrow's Intelligent Ecosystems", providing an excellent platform to introduce Asyn...(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)
126-126: 🛠️ Refactor suggestionMerge sentence fragment into previous sentence
The standalone fragment “Conference designed to bring together developers…” lacks a subject. Combine it with the previous line:- …this marked our first step in a year of global community building. Conference designed to bring together developers, architects, technical writers, DevRel folks, and API enthusiasts who are passionate about the future of event-driven APIs. + …this marked our first step in a year of global community building—a conference designed to bring together developers, architects, technical writers, DevRel folks, and API enthusiasts who are passionate about the future of event-driven APIs.
🧹 Nitpick comments (6)
markdown/blog/2025-singapore-conf-summary.md (6)
103-103: Split comma splice into two sentences
The line currently uses a comma to join two independent clauses:We sensed not just curiosity, but a real readiness to act, this wasn’t just a learning moment; for many, it was a turning point.It should be:
- We sensed not just curiosity, but a real readiness to act, this wasn’t just a learning moment; for many, it was a turning point. + We sensed not just curiosity, but a real readiness to act. This wasn’t just a learning moment; for many, it was a turning point.
113-113: Reduce redundancy in community bullet
You mention “Slack” twice in the same sentence. Consider simplifying for clarity:- Welcomed over 20 new faces to our Slack and GitHub communities, though we also noticed some hesitation to join the Slack community. + Welcomed over 20 new faces to our Slack and GitHub communities, though we noticed some hesitation to join.
124-124: Hyphenate “open source” as a compound adjective
Before a noun, “open source” should be hyphenated:- AsyncAPI is no longer just an open source project; + AsyncAPI is no longer just an open-source project;🧰 Tools
🪛 LanguageTool
[uncategorized] ~124-~124: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...reminder: AsyncAPI is no longer just an open source project; it’s a global movement. Being ...(EN_COMPOUND_ADJECTIVE_INTERNAL)
137-141: Optimize image asset sizes
To improve page load times, please ensure all.webpimages are compressed (e.g., via https://squoosh.app/) without degrading visual quality.Also applies to: 30-34, 41-45, 53-57, 63-67, 73-77, 83-87, 105-109, 116-120
122-122: Optional: Add comma in heading for compound structure
Depending on your style guide, you may prefer:- ## What This Means for Us And What’s Next? + ## What This Means for Us, and What’s Next?This is purely stylistic.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~122-~122: Use a comma before ‘And’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...xt-center" /> ## What This Means for Us And What’s Next? This event was a reminder...(COMMA_COMPOUND_SENTENCE_2)
158-158: Add missing preposition for clarity
The closing line reads “see you Asia-Pacific!” but should be:- Until next time, see you Asia-Pacific! + Until next time, see you in Asia-Pacific!
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-singapore-conf-summary.md(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
markdown/blog/2025-singapore-conf-summary.md (1)
Learnt from: thulieblack
PR: asyncapi/website#4056
File: markdown/blog/2025-singapore-conf-summary.md:26-30
Timestamp: 2025-04-25T10:47:37.468Z
Learning: In the website's custom Figure component, the caption text is automatically used as alt text for images when no specific altOnly prop is provided. The component sets alt text using: const alt = altOnly || caption; This ensures basic image accessibility for screen readers.
🪛 LanguageTool
markdown/blog/2025-singapore-conf-summary.md
[uncategorized] ~39-~39: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...ing Tomorrow's Intelligent Ecosystems", providing an excellent platform to introduce Asyn...
(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)
[uncategorized] ~122-~122: Use a comma before ‘And’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...xt-center" /> ## What This Means for Us And What’s Next? This event was a reminder...
(COMMA_COMPOUND_SENTENCE_2)
[uncategorized] ~124-~124: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...reminder: AsyncAPI is no longer just an open source project; it’s a global movement. Being ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~134-~134: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ue/Bangalore) - [Online 🌐: October 29, 2025](https://conference.asyncapi.com/venue/...
(MISSING_COMMA_AFTER_YEAR)
| @@ -0,0 +1,158 @@ | |||
| --- | |||
| title: "Bringing Asynchronous APIs to the Forefront at APIDays Singapore" | |||
| date: 2025-05-26T06:00:00+01:00 | |||
There was a problem hiding this comment.
🛠️ Refactor suggestion
Update publication date as requested by content team
thulieblack requested changing the blog date to the 12th for consistency with the release schedule. Please update the date field accordingly.
Suggested diff:
- date: 2025-05-26T06:00:00+01:00
+ date: 2025-05-12T06:00:00+01:00📝 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.
| date: 2025-05-26T06:00:00+01:00 | |
| date: 2025-05-12T06:00:00+01:00 |
🤖 Prompt for AI Agents
In markdown/blog/2025-singapore-conf-summary.md at line 3, the date field is
currently set to 2025-05-26T06:00:00+01:00 but needs to be updated to the 12th
of May for consistency with the release schedule. Change the date value to
2025-05-12T06:00:00+01:00 to reflect the correct publication date as requested
by the content team.
There was a problem hiding this comment.
@thulieblack Can you please confirm that?
There was a problem hiding this comment.
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!
|
/rtm |
Co-authored-by: Atinuke Oluwabamikemi Kayode <[email protected]> Co-authored-by: V Thulisile Sibanda <[email protected]> Co-authored-by: Rohit <[email protected]> Co-authored-by: akshatnema <[email protected]>
Hey folks,
This is the Singapore conference summary. It should be added to the April community update going out next week, so I would appreciate the earliest and quickest review. 🤗
Thank you 🙏
@derberg @TRohit20 @thulieblack @AceTheCreator
Summary by CodeRabbit