chore(blog): add the july community summary #4287
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. |
WalkthroughThe pull request updates the call-for-papers deadline for the AsyncAPI Conference Paris Edition banner, removes the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches
🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
asyncapi-bot
requested review from
CBID2,
bandantonio,
devilkiller-ag and
vishvamsinh28
thulieblack
requested review from
Mayaleeeee,
TRohit20,
akshatnema,
anshgoyalevil,
asyncapi-bot-eve,
derberg and
sambhavgupta0705
as code owners
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-4287--asyncapi-website.netlify.app/ |
|
@bandantonio @CBID2 @TRohit20 please review but do not approve as yet. |
|
@derberg anything else missing |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4287 +/- ##
=========================================
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: 1
🧹 Nitpick comments (1)
markdown/blog/2025-july-summary.md (1)
29-33: Correct sponsor alt-text spelling
Thealtattribute spells “SmartBeat”; the sponsor is “SmartBear”.- <img src='/img/sponsors/smartbear_logo.png' alt='SmartBeat' width='500px' /> + <img src='/img/sponsors/smartbear_logo.png' alt='SmartBear' width='500px' />
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (4)
components/campaigns/banners.ts(1 hunks)markdown/blog/2025-july-summary.md(1 hunks)markdown/blog/2025-may-summary.md(0 hunks)markdown/blog/first-governance-elections.md(0 hunks)
💤 Files with no reviewable changes (2)
- markdown/blog/2025-may-summary.md
- markdown/blog/first-governance-elections.md
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: asyncapi-bot
PR: asyncapi/website#0
File: :0-0
Timestamp: 2025-02-18T12:07:42.211Z
Learning: The following PR commands are supported in the asyncapi/website repository:
- `/please-take-a-look` or `/ptal`: Requests attention from reviewers who haven't reviewed the PR
- `/ready-to-merge` or `/rtm`: Triggers automerge when all conditions are met
- `/do-not-merge` or `/dnm`: Blocks automerge even if all conditions are met
- `/autoupdate` or `/au`: Adds autoupdate label to keep PR in sync with target branch
- `/update` or `/u`: One-time update of PR with latest changes from target branch
Learnt from: 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.
markdown/blog/2025-july-summary.md (1)
Learnt from: iambami
PR: #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-july-summary.md
[style] ~55-~55: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ... track took place on the first day with an amazing lineup of speakers from our community s...
(AWESOME)
[uncategorized] ~73-~73: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...I Without The Technical Jargon, how the Open Source community strives on collaboration, how...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~146-~146: The wording of this phrase can be improved.
Context: ... happening on #wg-community on how to make the experience better and share best practices on how we can ...
(MAKE_STYLE_BETTER)
⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Test NodeJS PR - windows-latest
- GitHub Check: Test NodeJS PR - macos-13
🔇 Additional comments (2)
components/campaigns/banners.ts (1)
25-25: Deadline extension looks good – confirm date-string consistency across banners
cfpDeadlinehas been updated to2025-10-05T06:00:00Z, which parses correctly in all modern browsers/Node runtimes. Just double-check that the same ISO-8601YYYY-MM-DDTHH:mm:ssZformat is used for every banner to avoid inconsistent parsing on older environments.markdown/blog/2025-july-summary.md (1)
14-15: Verify “featured: true” does not collide with existing featured posts
Only one blog post can be highlighted at a time on the homepage carousel. Ensure the two posts that just hadfeatured: trueremoved were the only other featured items; otherwise, update the flag here or in site config to prevent multiple featured entries.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
markdown/blog/2025-july-summary.md (2)
29-33: Fix typo inaltattribute to keep accessibility accurateThe
alttext for the SmartBear logo is miss-spelled as “SmartBeat”. Screen-readers and SEO rely on thealtstring, so it should match the sponsor’s actual name.-<img src='/img/sponsors/smartbear_logo.png' alt='SmartBeat' width='500px' /> +<img src='/img/sponsors/smartbear_logo.png' alt='SmartBear' width='500px' />
18-18: Clarify month reference to avoid reader confusionThe sentence thanks sponsors “in June”, yet the post is the July community update. If the gratitude is meant for July, change the month; otherwise add a brief note (e.g., “support received in June for July activities”) to make the timeline explicit.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-july-summary.md(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: asyncapi-bot
PR: asyncapi/website#0
File: :0-0
Timestamp: 2025-02-18T12:07:42.211Z
Learning: The following PR commands are supported in the asyncapi/website repository:
- `/please-take-a-look` or `/ptal`: Requests attention from reviewers who haven't reviewed the PR
- `/ready-to-merge` or `/rtm`: Triggers automerge when all conditions are met
- `/do-not-merge` or `/dnm`: Blocks automerge even if all conditions are met
- `/autoupdate` or `/au`: Adds autoupdate label to keep PR in sync with target branch
- `/update` or `/u`: One-time update of PR with latest changes from target branch
Learnt from: 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.
markdown/blog/2025-july-summary.md (3)
Learnt from: iambami
PR: #4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
Learnt from: akshatnema
PR: #3101
File: tests/fixtures/rssData.js:1-57
Timestamp: 2024-11-01T13:32:15.472Z
Learning: In the tests/fixtures/rssData.js file of the @asyncapi/website project, tests for edge cases such as empty strings for title or excerpt, very long text content, international characters (UTF-8), or malformed URLs in slug or cover are not necessary because these cases will not occur.
Learnt from: akshatnema
PR: #3439
File: markdown/blog/2024-marketing-report.md:71-71
Timestamp: 2024-12-07T16:54:10.709Z
Learning: When reviewing reports intended for future dates (e.g., 'Marketing Report: December 2024'), references to future dates within the same year (e.g., 'As of June 2024') are accurate and should not be flagged as errors.
🪛 LanguageTool
markdown/blog/2025-july-summary.md
[style] ~55-~55: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ... track took place on the first day with an amazing lineup of speakers from our community s...
(AWESOME)
[uncategorized] ~73-~73: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...I Without The Technical Jargon, how the Open Source community strives on collaboration, how...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~146-~146: The wording of this phrase can be improved.
Context: ... happening on #wg-community on how to make the experience better and share best practices on how we can ...
(MAKE_STYLE_BETTER)
🔇 Additional comments (1)
markdown/blog/2025-july-summary.md (1)
13-13: Excerpt now correctly says “July 2025” – nice catch
The earlier “May 2025” mismatch reported on a previous commit is fixed here.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
markdown/blog/2025-july-summary.md (3)
18-19: Month reference looks off
The sentence thanks sponsors “in June”, yet this is a July summary. If the renewals actually took place in July, switch the month for consistency.-But before we dive in, I want to acknowledge the continuous support we received from our sponsors in June. +Before we dive in, I want to acknowledge the continuous support we received from our sponsors in July.
53-56: Tighten wording for clarity
Minor editorial polish – avoid the dangling “what became our tradition” clause and remove the extra double-space.-The first day, what became our tradition, we started with the booth, where we could provide vendor-neutral consulting for the API community. The booth was there under the name `API Standards` with people not only from AsyncAPI but also JSON Schema, OpenAPI, and Arazzo. In case you want to learn more about the booth, how we organize it, and where, join the [API Standards mailing group](https://groups.io/g/api-standards). +As has become our tradition, we began the first day at the booth, providing vendor-neutral consulting for the API community. The booth operated under the `API Standards` banner alongside colleagues from JSON Schema, OpenAPI, and Arazzo. If you’d like to learn more about the booth or get involved, join the [API Standards mailing group](https://groups.io/g/api-standards).
68-70: Replace subjective “amazing” with a stronger descriptor
Aim for neutral, precise language in blog posts.-For the 2-day event in Lagos, the AsyncAPI track took place on the first day with an amazing lineup of speakers from our community sharing their knowledge and work. +During the two-day Lagos event, the AsyncAPI track opened day one with a diverse lineup of community speakers who shared their knowledge and experience.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-july-summary.md(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: asyncapi-bot
PR: asyncapi/website#0
File: :0-0
Timestamp: 2025-02-18T12:07:42.211Z
Learning: The following PR commands are supported in the asyncapi/website repository:
- `/please-take-a-look` or `/ptal`: Requests attention from reviewers who haven't reviewed the PR
- `/ready-to-merge` or `/rtm`: Triggers automerge when all conditions are met
- `/do-not-merge` or `/dnm`: Blocks automerge even if all conditions are met
- `/autoupdate` or `/au`: Adds autoupdate label to keep PR in sync with target branch
- `/update` or `/u`: One-time update of PR with latest changes from target branch
Learnt from: 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.
markdown/blog/2025-july-summary.md (3)
Learnt from: iambami
PR: #4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
Learnt from: akshatnema
PR: #3101
File: tests/fixtures/rssData.js:1-57
Timestamp: 2024-11-01T13:32:15.472Z
Learning: In the tests/fixtures/rssData.js file of the @asyncapi/website project, tests for edge cases such as empty strings for title or excerpt, very long text content, international characters (UTF-8), or malformed URLs in slug or cover are not necessary because these cases will not occur.
Learnt from: akshatnema
PR: #3439
File: markdown/blog/2024-marketing-report.md:71-71
Timestamp: 2024-12-07T16:54:10.709Z
Learning: When reviewing reports intended for future dates (e.g., 'Marketing Report: December 2024'), references to future dates within the same year (e.g., 'As of June 2024') are accurate and should not be flagged as errors.
🪛 LanguageTool
markdown/blog/2025-july-summary.md
[style] ~55-~55: Consider using an alternative to strengthen your wording.
Context: ...hema, OpenAPI, and Arazzo. In case you want to learn more about the booth, how we o...
(WANT_KEEN)
[style] ~69-~69: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ... track took place on the first day with an amazing lineup of speakers from our community s...
(AWESOME)
[style] ~160-~160: The wording of this phrase can be improved.
Context: ... happening on #wg-community on how to make the experience better and share best practices on how we can ...
(MAKE_STYLE_BETTER)
⏰ 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 - macos-13
- GitHub Check: Test NodeJS PR - windows-latest
🔇 Additional comments (1)
markdown/blog/2025-july-summary.md (1)
14-14: Confirm “featured: true” is intentional
Only one post can be rendered as “featured” on the homepage at a time. Double-check there isn’t already another July/August post carrying the same flag to avoid layout conflicts.
|
@thulieblack, you can disregard my approval too(merge time! 😃) |
TRohit20
left a comment
TRohit20
left a comment
There was a problem hiding this comment.
Except for couple of comments, rest looks good to me. Thank you @thulieblack
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
markdown/blog/2025-july-summary.md (3)
55-61:<Figure>components lack an explicit alt-textWhile the caption is useful, screen-reader users rely on an
altattribute (or anaria-label) on the underlying<img>element. If theFigurecomponent forwards such text automatically, great—otherwise consider adding an explicitaltprop.
69-70: Tone: replace “amazing” with a more descriptive adjective“An amazing lineup of speakers” is enthusiastic but vague. A more specific term (e.g., “diverse”, “insightful”, “expert”) conveys value without hyperbole.
87-88: Sentence structure feels overloadedThe sentence lists multiple ideas joined by commas, making it hard to parse. Consider splitting into two sentences or using bullets to improve readability.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
markdown/blog/2025-july-summary.md(1 hunks)next-env.d.ts(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- next-env.d.ts
🧰 Additional context used
🧠 Learnings (6)
📓 Common learnings
Learnt from: asyncapi-bot
PR: asyncapi/website#0
File: :0-0
Timestamp: 2025-02-18T12:07:42.211Z
Learning: The following PR commands are supported in the asyncapi/website repository:
- `/please-take-a-look` or `/ptal`: Requests attention from reviewers who haven't reviewed the PR
- `/ready-to-merge` or `/rtm`: Triggers automerge when all conditions are met
- `/do-not-merge` or `/dnm`: Blocks automerge even if all conditions are met
- `/autoupdate` or `/au`: Adds autoupdate label to keep PR in sync with target branch
- `/update` or `/u`: One-time update of PR with latest changes from target branch
Learnt from: akshatnema
PR: asyncapi/website#3265
File: tests/fixtures/toolsObjectData.js:51-52
Timestamp: 2024-10-09T17:35:36.557Z
Learning: When reviewing code in the 'asyncapi/website' repository, akshatnema prefers that I do not provide committable code suggestions.
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.
📚 Learning: for asyncapi community spotlight blog posts, the frontmatter date should reflect the actual publicat...
Learnt from: iambami
PR: asyncapi/website#4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
Applied to files:
markdown/blog/2025-july-summary.md
📚 Learning: in the `tests/fixtures/rssdata.js` file of the `@asyncapi/website` project, tests for edge cases suc...
Learnt from: akshatnema
PR: asyncapi/website#3101
File: tests/fixtures/rssData.js:1-57
Timestamp: 2024-11-01T13:32:15.472Z
Learning: In the `tests/fixtures/rssData.js` file of the `@asyncapi/website` project, tests for edge cases such as empty strings for title or excerpt, very long text content, international characters (UTF-8), or malformed URLs in `slug` or `cover` are not necessary because these cases will not occur.
Applied to files:
markdown/blog/2025-july-summary.md
📚 Learning: when reviewing reports intended for future dates (e.g., 'marketing report: december 2024'), referenc...
Learnt from: akshatnema
PR: asyncapi/website#3439
File: markdown/blog/2024-marketing-report.md:71-71
Timestamp: 2024-12-07T16:54:10.709Z
Learning: When reviewing reports intended for future dates (e.g., 'Marketing Report: December 2024'), references to future dates within the same year (e.g., 'As of June 2024') are accurate and should not be flagged as errors.
Applied to files:
markdown/blog/2025-july-summary.md
📚 Learning: for asyncapi blog posts, author photo filenames don't necessarily need to match the author's officia...
Learnt from: Siddhant-Pragyan-Sinha
PR: asyncapi/website#4074
File: markdown/blog/open-nest.md:11-12
Timestamp: 2025-04-28T01:13:59.084Z
Learning: For AsyncAPI blog posts, author photo filenames don't necessarily need to match the author's official name, as some authors may use pen names or nicknames (e.g., Aishat Muibudeen using "maya_picture.webp" for her avatar).
Applied to files:
markdown/blog/2025-july-summary.md
📚 Learning: when reviewing code in the 'asyncapi/website' repository, akshatnema prefers that i do not provide c...
Learnt from: akshatnema
PR: asyncapi/website#3265
File: tests/fixtures/toolsObjectData.js:51-52
Timestamp: 2024-10-09T17:35:36.557Z
Learning: When reviewing code in the 'asyncapi/website' repository, akshatnema prefers that I do not provide committable code suggestions.
Applied to files:
markdown/blog/2025-july-summary.md
🪛 LanguageTool
markdown/blog/2025-july-summary.md
[style] ~55-~55: Consider using an alternative to strengthen your wording.
Context: ...chema, OpenAPI, and Arazzo. In case you want to learn more about the booth, how we o...
(WANT_KEEN)
[style] ~69-~69: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ... track took place on the first day with an amazing lineup of speakers from our community s...
(AWESOME)
[style] ~160-~160: The wording of this phrase can be improved.
Context: ... happening on #wg-community on how to make the experience better and share best practices on how we can ...
(MAKE_STYLE_BETTER)
🔇 Additional comments (1)
markdown/blog/2025-july-summary.md (1)
18-19: Month reference appears off-by-oneThe paragraph thanks sponsors “in June”, yet the whole post covers July activity.
Please double-check whether the reference should be July instead of June to avoid confusing readers.
|
/rtm |
|
/rtm |
|
/rtm |
7 participants
Add the July Community Summary.
Munich Summary
Lagos Summary
Summary by CodeRabbit