-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
chore(blog): add the August summary #4370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
WalkthroughAdds a new August 2025 community summary blog post and removes the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
✨ 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/Issue comments)Type Other keywords and placeholders
Status, Documentation and Community
|
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-4370--asyncapi-website.netlify.app/ |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4370 +/- ##
=========================================
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:
|
There was a problem hiding this 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 (7)
markdown/blog/2025-august-summary.md (7)
67-67: Grammar and spacing fixes.
- Use “etc.” with a period.
- Add missing space before link text (MD039).
-... ambassadors, maintainers, etc, it made the onboarding ... -... is now part of the[ community content bucket, live on the AsyncAPI website] ... +... ambassadors, maintainers, etc., it made the onboarding ... +... is now part of the [community content bucket, live on the AsyncAPI website] ...
72-85: Number formatting consistency in analytics tables.Use thousands separators consistently to improve readability.
-... over **68 036 sessions** and **22 456 new users** ... +... over **68,036 sessions** and **22,456 new users** ...And similarly in table cells (e.g.,
12,909,18,576,9,728,1,881,18,331,7,034).
111-114: Typo: “AsyncPI” → “AsyncAPI”.Fix the closing bullet.
-... you'll find some of our AsyncPI experts and maintainers. +... you'll find some of our AsyncAPI experts and maintainers.
1-15: Publication date check (scheduled vs. month covered).Front matter date is 2025-09-04T06:00:00+01:00 while the post covers August. That’s okay if this is the planned publish date. Confirm scheduling so it doesn’t appear before September 4 in other time zones.
I can scan the repo for prior monthly posts to ensure date consistency if helpful.
7-14: Cover image is good; consider alt/credit metadata if supported.If the blog template supports
coverAlt/coverCredit, add them for accessibility and attribution. Also ensure the cover is part of the site’s image optimization pipeline to improve LCP.
19-25: Lighthouse perf score 41: image quick wins inside this post.
- Use WebP/AVIF for sponsor logo (already suggested).
- Ensure the cover is appropriately sized for the largest viewport and preloaded if it’s the LCP.
- Avoid fixed pixel width attributes in HTML that force upscaling on large screens.
76-85: Table rendering robustness.Some Markdown renderers are picky. Add a blank line before each table (and after the preceding paragraph) and ensure each header row and separator line align. You already have one before the first table; add one before the second to be safe.
-We can also see below the analytics of the onboarding and style guide docs, after completing the reorganisation work on the community repository from August 5, 2025, to August 29, 2025. +We can also see below the analytics of the onboarding and style guide docs, after completing the reorganisation work on the community repository from August 5, 2025, to August 29, 2025. + | Community Bucket | Page Views | Users|Also applies to: 88-92
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (2)
markdown/blog/2025-august-summary.md(1 hunks)markdown/blog/2025-july-summary.md(0 hunks)
💤 Files with no reviewable changes (1)
- markdown/blog/2025-july-summary.md
🧰 Additional context used
🧠 Learnings (1)
📓 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.
🪛 LanguageTool
markdown/blog/2025-august-summary.md
[style] ~67-~67: In American English, abbreviations like “etc.” require a period.
Context: ...contributors, ambassadors, maintainers, etc, it made the onboarding experience not ...
(ETC_PERIOD)
[grammar] ~67-~67: There might be a mistake here.
Context: ...capi.com/docs/community/000-onboarding). 3. Complete the AsyncAPI Style Guide: As ...
(QB_NEW_EN)
[grammar] ~76-~76: There might be a mistake here.
Context: ...ontent Bucket | Sessions | New Users | |------------------|----------|---------...
(QB_NEW_EN)
[grammar] ~77-~77: There might be a mistake here.
Context: ...-------------|----------|--------------| | /docs/concepts | 12 909 | 2 898 | ...
(QB_NEW_EN)
[grammar] ~78-~78: There might be a mistake here.
Context: ... | /docs/concepts | 12 909 | 2 898 | | /docs/tutorials| 18 576 | 7 435 | ...
(QB_NEW_EN)
[grammar] ~79-~79: There might be a mistake here.
Context: ... | /docs/tutorials| 18 576 | 7 435 | | /docs/tools | 9 728 | 2 647 | ...
(QB_NEW_EN)
[grammar] ~80-~80: There might be a mistake here.
Context: ... | /docs/tools | 9 728 | 2 647 | | /docs/guides | 1 881 | 548 | ...
(QB_NEW_EN)
[grammar] ~81-~81: There might be a mistake here.
Context: ... | /docs/guides | 1 881 | 548 | | /docs/reference| 18 331 | 7 034 | ...
(QB_NEW_EN)
[grammar] ~82-~82: There might be a mistake here.
Context: ... | /docs/reference| 18 331 | 7 034 | | /docs/migration| 891 | 253 | ...
(QB_NEW_EN)
[grammar] ~83-~83: There might be a mistake here.
Context: ... | /docs/migration| 891 | 253 | | /docs/community| 329 | 131 | ...
(QB_NEW_EN)
[grammar] ~94-~94: There might be a mistake here.
Context: ...1 | 331 | ## Maintainership Program We are officially on the road to Maintai...
(QB_NEW_EN)
[grammar] ~103-~103: There might be a mistake here.
Context: ...cAPI TSC members. <Profiles profiles={[ { name: 'Adi Boghawala', avatar:...
(QB_NEW_EN)
[grammar] ~108-~108: There might be a mistake here.
Context: ...nk: 'https://www.github.com/Adi-204' } ]} /> ## Coming in September - **AsyncA...
(QB_NEW_EN)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2025-august-summary.md
67-67: Spaces inside link text
(MD039, no-space-in-links)
⏰ 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 (1)
markdown/blog/2025-august-summary.md (1)
31-34: Verify promo code and confirm CFP deadlines
File: markdown/blog/2025-august-summary.md lines 31–34
CFP deadlines are accurate: Online Conference closes Sep 7 2025; Paris Edition closes Oct 5 2025 (select “AsyncAPI” track); Summit at DevWeek 2026 closes Nov 7 2025. Promo code “AsyncAPIVIP” could not be verified—please test the Apidays London registration flow or contact organizers to confirm it still grants a free Regular ticket.
|
lgtm |
markdown/blog/2025-august-summary.md
Outdated
| And I'm very excited to share what we have achieved so far. | ||
|
|
||
| 1. **Community to Website Repo Workflow**: To achieve our goal of integrating community documentation onto the website, we needed a workflow that automatically pushes all merged documents from the community repository to the website and deploys them live. [Animesh Kumar](https://github.com/animeshk923) led this contribution, [and we now have a functioning workflow in place](https://github.com/asyncapi/community/blob/master/.github/workflows/update-docs-in-website.yml). | ||
| 2. **Expand Community Documentation**: Due to the lack of enough onboarding materials for the diverse roles we have in the community, such as documentation contributors, code contributors, ambassadors, maintainers, etc, it made the onboarding experience not efficient, and to reduce the number of onboarding calls, [Anton Zolotukhin](https://www.linkedin.com/in/mister-gold) and I co-mentored as part of the 2024 Mentorship Program. The hard work of [Ezinne Anne Emilia](https://github.com/ezinneanne) and [Prince Onyeanuna](https://github.com/Aahil13), is now part of the[ community content bucket, live on the AsyncAPI website](https://www.asyncapi.com/docs/community/000-onboarding). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 2. **Expand Community Documentation**: Due to the lack of enough onboarding materials for the diverse roles we have in the community, such as documentation contributors, code contributors, ambassadors, maintainers, etc, it made the onboarding experience not efficient, and to reduce the number of onboarding calls, [Anton Zolotukhin](https://www.linkedin.com/in/mister-gold) and I co-mentored as part of the 2024 Mentorship Program. The hard work of [Ezinne Anne Emilia](https://github.com/ezinneanne) and [Prince Onyeanuna](https://github.com/Aahil13), is now part of the[ community content bucket, live on the AsyncAPI website](https://www.asyncapi.com/docs/community/000-onboarding). | |
| 2. **Expand Community Documentation**: We lacked sufficient onboarding materials for diverse roles like documentation and code contributors, ambassadors, and maintainers. To make onboarding experience more efficient and reduce the number of onboarding calls, [Anton Zolotukhin](https://www.linkedin.com/in/mister-gold) and I co-mentored as part of the 2024 Mentorship Program. The hard work of [Ezinne Anne Emilia](https://github.com/ezinneanne) and [Prince Onyeanuna](https://github.com/Aahil13), is now part of the [community content bucket, live on the AsyncAPI website](https://www.asyncapi.com/docs/community/000-onboarding). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thulieblack The last correction here for the misplaced bracket in the "community content bucket" wasn't fixed yet
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks I missed it. Fixed
There was a problem hiding this 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
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
markdown/blog/2025-august-summary.md (1)
112-114: Fix typo and tighten phrasing.“AsyncPI” → “AsyncAPI”.
-- **AsyncAPI Conference London Edition** - Get your **Free Tickets** to the London Conference, and we can't wait to see you there. Be sure to also catch us at the `API Standards Booth`, where you'll find some of our AsyncPI experts and maintainers. +- **AsyncAPI Conference London Edition** — Get your **Free Tickets** to the London Conference; we can't wait to see you there. Be sure to also catch us at the `API Standards Booth`, where you'll find some of our AsyncAPI experts and maintainers.
♻️ Duplicate comments (3)
markdown/blog/2025-august-summary.md (3)
22-24: Harden external link and stabilize image layout; switch to WebP if available.Add
rel="noopener noreferrer", lazy-load, async-decode, and explicit dimensions. Prefer a.webpasset to cut bytes.-<a href='https://www.aklivity.io' target='_blank'> -<img src='/img/sponsors/aklivity_logo.png' alt='Aklivity' width='500px' /> +<a href='https://www.aklivity.io' target='_blank' rel='noopener noreferrer'> +<img src='/img/sponsors/aklivity_logo.webp' alt='Aklivity' width='500' height='160' loading='lazy' decoding='async' /> </a>
101-109: JSX component in a .md file will render as text—rename to .mdx or replace.Either:
- Rename file to
2025-august-summary.mdx, or- Replace the component with static Markdown:
-<Profiles profiles={[ - { - name: 'Adi Boghawala', - avatar: 'https://avatars.githubusercontent.com/u/114283933?v=4', - link: 'https://www.github.com/Adi-204' - } -]} /> +**New TSC Member** + +<a href="https://www.github.com/Adi-204" target="_blank" rel="noopener noreferrer"> + <img src="https://avatars.githubusercontent.com/u/114283933?v=4" alt="Adi Boghawala" width="96" height="96" loading="lazy" decoding="async" /> + <br/>@Adi-204 +</a>
67-67: Grammar, punctuation, and link spacing fixes.
- Add period to “etc.” and break the run-on sentence.
- Add missing space before the link.
-2. **Expand Community Documentation**: We lacked enough onboarding materials for diverse roles we have in the community, such as documentation contributors, code contributors, ambassadors, maintainers, etc, it made the onboarding experience not efficient, and to reduce the number of onboarding calls, [Anton Zolotukhin](https://www.linkedin.com/in/mister-gold) and I co-mentored as part of the 2024 Mentorship Program. The hard work of [Ezinne Anne Emilia](https://github.com/ezinneanne) and [Prince Onyeanuna](https://github.com/Aahil13), is now part of the[ community content bucket, live on the AsyncAPI website](https://www.asyncapi.com/docs/community/000-onboarding). +2. **Expand Community Documentation**: We lacked sufficient onboarding materials for diverse roles in the community—documentation contributors, code contributors, ambassadors, maintainers, etc. This made the onboarding experience inefficient. To reduce the number of onboarding calls, [Anton Zolotukhin](https://www.linkedin.com/in/mister-gold) and I co-mentored as part of the 2024 Mentorship Program. The hard work of [Ezinne Anne Emilia](https://github.com/ezinneanne) and [Prince Onyeanuna](https://github.com/Aahil13) is now part of the [community content bucket, live on the AsyncAPI website](https://www.asyncapi.com/docs/community/000-onboarding).
🧹 Nitpick comments (3)
markdown/blog/2025-august-summary.md (3)
37-39: Replace relative time with an absolute date.“Less than three weeks” will stale quickly. Specify the exact event date (e.g., “on September NN, 2025”).
43-46: Ticket redemption steps—minor formatting for clarity.Render the code as code and tighten wording.
-2. Select one ticket from the **Apidays London Regular Tickets**. -3. Use the code "**AsyncAPIVIP**" to redeem your free ticket. +2. Select one ticket from **Apidays London Regular Tickets**. +3. Use the code `AsyncAPIVIP` to redeem your free ticket.
72-85: Number formatting consistency.Consider using thousands separators for readability across the metrics (e.g., “68,036” vs “68 036”) and apply consistently in the table.
-These efforts demonstrate ... over **68 036 sessions** and **22 456 new users** ... +These efforts demonstrate ... over **68,036 sessions** and **22,456 new users** ...-| `/docs/concepts` | 12 909 | 2 898 | -| `/docs/tutorials`| 18 576 | 7 435 | -| `/docs/tools` | 9 728 | 2 647 | -| `/docs/guides` | 1 881 | 548 | -| `/docs/reference`| 18 331 | 7 034 | -| `/docs/migration`| 891 | 253 | -| `/docs/community`| 329 | 131 | +| `/docs/concepts` | 12,909 | 2,898 | +| `/docs/tutorials`| 18,576 | 7,435 | +| `/docs/tools` | 9,728 | 2,647 | +| `/docs/guides` | 1,881 | 548 | +| `/docs/reference`| 18,331 | 7,034 | +| `/docs/migration`| 891 | 253 | +| `/docs/community`| 329 | 131 |
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
markdown/blog/2025-august-summary.md(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 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.
🪛 LanguageTool
markdown/blog/2025-august-summary.md
[grammar] ~67-~67: There might be a mistake here.
Context: ...: We lacked enough onboarding materials for diverse roles we have in the community,...
(QB_NEW_EN)
[style] ~67-~67: In American English, abbreviations like “etc.” require a period.
Context: ...contributors, ambassadors, maintainers, etc, it made the onboarding experience not ...
(ETC_PERIOD)
[grammar] ~67-~67: There might be a mistake here.
Context: ...capi.com/docs/community/000-onboarding). 3. Complete the AsyncAPI Style Guide: As ...
(QB_NEW_EN)
[grammar] ~76-~76: There might be a mistake here.
Context: ...ontent Bucket | Sessions | New Users | |------------------|----------|---------...
(QB_NEW_EN)
[grammar] ~77-~77: There might be a mistake here.
Context: ...-------------|----------|--------------| | /docs/concepts | 12 909 | 2 898 | ...
(QB_NEW_EN)
[grammar] ~78-~78: There might be a mistake here.
Context: ... | /docs/concepts | 12 909 | 2 898 | | /docs/tutorials| 18 576 | 7 435 | ...
(QB_NEW_EN)
[grammar] ~79-~79: There might be a mistake here.
Context: ... | /docs/tutorials| 18 576 | 7 435 | | /docs/tools | 9 728 | 2 647 | ...
(QB_NEW_EN)
[grammar] ~80-~80: There might be a mistake here.
Context: ... | /docs/tools | 9 728 | 2 647 | | /docs/guides | 1 881 | 548 | ...
(QB_NEW_EN)
[grammar] ~81-~81: There might be a mistake here.
Context: ... | /docs/guides | 1 881 | 548 | | /docs/reference| 18 331 | 7 034 | ...
(QB_NEW_EN)
[grammar] ~82-~82: There might be a mistake here.
Context: ... | /docs/reference| 18 331 | 7 034 | | /docs/migration| 891 | 253 | ...
(QB_NEW_EN)
[grammar] ~83-~83: There might be a mistake here.
Context: ... | /docs/migration| 891 | 253 | | /docs/community| 329 | 131 | ...
(QB_NEW_EN)
[grammar] ~94-~94: There might be a mistake here.
Context: ...1 | 331 | ## Maintainership Program We are officially on the road to Maintai...
(QB_NEW_EN)
[grammar] ~103-~103: There might be a mistake here.
Context: ...cAPI TSC members. <Profiles profiles={[ { name: 'Adi Boghawala', avatar:...
(QB_NEW_EN)
[grammar] ~108-~108: There might be a mistake here.
Context: ...nk: 'https://www.github.com/Adi-204' } ]} /> ## Coming in September - **AsyncA...
(QB_NEW_EN)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2025-august-summary.md
67-67: Spaces inside link text
(MD039, no-space-in-links)
🔇 Additional comments (2)
markdown/blog/2025-august-summary.md (2)
1-15: Front matter date looks correct; keep Sept 4 publish date. Also confirm single featured post.
- Date reflects publication (Sep 4, 2025), which aligns with our prior guidance for monthly summaries.
- Please verify there isn’t another post still marked
featured: trueto avoid multiple featured cards.
31-33: CFP close dates—please re-check before publishing.Double-check the Sept 7 (Online), Oct 5 (Paris), and Nov 7 (DeveloperWeek 2026) deadlines and update if they’ve shifted.
|
@derberg @bandantonio @TRohit20 please give your final reviews and approvals |
There was a problem hiding this 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
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
markdown/blog/2025-august-summary.md (1)
112-114: Typo and clarity.“AsyncPI” → “AsyncAPI”; tighten copy.
-- **AsyncAPI Conference London Edition** - Get your **Free Tickets** to the London Conference, and we can't wait to see you there. Be sure to also catch us at the `API Standards Booth`, where you'll find some of our AsyncPI experts and maintainers. +- **AsyncAPI Conference London Edition** — Get your **free tickets** to the London conference. Be sure to also catch us at the `API Standards Booth`, where you'll find some of our AsyncAPI experts and maintainers.
♻️ Duplicate comments (2)
markdown/blog/2025-august-summary.md (2)
22-24: Harden external link and fix image perf/CLS (noopener, lazy, explicit size, WebP).Repeat of earlier feedback; also fix nonstandard width="500px" (should be numeric).
-<a href='https://www.aklivity.io' target='_blank'> -<img src='/img/sponsors/aklivity_logo.png' alt='Aklivity' width='500px' /> +<a href='https://www.aklivity.io' target='_blank' rel='noopener noreferrer'> +<img src='/img/sponsors/aklivity_logo.webp' + alt='Aklivity sponsor logo' + width='500' height='160' + loading='lazy' decoding='async' /> </a>
103-109: MDX component in .md file won’t render — rename to .mdx or replace.Same as prior comment; either rename file to .mdx or replace with static Markdown.
Option A (rename):
- Rename file to markdown/blog/2025-august-summary.mdx.
Option B (replace component):
-<Profiles profiles={[ - { - name: 'Adi Boghawala', - avatar: 'https://avatars.githubusercontent.com/u/114283933?v=4', - link: 'https://www.github.com/Adi-204' - } -]} /> +{ width=96 height=96 } + +**Adi Boghawala** — [github.com/Adi-204](https://www.github.com/Adi-204)
🧹 Nitpick comments (3)
markdown/blog/2025-august-summary.md (3)
67-69: Grammar/spacing fixes (“etc.” and missing space).-2. **Expand Community Documentation**: We lacked enough onboarding materials for diverse roles we have in the community, such as documentation contributors, code contributors, ambassadors, maintainers, etc, it made the onboarding experience not efficient, and to reduce the number of onboarding calls, [Anton Zolotukhin](https://www.linkedin.com/in/mister-gold) and I co-mentored as part of the 2024 Mentorship Program. The hard work of [Ezinne Anne Emilia](https://github.com/ezinneanne) and [Prince Onyeanuna](https://github.com/Aahil13), is now part of the[ community content bucket, live on the AsyncAPI website](https://www.asyncapi.com/docs/community/000-onboarding). +2. **Expand Community Documentation**: We lacked enough onboarding materials for diverse roles we have in the community, such as documentation contributors, code contributors, ambassadors, and maintainers, etc., which made the onboarding experience inefficient. To reduce the number of onboarding calls, [Anton Zolotukhin](https://www.linkedin.com/in/mister-gold) and I co-mentored as part of the 2024 Mentorship Program. The hard work of [Ezinne Anne Emilia](https://github.com/ezinneanne) and [Prince Onyeanuna](https://github.com/Aahil13) is now part of the [community content bucket, live on the AsyncAPI website](https://www.asyncapi.com/docs/community/000-onboarding).
72-85: Number formatting for readability.Use thousand separators consistently (e.g., 68,036; 22,456) to match the rest of the site’s style.
-These efforts demonstrate the importance of documentation and its contribution to the overall AsyncAPI ecosystem. This is attested by the fact that we have garnered over **68 036 sessions** and **22 456 new users** from January to August 2025. +These efforts demonstrate the importance of documentation and its contribution to the overall AsyncAPI ecosystem. This is attested by the fact that we have garnered over **68,036 sessions** and **22,456 new users** from January to August 2025.
76-85: Table polish (consistency and spacing).Optional: normalize spacing and thousands separators across the table.
-| `/docs/concepts` | 12 909 | 2 898 | -| `/docs/tutorials`| 18 576 | 7 435 | -| `/docs/tools` | 9 728 | 2 647 | -| `/docs/guides` | 1 881 | 548 | -| `/docs/reference`| 18 331 | 7 034 | -| `/docs/migration`| 891 | 253 | -| `/docs/community`| 329 | 131 | +| `/docs/concepts` | 12,909 | 2,898 | +| `/docs/tutorials`| 18,576 | 7,435 | +| `/docs/tools` | 9,728 | 2,647 | +| `/docs/guides` | 1,881 | 548 | +| `/docs/reference`| 18,331 | 7,034 | +| `/docs/migration`| 891 | 253 | +| `/docs/community`| 329 | 131 |
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
markdown/blog/2025-august-summary.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-august-summary.md
[grammar] ~67-~67: There might be a mistake here.
Context: ...: We lacked enough onboarding materials for diverse roles we have in the community,...
(QB_NEW_EN)
[style] ~67-~67: In American English, abbreviations like “etc.” require a period.
Context: ...contributors, ambassadors, maintainers, etc, it made the onboarding experience not ...
(ETC_PERIOD)
[grammar] ~67-~67: There might be a mistake here.
Context: ...capi.com/docs/community/000-onboarding). 3. Complete the AsyncAPI Style Guide: As ...
(QB_NEW_EN)
[grammar] ~76-~76: There might be a mistake here.
Context: ...ontent Bucket | Sessions | New Users | |------------------|----------|---------...
(QB_NEW_EN)
[grammar] ~77-~77: There might be a mistake here.
Context: ...-------------|----------|--------------| | /docs/concepts | 12 909 | 2 898 | ...
(QB_NEW_EN)
[grammar] ~78-~78: There might be a mistake here.
Context: ... | /docs/concepts | 12 909 | 2 898 | | /docs/tutorials| 18 576 | 7 435 | ...
(QB_NEW_EN)
[grammar] ~79-~79: There might be a mistake here.
Context: ... | /docs/tutorials| 18 576 | 7 435 | | /docs/tools | 9 728 | 2 647 | ...
(QB_NEW_EN)
[grammar] ~80-~80: There might be a mistake here.
Context: ... | /docs/tools | 9 728 | 2 647 | | /docs/guides | 1 881 | 548 | ...
(QB_NEW_EN)
[grammar] ~81-~81: There might be a mistake here.
Context: ... | /docs/guides | 1 881 | 548 | | /docs/reference| 18 331 | 7 034 | ...
(QB_NEW_EN)
[grammar] ~82-~82: There might be a mistake here.
Context: ... | /docs/reference| 18 331 | 7 034 | | /docs/migration| 891 | 253 | ...
(QB_NEW_EN)
[grammar] ~83-~83: There might be a mistake here.
Context: ... | /docs/migration| 891 | 253 | | /docs/community| 329 | 131 | ...
(QB_NEW_EN)
[grammar] ~94-~94: There might be a mistake here.
Context: ...1 | 331 | ## Maintainership Program We are officially on the road to Maintai...
(QB_NEW_EN)
[grammar] ~103-~103: There might be a mistake here.
Context: ...cAPI TSC members. <Profiles profiles={[ { name: 'Adi Boghawala', avatar:...
(QB_NEW_EN)
[grammar] ~108-~108: There might be a mistake here.
Context: ...nk: 'https://www.github.com/Adi-204' } ]} /> ## Coming in September - **AsyncA...
(QB_NEW_EN)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2025-august-summary.md
67-67: Spaces inside link text
(MD039, no-space-in-links)
🔇 Additional comments (3)
markdown/blog/2025-august-summary.md (3)
2-3: Publish date is in the future and “featured” — confirm scheduling behavior and uniqueness.
- The date (2025-09-04) is future relative to now; ensure the site won’t publish prematurely or hide the post until that date.
- Verify only one post is allowed to be featured at a time.
Also applies to: 14-15
31-33: Time-sensitive copy (deadlines, “less than three weeks,” and promo code) — verify before publish.Confirm CFP closing dates, London event timing, and public-sharing of code “AsyncAPIVIP.” If any are wrong on Sept 4, adjust.
Also applies to: 37-47
7-7: Assets verified — cover banner and sponsor logos are present.
Co-authored-by: Antonio <bandantonio@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
♻️ Duplicate comments (2)
markdown/blog/2025-august-summary.md (2)
22-24: Add rel, lazy-load, and explicit dimensions; prefer WebP.Harden security and reduce CLS by updating the external link and image. Use WebP if available and drop
pxin width.-<a href='https://www.aklivity.io' target='_blank'> -<img src='/img/sponsors/aklivity_logo.png' alt='Aklivity' width='500px' /> +<a href='https://www.aklivity.io' target='_blank' rel='noopener noreferrer'> +<img src='/img/sponsors/aklivity_logo.webp' alt='Aklivity logo' width='500' height='160' loading='lazy' decoding='async' /> </a>Note: Replace
height='160'with the actual intrinsic height of the asset.
101-109: JSX won’t render in .md — rename to .mdx or replace with static markup.
<Profiles ... />requires MDX processing. Either rename the file to.mdxor replace with static HTML/Markdown.Option A — rename:
- markdown/blog/2025-august-summary.md → markdown/blog/2025-august-summary.mdx
Option B — static replacement:
-<Profiles profiles={[ - { - name: 'Adi Boghawala', - avatar: 'https://avatars.githubusercontent.com/u/114283933?v=4', - link: 'https://www.github.com/Adi-204' - } -]} /> +<div class="profile"> + <a href="https://www.github.com/Adi-204" target="_blank" rel="noopener noreferrer"> + <img src="https://avatars.githubusercontent.com/u/114283933?v=4" alt="Adi Boghawala avatar" width="96" height="96" loading="lazy" decoding="async" /> + <div><strong>Adi Boghawala</strong></div> + </a> +</div>I can convert this post to MDX and adjust any required imports if you confirm the site’s blog supports
.mdx.
🧹 Nitpick comments (7)
markdown/blog/2025-august-summary.md (7)
31-34: Make dates absolute and include the year for clarity.Ordinals like “7th September” are locale-sensitive and drift over time. Prefer “September 7, 2025,” etc.
-- [AsyncAPI Online Conference](https://conference.asyncapi.com/venue/Online) submissions are closing on **7th September.** - [AsyncAPI Paris Edition submissions](https://conference.asyncapi.com/venue/Paris) are closing on **5th October** (*make sure to select the "**AsyncAPI**" track when submitting your proposal*). - [AsyncAPI Summit at DeveloperWeek 2026](https://confengine.com/conferences/asyncapi-summit-at-developerweek2026) is closing on **7th November**. +- [AsyncAPI Online Conference](https://conference.asyncapi.com/venue/Online) submissions close on **September 7, 2025**. +- [AsyncAPI Paris Edition](https://conference.asyncapi.com/venue/Paris) submissions close on **October 5, 2025** (*select the "**AsyncAPI**" track when submitting*). +- [AsyncAPI Summit at DeveloperWeek 2026](https://confengine.com/conferences/asyncapi-summit-at-developerweek2026) submissions close on **November 7, 2025**.
37-41: Avoid relative time (“less than three weeks”) and “soon.”These age poorly post-publication. Replace with the exact event dates and remove “soon/finalising” phrasing.
-We have less than three weeks until the AsyncAPI London Edition, and we are excited to share that we have **FREE Community Tickets** to give to our community members. - -This year's conference features an impressive lineup of speakers; be sure to [check the agenda on the conference website](https://conference.asyncapi.com/venue/London) soon (*we are still finalising the scheduling*). +The AsyncAPI London Edition is coming up, and we have **FREE Community Tickets** for community members. + +This year's conference features an impressive lineup of speakers; [check the agenda](https://conference.asyncapi.com/venue/London) for updates as they are published.If you provide the exact London dates, I can supply a precise wording.
43-46: Ticket flow: add availability window/limits to reduce support churn.Consider noting a redemption deadline, limited quantity, and that codes are first-come-first-served.
66-68: Fix punctuation and streamline the long sentence.“etc,” → “etc., ” and split the run-on for readability.
-2. **Expand Community Documentation**: We lacked enough onboarding materials for diverse roles we have in the community, such as documentation contributors, code contributors, ambassadors, maintainers, etc, it made the onboarding experience not efficient, and to reduce the number of onboarding calls, [Anton Zolotukhin](https://www.linkedin.com/in/mister-gold) and I co-mentored as part of the 2024 Mentorship Program. The hard work of [Ezinne Anne Emilia](https://github.com/ezinneanne) and [Prince Onyeanuna](https://github.com/Aahil13), is now part of the [community content bucket, live on the AsyncAPI website](https://www.asyncapi.com/docs/community/000-onboarding). +2. **Expand Community Documentation**: We lacked enough onboarding materials for diverse community roles—documentation contributors, code contributors, ambassadors, maintainers, etc.,—which made onboarding inefficient. To reduce the number of onboarding calls, [Anton Zolotukhin](https://www.linkedin.com/in/mister-gold) and I co‑mentored as part of the 2024 Mentorship Program. The hard work of [Ezinne Anne Emilia](https://github.com/ezinneanne) and [Prince Onyeanuna](https://github.com/Aahil13) is now part of the [community content bucket on the AsyncAPI website](https://www.asyncapi.com/docs/community/000-onboarding).
72-75: Normalize number formatting for consistency.Use commas for thousands (site-wide default) or stick to a single locale across the post.
-These efforts demonstrate the importance of documentation and its contribution to the overall AsyncAPI ecosystem. This is attested by the fact that we have garnered over **68 036 sessions** and **22 456 new users** from January to August 2025. +These efforts demonstrate the importance of documentation and its contribution to the overall AsyncAPI ecosystem. This is attested by the fact that we have garnered over **68,036 sessions** and **22,456 new users** from January to August 2025.
86-92: Table spacing: remove stray spaces for cleaner rendering.Minor polish; ensures consistent table alignment in most Markdown renderers.
-| Community Bucket | Page Views | Users| +| Community Bucket | Page Views | Users |
7-7: Verify cover asset path and size.Ensure
/img/posts/2025-blog-banner/banner-aug.webpexists, has explicit dimensions in its metadata, and is pre-compressed (quality ~70–80, no oversized resolution) to avoid poor Lighthouse Performance on the preview.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
markdown/blog/2025-august-summary.md(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 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.
🪛 LanguageTool
markdown/blog/2025-august-summary.md
[style] ~67-~67: In American English, abbreviations like “etc.” require a period.
Context: ...contributors, ambassadors, maintainers, etc, it made the onboarding experience not ...
(ETC_PERIOD)
[grammar] ~67-~67: There might be a mistake here.
Context: ...capi.com/docs/community/000-onboarding). 3. Complete the AsyncAPI Style Guide: As ...
(QB_NEW_EN)
[grammar] ~76-~76: There might be a mistake here.
Context: ...ontent Bucket | Sessions | New Users | |------------------|----------|---------...
(QB_NEW_EN)
[grammar] ~77-~77: There might be a mistake here.
Context: ...-------------|----------|--------------| | /docs/concepts | 12 909 | 2 898 | ...
(QB_NEW_EN)
[grammar] ~78-~78: There might be a mistake here.
Context: ... | /docs/concepts | 12 909 | 2 898 | | /docs/tutorials| 18 576 | 7 435 | ...
(QB_NEW_EN)
[grammar] ~79-~79: There might be a mistake here.
Context: ... | /docs/tutorials| 18 576 | 7 435 | | /docs/tools | 9 728 | 2 647 | ...
(QB_NEW_EN)
[grammar] ~80-~80: There might be a mistake here.
Context: ... | /docs/tools | 9 728 | 2 647 | | /docs/guides | 1 881 | 548 | ...
(QB_NEW_EN)
[grammar] ~81-~81: There might be a mistake here.
Context: ... | /docs/guides | 1 881 | 548 | | /docs/reference| 18 331 | 7 034 | ...
(QB_NEW_EN)
[grammar] ~82-~82: There might be a mistake here.
Context: ... | /docs/reference| 18 331 | 7 034 | | /docs/migration| 891 | 253 | ...
(QB_NEW_EN)
[grammar] ~83-~83: There might be a mistake here.
Context: ... | /docs/migration| 891 | 253 | | /docs/community| 329 | 131 | ...
(QB_NEW_EN)
[grammar] ~94-~94: There might be a mistake here.
Context: ...1 | 331 | ## Maintainership Program We are officially on the road to Maintai...
(QB_NEW_EN)
[grammar] ~103-~103: There might be a mistake here.
Context: ...cAPI TSC members. <Profiles profiles={[ { name: 'Adi Boghawala', avatar:...
(QB_NEW_EN)
[grammar] ~108-~108: There might be a mistake here.
Context: ...nk: 'https://www.github.com/Adi-204' } ]} /> ## Coming in September - **AsyncA...
(QB_NEW_EN)
⏰ 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). (4)
- GitHub Check: Redirect rules - asyncapi-website
- GitHub Check: Header rules - asyncapi-website
- GitHub Check: Pages changed - asyncapi-website
- GitHub Check: Test NodeJS PR - windows-latest
🔇 Additional comments (2)
markdown/blog/2025-august-summary.md (2)
3-3: Publish date looks fine; confirm intended timezone and schedule.Date is set to 2025-09-04T06:00:00+01:00. If the post is scheduled, verify the build/publish pipeline honors timezone offsets so it doesn’t publish a day early/late for US visitors. Also aligns with our prior learning to use publication date, not the month being highlighted.
14-14: Only one featured post at a time — verify homepage spotlight.You set
featured: true. Ensure July’s post is no longer featured and that the homepage expects a single featured entry.
There was a problem hiding this 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 (2)
markdown/blog/2025-august-summary.md (2)
22-24: Add rel, lazy-loading, and fixed dimensions; switch logo to WebP.Improves security (noopener), CLS, and performance. Also use numeric width/height (not “px”).
-<a href='https://www.aklivity.io' target='_blank'> -<img src='/img/sponsors/aklivity_logo.png' alt='Aklivity' width='500px' /> +<a href='https://www.aklivity.io' target='_blank' rel='noopener noreferrer'> +<img src='/img/sponsors/aklivity_logo.webp' alt='Aklivity' width='500' height='160' loading='lazy' decoding='async' /> </a>
101-109: MDX component in a .md file will render as text.Either rename the file to .mdx or replace the JSX with plain Markdown/HTML.
Option A (rename):
- Rename: markdown/blog/2025-august-summary.md → markdown/blog/2025-august-summary.mdx
Option B (keep .md; replace block):
-<Profiles profiles={[ - { - name: 'Adi Boghawala', - avatar: 'https://avatars.githubusercontent.com/u/114283933?v=4', - link: 'https://www.github.com/Adi-204' - } -]} /> +- New TSC member: [Adi Boghawala](https://www.github.com/Adi-204)
🧹 Nitpick comments (4)
markdown/blog/2025-august-summary.md (4)
67-67: Fix run-on sentence and punctuation around “etc.”; tighten wording.Improves readability and American English punctuation.
-2. **Expand Community Documentation**: We lacked enough onboarding materials for diverse roles we have in the community, such as documentation contributors, code contributors, ambassadors, maintainers, etc, it made the onboarding experience not efficient, and to reduce the number of onboarding calls, [Anton Zolotukhin](https://www.linkedin.com/in/mister-gold) and I co-mentored as part of the 2024 Mentorship Program. The hard work of [Ezinne Anne Emilia](https://github.com/ezinneanne) and [Prince Onyeanuna](https://github.com/Aahil13), is now part of the [community content bucket, live on the AsyncAPI website](https://www.asyncapi.com/docs/community/000-onboarding). +2. **Expand Community Documentation**: We lacked enough onboarding materials for diverse roles in the community, such as documentation and code contributors, ambassadors, and maintainers, etc. This made onboarding inefficient. To reduce the number of onboarding calls, [Anton Zolotukhin](https://www.linkedin.com/in/mister-gold) and I co-mentored as part of the 2024 Mentorship Program. The hard work of [Ezinne Anne Emilia](https://github.com/ezinneanne) and [Prince Onyeanuna](https://github.com/Aahil13) is now part of the [community content bucket, live on the AsyncAPI website](https://www.asyncapi.com/docs/community/000-onboarding).
72-72: Use thousands separators for readability.Small editorial polish.
-These efforts demonstrate the importance of documentation and its contribution to the overall AsyncAPI ecosystem. This is attested by the fact that we have garnered over **68 036 sessions** and **22 456 new users** from January to August 2025. +These efforts demonstrate the importance of documentation and its contribution to the overall AsyncAPI ecosystem. This is attested by the fact that we have garnered over **68,036 sessions** and **22,456 new users** from January to August 2025.
76-85: Consistent numeric formatting in the table.Apply thousands separators across the dataset.
-| `/docs/concepts` | 12 909 | 2 898 | -| `/docs/tutorials`| 18 576 | 7 435 | -| `/docs/tools` | 9 728 | 2 647 | -| `/docs/guides` | 1 881 | 548 | -| `/docs/reference`| 18 331 | 7 034 | -| `/docs/migration`| 891 | 253 | -| `/docs/community`| 329 | 131 | +| `/docs/concepts` | 12,909 | 2,898 | +| `/docs/tutorials`| 18,576 | 7,435 | +| `/docs/tools` | 9,728 | 2,647 | +| `/docs/guides` | 1,881 | 548 | +| `/docs/reference`| 18,331 | 7,034 | +| `/docs/migration`| 891 | 253 | +| `/docs/community`| 329 | 131 |
111-113: Minor style nit: tighten sentence and remove title caps.Optional, reads smoother.
-- **AsyncAPI Community Updates Newsletter** - The September Edition will be making its way to your inbox on the 5th. [Please subscribe to the AsyncAPI Newsletter](https://www.asyncapi.com/newsletter); don't miss the updates. +- **AsyncAPI community updates newsletter** — The September edition lands in inboxes on the 5th. [Subscribe to the AsyncAPI newsletter](https://www.asyncapi.com/newsletter) so you don’t miss it.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
markdown/blog/2025-august-summary.md(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 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.
🪛 LanguageTool
markdown/blog/2025-august-summary.md
[grammar] ~67-~67: There might be a mistake here.
Context: ...: We lacked enough onboarding materials for diverse roles we have in the community,...
(QB_NEW_EN)
[style] ~67-~67: In American English, abbreviations like “etc.” require a period.
Context: ...contributors, ambassadors, maintainers, etc, it made the onboarding experience not ...
(ETC_PERIOD)
[grammar] ~67-~67: There might be a mistake here.
Context: ...capi.com/docs/community/000-onboarding). 3. Complete the AsyncAPI Style Guide: As ...
(QB_NEW_EN)
[grammar] ~76-~76: There might be a mistake here.
Context: ...ontent Bucket | Sessions | New Users | |------------------|----------|---------...
(QB_NEW_EN)
[grammar] ~77-~77: There might be a mistake here.
Context: ...-------------|----------|--------------| | /docs/concepts | 12 909 | 2 898 | ...
(QB_NEW_EN)
[grammar] ~78-~78: There might be a mistake here.
Context: ... | /docs/concepts | 12 909 | 2 898 | | /docs/tutorials| 18 576 | 7 435 | ...
(QB_NEW_EN)
[grammar] ~79-~79: There might be a mistake here.
Context: ... | /docs/tutorials| 18 576 | 7 435 | | /docs/tools | 9 728 | 2 647 | ...
(QB_NEW_EN)
[grammar] ~80-~80: There might be a mistake here.
Context: ... | /docs/tools | 9 728 | 2 647 | | /docs/guides | 1 881 | 548 | ...
(QB_NEW_EN)
[grammar] ~81-~81: There might be a mistake here.
Context: ... | /docs/guides | 1 881 | 548 | | /docs/reference| 18 331 | 7 034 | ...
(QB_NEW_EN)
[grammar] ~82-~82: There might be a mistake here.
Context: ... | /docs/reference| 18 331 | 7 034 | | /docs/migration| 891 | 253 | ...
(QB_NEW_EN)
[grammar] ~83-~83: There might be a mistake here.
Context: ... | /docs/migration| 891 | 253 | | /docs/community| 329 | 131 | ...
(QB_NEW_EN)
[grammar] ~94-~94: There might be a mistake here.
Context: ...1 | 331 | ## Maintainership Program We are officially on the road to Maintai...
(QB_NEW_EN)
[grammar] ~103-~103: There might be a mistake here.
Context: ...cAPI TSC members. <Profiles profiles={[ { name: 'Adi Boghawala', avatar:...
(QB_NEW_EN)
[grammar] ~108-~108: There might be a mistake here.
Context: ...nk: 'https://www.github.com/Adi-204' } ]} /> ## Coming in September - **AsyncA...
(QB_NEW_EN)
⏰ 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 - windows-latest
- GitHub Check: Test NodeJS PR - macos-13
🔇 Additional comments (1)
markdown/blog/2025-august-summary.md (1)
3-3: Frontmatter date aligns with publication policy.Date reflects publication (September 4, 2025), matching the learned guideline for spotlight/summary posts. No change needed.
|
/rtm |
Add the AsyncAPI Community Summary Update for August
Summary by CodeRabbit
New Features
Documentation