chore(blog): add marketing q1 report #3911
Conversation
iambami
requested review from
thulieblack,
quetzalliwrites,
TRohit20,
derberg,
akshatnema,
anshgoyalevil,
Mayaleeeee and
asyncapi-bot-eve
as code owners
WalkthroughA new markdown file has been added to document the AsyncAPI Q1 Marketing Report for 2025. The report details marketing activities including social media performance metrics, community initiatives, and promotional activities surrounding the AsyncAPI Conference 2025. It also outlines future strategies for audience growth, live sessions, and further community engagement. Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
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
|
✅ 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 #3911 +/- ##
=========================================
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:
|
iambami
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (8)
markdown/blog/2025-Q1-marketing-report.md (8)
1-14: Front Matter Verification and Excerpt Quote Check
The front matter is well-structured and includes all essential metadata. One minor note: verify that the single quotes in the excerpt (which contains an apostrophe in "AsyncAPI's") render correctly with your markdown parser.
20-26: Correction of Typographical Error in Key Objectives
On line 24, the word "Confrences" appears. It should be corrected to "Conferences" for accuracy.Diff suggestion:
- - Promote AsyncAPI-led events and initiatives, including Google Summer of Code (GSoC) and the AsyncAPI Confrences and Webinar. + - Promote AsyncAPI-led events and initiatives, including Google Summer of Code (GSoC) and the AsyncAPI Conferences and Webinar.
40-45: Consider Adding a Determiner for Clarity in Key Insights
For improved clarity, consider adding a determiner on line 43. For example, “The engagement rate increased by 13%…” enhances the flow.Diff suggestion:
- Engagement rate increased by 13%, indicating that our content resonates well with our audience. + The engagement rate increased by 13%, indicating that our content resonates well with our audience.🧰 Tools
🪛 LanguageTool
[uncategorized] ~43-~43: A determiner appears to be missing. Consider inserting it.
Context: ...owing interest in AsyncAPI’s content. - Engagement rate increased by 13%, indicating that ...(AI_EN_LECTOR_MISSING_DETERMINER)
47-58: Fix Missing Data in Twitter Metrics Table
The row on line 57 for "New Followers" is missing the "% Change" value. Consider adding a placeholder (e.g., a hyphen) if data is not available to maintain consistent column count.Diff suggestion:
- |New Followers| 2 | + |New Followers| 2 | -🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
57-57: Table column count
Expected: 3; Actual: 2; Too few cells, row will be missing data(MD056, table-column-count)
59-64: Avoid Duplicate Headings for Enhanced Clarity
The heading "### Key Insights" on line 59 duplicates the previous insights section. Consider renaming it to "### Twitter Insights" to clearly differentiate the insights related to Twitter metrics.Diff suggestion:
- ### Key Insights + ### Twitter Insights🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
59-59: Multiple headings with the same content
null(MD024, no-duplicate-heading)
73-78: Improve Clarity in Community Spotlight Initiative Section
The sentence on line 77 can be rephrased for greater clarity. For example:
“The first spotlight features the Ashmit story. We look forward to featuring more such stories in the future.”Diff suggestion:
- The first spotlight is the Ashmit story. We look forward to having more stories in as we go. + The first spotlight features the Ashmit story. We look forward to featuring more such stories in the future.
79-84: Refine Conference Section for Clarity
On line 83, the phrase "Munich Call for Speaker is also out." could be clearer. Consider revising it to:
“The call for speakers for the Munich event is also now open.”Diff suggestion:
- Munich Call for Speaker is also out. + The call for speakers for the Munich event is also now open.
116-124: Typo Correction in Future Marketing Strategy Section
On line 120, "Manstadon" appears to be a typo. It likely should be "Mastodon."Diff suggestion:
- - Expand LinkedIn, Manstadon, and Twitter audience growth with targeted engagement strategies. + - Expand LinkedIn, Mastodon, and Twitter audience growth with targeted engagement strategies.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-Q1-marketing-report.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-Q1-marketing-report.md
[uncategorized] ~43-~43: A determiner appears to be missing. Consider inserting it.
Context: ...owing interest in AsyncAPI’s content. - Engagement rate increased by 13%, indicating that ...
(AI_EN_LECTOR_MISSING_DETERMINER)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2025-Q1-marketing-report.md
57-57: Table column count
Expected: 3; Actual: 2; Too few cells, row will be missing data
(MD056, table-column-count)
59-59: Multiple headings with the same content
null
(MD024, no-duplicate-heading)
🔇 Additional comments (3)
markdown/blog/2025-Q1-marketing-report.md (3)
16-19: Clear Introduction
The introductory paragraph clearly outlines the scope of the report. The content is concise and sets the right context for the reader.
27-39: Social Media Performance Table Review
The LinkedIn metrics table is clear and effectively presents the data. No issues noted.
125-132: Conclusion and Summary Section Looks Good
The final section effectively summarizes the marketing outcomes and outlines forward-looking strategies. It is clear and comprehensive.
Co-authored-by: Lukasz Gornicki <[email protected]>
asyncapi-bot
requested review from
devilkiller-ag,
sambhavgupta0705,
Aahil13 and
VaishnaviNandakumar
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (8)
markdown/blog/2025-Q1-marketing-report.md (8)
20-26: Typo in Key Objectives.In the bullet on line 24, "AsyncAPI Confrences and Webinar" should be corrected to "AsyncAPI Conferences and Webinar" for clarity.
40-45: Enhance Clarity in Key Insights.Consider revising the bullet on line 43 to include a determiner for improved clarity. For example, "The engagement rate increased by 13%, indicating that our content resonates well with our audience."
🧰 Tools
🪛 LanguageTool
[uncategorized] ~43-~43: A determiner appears to be missing. Consider inserting it.
Context: ...owing interest in AsyncAPI’s content. - Engagement rate increased by 13%, indicating that ...(AI_EN_LECTOR_MISSING_DETERMINER)
47-58: Twitter Metrics Table Structure Issues.
- The header on line 47 could be clearer if formatted as "X (Formerly Twitter) Metric" (i.e. inserting a space after "Twitter)").
- The "New Followers" row on line 57 is missing a cell for the "% Change" value. Please add the missing data or a placeholder to maintain consistent column counts.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
57-57: Table column count
Expected: 3; Actual: 2; Too few cells, row will be missing data(MD056, table-column-count)
59-64: Duplicate Heading Detected.There are two "### Key Insights" sections (lines 40–45 and 59–64). To avoid confusion and improve navigability, consider renaming one—for example, "### Key Insights - Twitter" for the second instance.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
59-59: Multiple headings with the same content
null(MD024, no-duplicate-heading)
73-78: Clarify Community Spotlight Initiative Narrative.The sentence on line 77 ("The first spotlight is the Ashmit story. We look forward to having more stories in as we go.") could be rephrased for better clarity. For example: "The first spotlight features the Ashmit story. We look forward to highlighting more stories as the initiative grows."
85-89: Impact & Next Steps Section Review.The section neatly summarizes the outcomes and future plans. Consider adding any additional specifics on upcoming live sessions if available.
90-115: Improve Image and Link Formatting in Best-Performing Posts Section.The posts are currently represented by file paths. For better rendering in Markdown, consider using the image syntax, for example:
This will help ensure the images display correctly across different platforms.
116-124: Typo in Future Marketing Strategy Section.On line 120, "Manstadon" appears to be a typo. It likely should be "Mastodon" when referencing the social platform.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-Q1-marketing-report.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-Q1-marketing-report.md
[uncategorized] ~43-~43: A determiner appears to be missing. Consider inserting it.
Context: ...owing interest in AsyncAPI’s content. - Engagement rate increased by 13%, indicating that ...
(AI_EN_LECTOR_MISSING_DETERMINER)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2025-Q1-marketing-report.md
57-57: Table column count
Expected: 3; Actual: 2; Too few cells, row will be missing data
(MD056, table-column-count)
59-59: Multiple headings with the same content
null
(MD024, no-duplicate-heading)
⏰ Context from checks skipped due to timeout of 180000ms (1)
- GitHub Check: Lighthouse CI
🔇 Additional comments (7)
markdown/blog/2025-Q1-marketing-report.md (7)
1-14: YAML Front Matter is Well-Formatted.The metadata including title, date, type, tags, cover, authors, and excerpt is clearly defined. Ensure consistency with future posts.
16-19: Introduction Section is Clear.The opening paragraphs succinctly introduce the report’s focus and scope.
27-30: Section Heading Review.The "Marketing Performance Overview" and its sub-heading "Social Media Performance" are clear and set the context well.
31-38: Social Media Performance Table Looks Good.The table under this section is well-structured with three columns that clearly present the LinkedIn metrics.
65-73: Event & Community Engagement Section is Informative.The portion detailing the Google Summer of Code Mentorship Program is clear, and the inclusion of the webinar link is beneficial.
79-84: AsyncAPI Conference 2025 Section is Concise.This section clearly outlines the speaker announcements and promotional efforts. The content is succinct and engaging.
125-132: Conclusion Section is Impactful.The final summary effectively recaps key achievements and outlines future strategies. The messaging is clear and well-presented.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (10)
markdown/blog/2025-Q1-marketing-report.md (10)
20-26: Key Objectives List – Spelling & Clarity
The “Key Objectives” section is well outlined. However, note the typo in objective 3 where “AsyncAPI Confrences and Webinar” should likely be “AsyncAPI Conferences and Webinar”.- - Promote AsyncAPI-led events and initiatives, including Google Summer of Code (GSoC) and the AsyncAPI Confrences and Webinar. + - Promote AsyncAPI-led events and initiatives, including Google Summer of Code (GSoC) and the AsyncAPI Conferences and Webinar.
27-44: Social Media Performance Table & Insights – Language Enhancement
The social media performance table is clear and informative. In the Key Insights list, consider modifying the second bullet by adding a definite article for better readability. For example, change- Engagement rate increased by 13%, indicating that our content resonates well with our audience.to
- The engagement rate increased by 13%, indicating that our content resonates well with our audience.This small change addresses the static analysis hint regarding a missing determiner.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~43-~43: A determiner appears to be missing. Consider inserting it.
Context: ...owing interest in AsyncAPI’s content. - Engagement rate increased by 13%, indicating that ...(AI_EN_LECTOR_MISSING_DETERMINER)
58-62: Duplicate Heading for Key Insights
There are two separate “### Key Insights” sections (one for LinkedIn and another for X). To improve clarity, consider renaming the second instance (e.g., “### Twitter Insights”) so that each section clearly distinguishes the platforms.- ### Key Insights + ### Twitter Insights🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
58-58: Multiple headings with the same content
null(MD024, no-duplicate-heading)
76-83: Headings vs. Emphasis in User Engagement Insights
The section titles “User Engagement Insights (Google Analytics)” and “Strong Interest in Version 3.0.0” use bold formatting instead of proper Markdown headings. For improved semantic structure and accessibility, please convert these to heading syntax. For example:- **User Engagement Insights (Google Analytics)** + ## User Engagement Insights (Google Analytics)and
- **Strong Interest in Version 3.0.0** + ## Strong Interest in Version 3.0.0🧰 Tools
🪛 LanguageTool
[style] ~83-~83: Consider an alternative adjective to strengthen your wording.
Context: ... with a solid 41s average time, showing deep interest in the newest spec release. *...(DEEP_PROFOUND)
🪛 markdownlint-cli2 (0.17.2)
81-81: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
85-91: Proper Heading Usage for Section Titles
Similarly, sections like “High Engagement Pages” and “Notable Drops” are currently formatted with bold text. Converting these to proper headings (e.g., using##or###) will improve document structure and accessibility.- **High Engagement Pages** + ## High Engagement Pages- **Notable Drops** + ## Notable Drops🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
85-85: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
91-91: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
93-93: Punctuation in Compound Sentence
Line 93 contains a compound sentence that would benefit from a comma before “but”. For clarity, change:"Generator" and "Tools" saw good traffic but experienced drops in average time spent (-13.4% and +1.9%, respectively).to
"Generator" and "Tools" saw good traffic, but experienced drops in average time spent (-13.4% and +1.9%, respectively).🧰 Tools
🪛 LanguageTool
[uncategorized] ~93-~93: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ..."Generator" and "Tools" saw good traffic but experienced drops in average time spent...(COMMA_COMPOUND_SENTENCE_2)
124-139: Best-Performing Post – First Entry Details
The details for the first best-performing post are well outlined. For clarity and conciseness, consider rephrasing the key takeaway. For example, instead of:- Key Takeaway: Why it performed well is because it's a community-driven and thought leadership post.you might simplify to:
- Key Takeaway: Its community-driven and thought leadership focus drove strong engagement.
147-155: Second Best-Performing Post – Metrics Correction
There is a minor typographical error with the metric “Clicks; 215” on line 152. It should read “Clicks: 215”. Ensuring consistency in punctuation across all metrics will improve readability.- - Clicks; 215 + - Clicks: 215
175-183: Future Marketing Strategy & Key Focus Areas – Typographical Check
The future strategy section is very informative. However, on line 179, the term “Manstadon” appears. This is likely a typo for “Mastodon” (the social platform). Please confirm and correct as needed.- - Expand LinkedIn, Manstadon, and Twitter audience growth with targeted engagement strategies. + - Expand LinkedIn, Mastodon, and Twitter audience growth with targeted engagement strategies.
184-190: Conclusion and Final Remarks
The concluding section effectively summarizes AsyncAPI’s recent achievements and outlines future focus areas. Consider adding a succinct call-to-action or a brief outlook on the next steps to further engage your audience.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-Q1-marketing-report.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-Q1-marketing-report.md
[uncategorized] ~43-~43: A determiner appears to be missing. Consider inserting it.
Context: ...owing interest in AsyncAPI’s content. - Engagement rate increased by 13%, indicating that ...
(AI_EN_LECTOR_MISSING_DETERMINER)
[style] ~83-~83: Consider an alternative adjective to strengthen your wording.
Context: ... with a solid 41s average time, showing deep interest in the newest spec release. *...
(DEEP_PROFOUND)
[uncategorized] ~93-~93: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ..."Generator" and "Tools" saw good traffic but experienced drops in average time spent...
(COMMA_COMPOUND_SENTENCE_2)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2025-Q1-marketing-report.md
58-58: Multiple headings with the same content
null
(MD024, no-duplicate-heading)
81-81: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
85-85: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
91-91: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
⏰ 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 (9)
markdown/blog/2025-Q1-marketing-report.md (9)
1-14: Front Matter & Metadata Overview
The YAML front matter is well structured, and the metadata (title, date, type, tags, cover, authors, and excerpt) appears correctly formatted. The excerpt matches previous suggestions; if it’s identical to earlier commits, please double-check consistency.
16-18: Introduction Clarity
The introductory paragraphs clearly set the context for the report. They succinctly summarize the marketing efforts and outline the report’s purpose.
47-57: X (Formerly Twitter) Performance Table Review
The performance table for X is formatted consistently with its LinkedIn counterpart. Ensure that the column headers and numerical values are accurate and that formatting (such as spacing and alignment) remains consistent when rendered.
66-74: Website Performance Section – Figure Block
The website performance section and its figure block are well implemented. The alt text and caption are descriptive, which is great for accessibility and context.
95-107: Event & Community Engagement Section
The sections detailing the Google Summer of Code Mentorship Program and Community Spotlight Initiative are well-written and engaging. The hyperlink in line 100 is clear and descriptive. Overall, the content here effectively communicates the initiatives undertaken.
109-114: AsyncAPI Conference 2025 Section
This section clearly presents the conference-related promotional details. The bullet points are concise and informative. No changes required here.
115-123: Impact & Next Steps; Top 3 Best-Performing Posts Sections
These sections provide a strong summary of performance metrics and key takeaways. The headings are correctly used in these parts. Great job organizing the critical insights here.
156-173: Third Best-Performing Post – Consistency Check
The details for the third best-performing post are clearly presented. The formatting and narrative are consistent with the other entries. No changes required here.
1-191: Overall Structure and Readability
The new Q1 Marketing Report is comprehensive and well-organized. The detailed metrics, visual elements, and future strategy provide a complete picture of AsyncAPI’s marketing performance. The suggestions above aim to refine markdown formatting, correct minor typographical errors, and enhance clarity.🧰 Tools
🪛 LanguageTool
[uncategorized] ~43-~43: A determiner appears to be missing. Consider inserting it.
Context: ...owing interest in AsyncAPI’s content. - Engagement rate increased by 13%, indicating that ...(AI_EN_LECTOR_MISSING_DETERMINER)
[style] ~83-~83: Consider an alternative adjective to strengthen your wording.
Context: ... with a solid 41s average time, showing deep interest in the newest spec release. *...(DEEP_PROFOUND)
[uncategorized] ~93-~93: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ..."Generator" and "Tools" saw good traffic but experienced drops in average time spent...(COMMA_COMPOUND_SENTENCE_2)
🪛 markdownlint-cli2 (0.17.2)
58-58: Multiple headings with the same content
null(MD024, no-duplicate-heading)
81-81: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
85-85: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
91-91: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
|
The doc has been updated. @thulieblack @derberg @AceTheCreator @TRohit20 In the meantime, I will be implementing suggestions from coderabbit. |
| 1. [We’re welcoming three new members to the AsyncAPI Technical Steering Committee (TSC)](https://www.linkedin.com/feed/update/urn:li:ugcPost:7287771093354893312/) | ||
|
|
||
| - Impressions: 2,470 Impressions | ||
| - Likes: 67 | ||
| - Comments: 12 | ||
| - Clicks: 361 | ||
| - Engagement Rate: 18.18% | ||
| - Key Takeaway: Why it performed well is because it's a community-driven and thought leadership post. | ||
|
|
||
| <Figure | ||
| src="/img/posts/marketing-images/second-best-performance-post.webp" | ||
| alt="Ankit Kumar, Head of Developer & Customer Success at @Aklivity, as a speaker at AsyncAPI Conference Singapore 2025" | ||
| caption="A LinkedIn announcement showing the performance details of Ankit Kumar speaker post" | ||
| className="text-center" | ||
| /> | ||
|
|
||
| 2. [Join us in welcoming Ankit Kumar, Head of Developer & Customer Success at @Aklivity, as a speaker at AsyncAPI Conference Singapore 2025! 🚀](https://www.linkedin.com/feed/update/urn:li:share:7308442490213126145/) | ||
|
|
||
| - Impressions: 1,332 | ||
| - Likes: 54 | ||
| - Comments: 1 | ||
| - Clicks; 215 | ||
| - Engagement Rate: 20.42% | ||
| - Key Takeaway: What worked well, thought leadership, community-driven | ||
|
|
||
|
|
||
| <Figure | ||
| src="/img/posts/marketing-images/third-best-performance-post.webp" | ||
| alt="Announcement that Laurent Broudoux is stepping into a new role as an AsyncAPI Ambassador!" | ||
| caption="A LinkedIn announcement showing the performance details of Laurent Broudoux post" | ||
| className="text-center" | ||
| /> | ||
|
|
||
| 3. [We’re thrilled to announce that Laurent Broudoux is stepping into a new role as an AsyncAPI Ambassador! 🚀](https://www.linkedin.com/feed/update/urn:li:share:7310201401454829568/) | ||
|
|
||
|
|
||
| - Impressions: 998 | ||
| - Likes: 70 | ||
| - Comments: 5 | ||
| - Clicks: 49 | ||
| - Engagement Rate: 12.73% | ||
| - Key Takeaway: It's community-driven, high-value content, visual appeal | ||
|
|
There was a problem hiding this comment.
| 1. [We’re welcoming three new members to the AsyncAPI Technical Steering Committee (TSC)](https://www.linkedin.com/feed/update/urn:li:ugcPost:7287771093354893312/) | |
| - Impressions: 2,470 Impressions | |
| - Likes: 67 | |
| - Comments: 12 | |
| - Clicks: 361 | |
| - Engagement Rate: 18.18% | |
| - Key Takeaway: Why it performed well is because it's a community-driven and thought leadership post. | |
| <Figure | |
| src="/img/posts/marketing-images/second-best-performance-post.webp" | |
| alt="Ankit Kumar, Head of Developer & Customer Success at @Aklivity, as a speaker at AsyncAPI Conference Singapore 2025" | |
| caption="A LinkedIn announcement showing the performance details of Ankit Kumar speaker post" | |
| className="text-center" | |
| /> | |
| 2. [Join us in welcoming Ankit Kumar, Head of Developer & Customer Success at @Aklivity, as a speaker at AsyncAPI Conference Singapore 2025! 🚀](https://www.linkedin.com/feed/update/urn:li:share:7308442490213126145/) | |
| - Impressions: 1,332 | |
| - Likes: 54 | |
| - Comments: 1 | |
| - Clicks; 215 | |
| - Engagement Rate: 20.42% | |
| - Key Takeaway: What worked well, thought leadership, community-driven | |
| <Figure | |
| src="/img/posts/marketing-images/third-best-performance-post.webp" | |
| alt="Announcement that Laurent Broudoux is stepping into a new role as an AsyncAPI Ambassador!" | |
| caption="A LinkedIn announcement showing the performance details of Laurent Broudoux post" | |
| className="text-center" | |
| /> | |
| 3. [We’re thrilled to announce that Laurent Broudoux is stepping into a new role as an AsyncAPI Ambassador! 🚀](https://www.linkedin.com/feed/update/urn:li:share:7310201401454829568/) | |
| - Impressions: 998 | |
| - Likes: 70 | |
| - Comments: 5 | |
| - Clicks: 49 | |
| - Engagement Rate: 12.73% | |
| - Key Takeaway: It's community-driven, high-value content, visual appeal | |
| 1. [We’re welcoming three new members to the AsyncAPI Technical Steering Committee (TSC)](https://www.linkedin.com/feed/update/urn:li:ugcPost:7287771093354893312/) | |
| - Impressions: 2,470 Impressions | |
| - Likes: 67 | |
| - Comments: 12 | |
| - Clicks: 361 | |
| - Engagement Rate: 18.18% | |
| - Key Takeaway: Why it performed well is because it's a community-driven and thought leadership post. | |
| <Figure | |
| src="/img/posts/marketing-images/second-best-performance-post.webp" | |
| alt="Ankit Kumar, Head of Developer & Customer Success at @Aklivity, as a speaker at AsyncAPI Conference Singapore 2025" | |
| caption="A LinkedIn announcement showing the performance details of Ankit Kumar speaker post" | |
| className="text-center" | |
| /> | |
| 2. [Join us in welcoming Ankit Kumar, Head of Developer & Customer Success at @Aklivity, as a speaker at AsyncAPI Conference Singapore 2025! 🚀](https://www.linkedin.com/feed/update/urn:li:share:7308442490213126145/) | |
| - Impressions: 1,332 | |
| - Likes: 54 | |
| - Comments: 1 | |
| - Clicks; 215 | |
| - Engagement Rate: 20.42% | |
| - Key Takeaway: What worked well, thought leadership, community-driven | |
| <Figure | |
| src="/img/posts/marketing-images/third-best-performance-post.webp" | |
| alt="Announcement that Laurent Broudoux is stepping into a new role as an AsyncAPI Ambassador!" | |
| caption="A LinkedIn announcement showing the performance details of Laurent Broudoux post" | |
| className="text-center" | |
| /> | |
| 3. [We’re thrilled to announce that Laurent Broudoux is stepping into a new role as an AsyncAPI Ambassador! 🚀](https://www.linkedin.com/feed/update/urn:li:share:7310201401454829568/) | |
| - Impressions: 998 | |
| - Likes: 70 | |
| - Comments: 5 | |
| - Clicks: 49 | |
| - Engagement Rate: 12.73% | |
| - Key Takeaway: It's community-driven, high-value content, visual appeal |
|
Hey folks, the changes have been implemented. Kindly review. |
There was a problem hiding this comment.
Actionable comments posted: 6
🧹 Nitpick comments (3)
markdown/blog/2025-Q1-marketing-report.md (3)
16-19: Consider strengthening descriptive language
You might replace “solidify our position” or “stronger community presence” with more specific or impactful adjectives to make the intro more engaging.
92-92: Insert missing comma before “but”
For grammatical correctness, add a comma before “but”:“Generator and Tools saw good traffic**,** but experienced drops in average time spent.”
🧰 Tools
🪛 LanguageTool
[uncategorized] ~92-~92: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ..."Generator" and "Tools" saw good traffic but experienced drops in average time spent...(COMMA_COMPOUND_SENTENCE_2)
120-120: Correct event name grammar
Consider updating “Munich Call for Speaker is also out” to “Munich Call for Speakers is now open” for clarity and consistency.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-Q1-marketing-report.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-Q1-marketing-report.md
[style] ~82-~82: Consider an alternative adjective to strengthen your wording.
Context: ... with a solid 41s average time, showing deep interest in the newest spec release. *...
(DEEP_PROFOUND)
[uncategorized] ~92-~92: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ..."Generator" and "Tools" saw good traffic but experienced drops in average time spent...
(COMMA_COMPOUND_SENTENCE_2)
[style] ~127-~127: Consider an alternative adjective to strengthen your wording.
Context: ...real-world applications. Eduardo shared deep insights into event-driven architecture...
(DEEP_PROFOUND)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2025-Q1-marketing-report.md
58-58: Multiple headings with the same content
null
(MD024, no-duplicate-heading)
80-80: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
84-84: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
90-90: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
⏰ 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 (3)
markdown/blog/2025-Q1-marketing-report.md (3)
1-14: Frontmatter metadata is well-structured
The frontmatter contains all required fields (title, date, type, tags, cover, authors, excerpt) and follows the site’s conventions.
4-4: Verifytypefrontmatter field aligns with blog taxonomy
Ensure thattype: Communicationmatches the content model for blog posts; many posts usetype: blog. Please confirm this field is correct.
100-101: Double-check link to strategy document
The link points to the GitHub repository. If the intention is to link to the website’s published page, please verify or update the URL accordingly.
| **User Engagement Insights (Google Analytics)** | ||
| **Homepage Performance** |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Replace emphasis with semantic subheadings
Sections such as User Engagement Insights (Google Analytics), Homepage Performance, High Engagement Pages, and Notable Drops should use markdown headings (e.g., ###/####) instead of bold/emphasis to correctly convey document structure and improve accessibility.
Also applies to: 84-84, 90-90
| - To sustain and scale this initiative, we plan to: | ||
|
|
||
| - Host monthly live sessions and developer Q&As featuring maintainers, contributors, and experts in the ecosystem. | ||
|
|
||
| - Introduce community-driven topic nominations to ensure the sessions address current challenges and interests. | ||
|
|
||
| - Repurpose session content into bite-sized clips, blog posts, and social media highlights for ongoing engagement. | ||
|
|
||
| - Build a resource hub where past sessions and learning materials can be accessed anytime. | ||
|
|
||
| - Collaborate with community ambassadors and contributors to co-host sessions, fostering ownership and inclusiveness. | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Standardize nested list indentation
The nested bullets under “To sustain and scale this initiative” use two-space indentation, whereas other nested lists use four spaces. For consistency, choose one style (e.g., two spaces) throughout.
|
@iambami looking great now! just please update date, set it for tomorrow, and also there are some good minor suggestions from rabbit, please apply them, especially that it offers a commitable suggestions, so you do not have to do anything locally on your computer |
|
Done, @derberg. |
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (3)
markdown/blog/2025-Q1-marketing-report.md (3)
3-3: Duplicate date update suggestion
Derberg previously requested updating the report’s date to the following day. Please confirm and adjust thedate:in the frontmatter to the correct publication date.
40-45: Avoid duplicate “Key Insights” headings
Having two identical### Key Insightssections will create conflicting anchors. Rename them to reflect their context, for example:-### Key Insights +### LinkedIn Key Insights ... -### Key Insights +### X Key InsightsAlso applies to: 58-63
75-77: Use semantic headings instead of bold emphasis
Emphasized lines should be true markdown headings to improve structure and accessibility. For example:- **User Engagement Insights (Google Analytics)** + ### User Engagement Insights (Google Analytics) - **Homepage Performance** + #### Homepage Performance - **Strong Interest in Version 3.0.0** + #### Strong Interest in Version 3.0.0 - **High Engagement Pages** + #### High Engagement Pages - **Notable Drops** + #### Notable DropsAlso applies to: 80-80, 84-84, 90-90
🧹 Nitpick comments (3)
markdown/blog/2025-Q1-marketing-report.md (3)
31-31: Capitalize table header for consistency
The third header cell reads**last Quarter Value**; consider capitalizing “Last” for consistency with other headers:-| **LinkedIn Metric** | **Value** | **last Quarter Value** | **% Change** | +| **LinkedIn Metric** | **Value** | **Last Quarter Value** | **% Change** |
92-92: Add comma before “but” for clarity
In the Notable Drops sentence, insert a comma before “but” to properly join the clauses:- "Generator" and "Tools" saw good traffic but experienced drops in average time spent (-13.4% and +1.9%, respectively). + "Generator" and "Tools" saw good traffic, but experienced drops in average time spent (-13.4% and +1.9%, respectively).🧰 Tools
🪛 LanguageTool
[uncategorized] ~92-~92: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ..."Generator" and "Tools" saw good traffic but experienced drops in average time spent...(COMMA_COMPOUND_SENTENCE_2)
127-127: Consider a stronger adjective
You describe Eduardo’s session as sharing “deep insights.” To make this more vivid, you could use a term like “comprehensive insights” or “actionable insights.”🧰 Tools
🪛 LanguageTool
[style] ~127-~127: Consider a different adjective to strengthen your wording.
Context: ...real-world applications. Eduardo shared deep insights into event-driven architecture...(DEEP_PROFOUND)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-Q1-marketing-report.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-Q1-marketing-report.md
[style] ~82-~82: Consider a different adjective to strengthen your wording.
Context: ... with a solid 41s average time, showing deep interest in the newest spec release. *...
(DEEP_PROFOUND)
[uncategorized] ~92-~92: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ..."Generator" and "Tools" saw good traffic but experienced drops in average time spent...
(COMMA_COMPOUND_SENTENCE_2)
[style] ~127-~127: Consider a different adjective to strengthen your wording.
Context: ...real-world applications. Eduardo shared deep insights into event-driven architecture...
(DEEP_PROFOUND)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2025-Q1-marketing-report.md
58-58: Multiple headings with the same content
null
(MD024, no-duplicate-heading)
80-80: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
84-84: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
90-90: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
⏰ Context from checks skipped due to timeout of 180000ms (2)
- GitHub Check: Test NodeJS PR - windows-latest
- GitHub Check: Lighthouse CI
🔇 Additional comments (1)
markdown/blog/2025-Q1-marketing-report.md (1)
13-13: Excerpt matches approved suggestion
Theexcerpthas been updated to the phrasing suggested by Derberg, capturing the quarter’s highlights succinctly.
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (1)
markdown/blog/2025-Q1-marketing-report.md (1)
75-77: 🛠️ Refactor suggestionUse Markdown headings instead of bold text.
Convert the emphasized lines into proper headings for better structure and accessibility:
- **User Engagement Insights (Google Analytics)** - **Homepage Performance** +### User Engagement Insights (Google Analytics) +#### Homepage Performance
🧹 Nitpick comments (7)
markdown/blog/2025-Q1-marketing-report.md (7)
36-36: Add a leading space for consistency in the table row.In the LinkedIn metrics table, the “Impressions” row is missing a space after the leading
|.-|Impressions | 23,715 | 29,366 | -18% | +| Impressions | 23,715 | 29,366 | -18% |
47-47: Correct the X metrics table header label.The third column is currently labeled
% last Quarterbut it shows raw values, not percentages. Rename it to “Last Quarter Value” for clarity:-| **X (Formerly Twitter) Metric** | **Value** | **% last Quarter** | **% Change** | +| **X (Formerly Twitter) Metric** | **Value** | **Last Quarter Value** | **% Change** |
82-83: Consider a stronger adjective.“showing deep interest” is serviceable, but you might use a more impactful adjective (e.g., “profound interest”) to strengthen your wording.
🧰 Tools
🪛 LanguageTool
[style] ~82-~82: Consider a different adjective to strengthen your wording.
Context: ... with a solid 41s average time, showing deep interest in the newest spec release. *...(DEEP_PROFOUND)
90-93: Add a comma before “but”.This is a compound sentence; insert a comma for correct punctuation:
- "Generator" and "Tools" saw good traffic but experienced drops... + "Generator" and "Tools" saw good traffic, but experienced drops...🧰 Tools
🪛 LanguageTool
[uncategorized] ~92-~92: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ..."Generator" and "Tools" saw good traffic but experienced drops in average time spent...(COMMA_COMPOUND_SENTENCE_2)
126-128: Refine “deep insights” phrasing.Instead of “Eduardo shared deep insights,” consider a more descriptive adjective (e.g., “profound insights”) to enhance readability.
🧰 Tools
🪛 LanguageTool
[style] ~127-~127: Consider a different adjective to strengthen your wording.
Context: ...real-world applications. Eduardo shared deep insights into event-driven architecture...(DEEP_PROFOUND)
120-120: Link the Munich Call for Speakers.Provide a URL for the “Munich Call for Speaker” item so readers can directly access the CFP:
- - Munich Call for Speaker is also out. + - [Munich Call for Speakers is also out](<insert-link-here>).
131-142: Standardize nested list indentation.The sub-bullets under “To sustain and scale this initiative” use two spaces, while other sections use four. For consistency, choose one style (e.g., four spaces) across the document.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-Q1-marketing-report.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-Q1-marketing-report.md
[style] ~82-~82: Consider a different adjective to strengthen your wording.
Context: ... with a solid 41s average time, showing deep interest in the newest spec release. *...
(DEEP_PROFOUND)
[uncategorized] ~92-~92: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ..."Generator" and "Tools" saw good traffic but experienced drops in average time spent...
(COMMA_COMPOUND_SENTENCE_2)
[style] ~127-~127: Consider a different adjective to strengthen your wording.
Context: ...real-world applications. Eduardo shared deep insights into event-driven architecture...
(DEEP_PROFOUND)
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (2)
markdown/blog/2025-Q1-marketing-report.md (2)
134-142: 🛠️ Refactor suggestionStandardize nested list indentation.
Use four spaces for nested items to match the rest of the document.
- - Host monthly live sessions and developer Q&As featuring maintainers, contributors, and experts in the ecosystem. - - Introduce community-driven topic nominations to ensure the sessions address current challenges and interests. - - Repurpose session content into bite-sized clips, blog posts, and social media highlights for ongoing engagement. - - Build a resource hub where past sessions and learning materials can be accessed anytime. - - Collaborate with community ambassadors and contributors to co-host sessions, fostering ownership and inclusiveness. + - Host monthly live sessions and developer Q&As featuring maintainers, contributors, and experts in the ecosystem. + - Introduce community-driven topic nominations to ensure the sessions address current challenges and interests. + - Repurpose session content into bite-sized clips, blog posts, and social media highlights for ongoing engagement. + - Build a resource hub where past sessions and learning materials can be accessed anytime. + - Collaborate with community ambassadors and contributors to co-host sessions, fostering ownership and inclusiveness.
76-93: 🛠️ Refactor suggestionConvert emphasized subheadings to proper Markdown headings.
Using bold text for subheadings reduces accessibility and breaks document structure. Please use
###/####for the following sections:- **User Engagement Insights (Google Analytics)** + ### User Engagement Insights (Google Analytics) - **Homepage Performance** + #### Homepage Performance - **Strong Interest in Version 3.0.0** + #### Strong Interest in Version 3.0.0 - **High Engagement Pages** + #### High Engagement Pages - **Notable Drops** + #### Notable Drops🧰 Tools
🪛 LanguageTool
[style] ~83-~83: Consider a different adjective to strengthen your wording.
Context: ... with a solid 41s average time, showing deep interest in the newest spec release. *...(DEEP_PROFOUND)
[uncategorized] ~93-~93: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ..."Generator" and "Tools" saw good traffic but experienced drops in average time spent...(COMMA_COMPOUND_SENTENCE_2)
🪛 markdownlint-cli2 (0.17.2)
81-81: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
85-85: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
91-91: Emphasis used instead of a heading
null(MD036, no-emphasis-as-heading)
🧹 Nitpick comments (4)
markdown/blog/2025-Q1-marketing-report.md (4)
3-3: Update the publication date to the live date.Derberg requested bumping the report date to the day it goes live.
- date: 2025-05-21T06:00:00+01:00 + date: 2025-05-22T06:00:00+01:00
69-74: Remove extra spacing in the image alt text.There are two spaces between “AsyncAPI” and “Google Analytics.”
<Figure src="/img/posts/marketing-images/google-analysis-page-view.webp" - alt="A table showing AsyncAPI Google Analytics Homepage performance from January to March" + alt="A table showing AsyncAPI Google Analytics Homepage performance from January to March" caption="AsyncAPI Google Analytics Homepage performance from January to March" className="text-center" />
97-97: Remove leading space before paragraph.Extra indentation can render unpredictably in MDX.
- As highlighted in the [2024 Marketing Report]... + As highlighted in the [2024 Marketing Report]...
121-121: Fix grammar in the Munich call bullet.“Call for Speaker” should be plural or phrased consistently.
- - Munich Call for Speaker is also out. + - Munich Call for Speakers is now live.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting
📒 Files selected for processing (1)
markdown/blog/2025-Q1-marketing-report.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-Q1-marketing-report.md
[uncategorized] ~44-~44: A determiner appears to be missing. Consider inserting it.
Context: ...owing interest in AsyncAPI’s content. - Engagement rate increased by 13%, indicating that ...
(AI_EN_LECTOR_MISSING_DETERMINER)
[style] ~83-~83: Consider a different adjective to strengthen your wording.
Context: ... with a solid 41s average time, showing deep interest in the newest spec release. *...
(DEEP_PROFOUND)
[uncategorized] ~93-~93: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ..."Generator" and "Tools" saw good traffic but experienced drops in average time spent...
(COMMA_COMPOUND_SENTENCE_2)
[style] ~128-~128: Consider a different adjective to strengthen your wording.
Context: ...real-world applications. Eduardo shared deep insights into event-driven architecture...
(DEEP_PROFOUND)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2025-Q1-marketing-report.md
81-81: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
85-85: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
91-91: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
🔇 Additional comments (1)
markdown/blog/2025-Q1-marketing-report.md (1)
57-57: Verify the “New Followers” last quarter value.A negative follower count of
-27seems unlikely—please confirm this data point or correct it if it’s a typo.
| - Click-through rates need improvement, signaling stronger CTAs and content hooks. | ||
|
|
||
|
|
||
| | **X (Formerly Twitter) Metric** | **Value** |**% last Quarter** |**% Change** | |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Unify the X table header for consistency.
The third column header for the X metrics table should match the LinkedIn table’s “Last Quarter Value” label.
- | **X (Formerly Twitter) Metric** | **Value** |**% last Quarter** |**% Change** |
+ | **X (Formerly Twitter) Metric** | **Value** | **Last Quarter Value** | **% Change** |📝 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.
| | **X (Formerly Twitter) Metric** | **Value** |**% last Quarter** |**% Change** | | |
| | **X (Formerly Twitter) Metric** | **Value** | **Last Quarter Value** | **% Change** | |
🤖 Prompt for AI Agents
In markdown/blog/2025-Q1-marketing-report.md at line 48, update the third column
header of the X metrics table from "% last Quarter" to "Last Quarter Value" to
match the LinkedIn table header for consistency.
|
Hey folks, Is there a reason this PR isn’t merged? It’s been two months now. If there is anything I still need to change, please let me know. |
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (5)
markdown/blog/2025-Q1-marketing-report.md (5)
14-14: Excerpt matches previous suggestion
The front-matterexcerptexactly matches derberg’s approved wording from earlier feedback.
17-17: Intro aligns with suggested phrasing
The opening sentence uses TRohit20’s recommended wording about “expanding community reach, driving awareness…”, which was already proposed and applied.
25-25: Objective bullet matches past suggestion
The “Promote AsyncAPI-led events and initiatives…” line corresponds to TRohit20’s recommended list item.
108-109: Webinar bullet updated per earlier comment
The March 14 webinar item now matches TRohit20’s suggested link text and comma placement.
48-48: 🛠️ Refactor suggestionUnify X table header label
To match the LinkedIn metrics table, rename the third column from “% last Quarter” to “Last Quarter Value.”-| **X (Formerly Twitter) Metric** | **Value** |**% last Quarter** |**% Change** | +| **X (Formerly Twitter) Metric** | **Value** | **Last Quarter Value** | **% Change** |
🧹 Nitpick comments (6)
markdown/blog/2025-Q1-marketing-report.md (6)
38-38: Consistent number formatting in LinkedIn table
The “Last Quarter Value” for Clicks reads1398; consider formatting with a comma (1,398) to match other numbers.-| Clicks | 1,495| 1398 | +8% | +| Clicks | 1,495 | 1,398 | +8% |
71-71: Remove extra space in alt text
The alt text has two spaces between “AsyncAPI” and “Google”—please remove the extra space for consistency.- alt="A table showing AsyncAPI Google Analytics Homepage performance from January to March" + alt="A table showing AsyncAPI Google Analytics Homepage performance from January to March"
93-93: Add comma before 'but' in compound sentence
Use a comma before “but” to separate independent clauses per style guide:- "Generator" and "Tools" saw good traffic but experienced drops in average time spent. + "Generator" and "Tools" saw good traffic, but experienced drops in average time spent.🧰 Tools
🪛 LanguageTool
[uncategorized] ~93-~93: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ..."Generator" and "Tools" saw good traffic but experienced drops in average time spent...(COMMA_COMPOUND_SENTENCE_2)
121-121: Link the Munich Call for Speakers
The “Munich Call for Speaker is also out” bullet would benefit from a direct link to the CFP page.
132-143: Standardize nested list indentation
The nested bullets under “To sustain and scale this initiative” use inconsistent indentation (two spaces). Align with four-space nesting throughout:- - Host monthly live sessions... + - Host monthly live sessions...
156-156: Remove duplicate word in metrics list
The first post’s impressions line redundantly repeats “Impressions.” Please drop the second instance:- - Impressions: 2,470 Impressions + - Impressions: 2,470
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-Q1-marketing-report.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-Q1-marketing-report.md
[uncategorized] ~44-~44: A determiner appears to be missing. Consider inserting it.
Context: ...owing interest in AsyncAPI’s content. - Engagement rate increased by 13%, indicating that ...
(AI_EN_LECTOR_MISSING_DETERMINER)
[style] ~83-~83: Consider a different adjective to strengthen your wording.
Context: ... with a solid 41s average time, showing deep interest in the newest spec release. *...
(DEEP_PROFOUND)
[uncategorized] ~93-~93: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ..."Generator" and "Tools" saw good traffic but experienced drops in average time spent...
(COMMA_COMPOUND_SENTENCE_2)
[style] ~128-~128: Consider a different adjective to strengthen your wording.
Context: ...real-world applications. Eduardo shared deep insights into event-driven architecture...
(DEEP_PROFOUND)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2025-Q1-marketing-report.md
81-81: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
85-85: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
91-91: Emphasis used instead of a heading
null
(MD036, no-emphasis-as-heading)
⏰ 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 (2)
markdown/blog/2025-Q1-marketing-report.md (2)
3-3: Verify publication date
Derberg requested bumping the report date to reflect the actual publication day. Please confirm thatdate: 2025-05-27T06:00:00+01:00is correct, or update it to the intended go-live date.
203-210: Overall LGTM with minor refinements above
Great to see the Q1 marketing report in shape—just a few small tweaks for consistency and style.
| **User Engagement Insights (Google Analytics)** | ||
| **Homepage Performance** | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Replace emphasis with semantic headings
Markdown lint flags use of **…** for section titles. Convert to appropriate heading levels for accessibility and structure:
- **User Engagement Insights (Google Analytics)**
- **Homepage Performance**
+ ### User Engagement Insights (Google Analytics)
+ #### Homepage Performance
- **High Engagement Pages**
+ #### High Engagement Pages
- **Notable Drops**
+ #### Notable DropsAlso applies to: 85-85, 91-91
🤖 Prompt for AI Agents
In markdown/blog/2025-Q1-marketing-report.md at lines 76-78, 85, and 91, replace
the bold text used for section titles (marked with **) with proper markdown
headings using hash symbols (#) to improve accessibility and document structure.
Choose heading levels that reflect the document hierarchy appropriately.
|
@iambami, to be honest, it's two weeks |
|
/rtm |
Description
Hello folks,
As promised, here is the first quarter marketing report.
I hope to add more details to it before the published date, as some of the PRs have not been merged.
In the meantime, I will be looking forward to your reviews and suggestions.
Summary by CodeRabbit