chore(blog): add q2 marketing report #4319
Conversation
iambami
requested review from
Mayaleeeee,
TRohit20,
akshatnema,
anshgoyalevil,
asyncapi-bot-eve,
derberg,
sambhavgupta0705 and
thulieblack
as code owners
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
WalkthroughA new markdown file containing the Q2 2025 marketing report was added to the blog directory. The report details AsyncAPI's marketing activities, strategies, performance metrics, and future outlook for Q2 2025, including community engagement, event participation, and social media analytics. Changes
Sequence Diagram(s)No sequence diagram generated as the change is limited to adding a static markdown report. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Note 🔌 MCP (Model Context Protocol) integration is now available in Early Access!Pro users can now connect to remote MCP servers under the Integrations page to get reviews and chat conversations that understand additional development context. ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
asyncapi-bot
requested review from
CBID2,
ashmitjsg,
bandantonio and
vishvamsinh28
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4319 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 22 22
Lines 778 778
Branches 144 144
=========================================
Hits 778 778 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-4319--asyncapi-website.netlify.app/ |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
🧹 Nitpick comments (5)
markdown/blog/2025-Q2-marketing-report.md (5)
3-3: Verify publish date and update cover to Q2 image
- Date: If this will publish post-Q2, confirm you want the post dated May 27 (affects sort/order). Community Spotlight posts must use publication date (per past learning), but this is a marketing report; still, please confirm preferred convention.
- Cover: The image filename references Q1. Suggest updating to Q2.
- cover: /img/posts/marketing-images/marketing-q1-report.webp + cover: /img/posts/marketing-images/marketing-q2-report.webpAlso applies to: 8-8
215-219: Empty “Slack Performance” section – add content or removeThis heading has no content. Either add Slack KPIs/insights or remove the section to avoid a dangling header.
-### Slack Performance - - - -
56-57: Grammar fix for “Gap/Next steps” sentenceMinor but noticeable grammar issue.
-Multilingual documentation target (one translation by end of Q2) was planned in the strategy, work was but has not been initiated. +Multilingual documentation (one translation by end of Q2) was planned in the strategy, but the work has not been initiated.
257-257: Fix list formatting and commas in the post title (item 2)
- Add space after “2.”
- Remove stray comma after “at”.
- Add comma after “Aklivity”.
-2.[Ankit Kumar, Head of Developer and Customer Success at,Aklivity is speaking on "AsyncAPI v3: Streamlining Event-Driven API Design"](https://www.linkedin.com/feed/update/urn:li:ugcPost:7318133926613401600/) +2. [Ankit Kumar, Head of Developer and Customer Success at Aklivity, is speaking on "AsyncAPI v3: Streamlining Event-Driven API Design"](https://www.linkedin.com/feed/update/urn:li:ugcPost:7318133926613401600/)
289-289: Clarify the Q3 bulletAdd a verb for consistency with surrounding bullets.
-- Q3 report +- Publish Q3 report
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-Q2-marketing-report.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.
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.
📚 Learning: 2025-06-03T06:48:09.304Z
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-Q2-marketing-report.md
🪛 LanguageTool
markdown/blog/2025-Q2-marketing-report.md
[grammar] ~96-~96: Ensure spelling is correct
Context: ...tor surveys to close feedback loops. Recomendation - Targeted email campaigns - AMAs a...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~153-~153: Consider a different verb to strengthen your wording.
Context: ..., clicks dipped by 7% and new followers dropped by 25%, indicating that while interacti...
(DROP_DECLINE)
[grammar] ~157-~157: Ensure spelling is correct
Context: ...our spec and tools update. ### Website Performace **User Engagement Insights (Google Ana...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~177-~177: To form a complete sentence, be sure to include a subject.
Context: ... example-driven content resonates. - Could be promoted more heavily to increase tr...
(MISSING_IT_THERE)
[grammar] ~215-~215: Ensure spelling is correct
Context: ...nt and Community Engagement ### Slack Performace ### The AsyncAPI Webinar Initiative...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~221-~221: Ensure spelling is correct
Context: ...in the most part of Q3. [The initiative documetation was merged in June](https://github.com/...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🪛 markdownlint-cli2 (0.17.2)
markdown/blog/2025-Q2-marketing-report.md
39-39: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
47-47: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
54-54: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
61-61: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
65-65: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
71-71: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
78-78: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
84-84: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
90-90: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
96-96: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
108-108: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe
(MD055, table-pipe-style)
108-108: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe
(MD055, table-pipe-style)
109-109: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe
(MD055, table-pipe-style)
109-109: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe
(MD055, table-pipe-style)
110-110: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe
(MD055, table-pipe-style)
110-110: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe
(MD055, table-pipe-style)
111-111: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe
(MD055, table-pipe-style)
111-111: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe
(MD055, table-pipe-style)
115-115: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
116-116: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
117-117: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
118-118: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
119-119: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
120-120: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
134-134: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
136-136: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
137-137: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
138-138: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
139-139: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
140-140: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
141-141: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
142-142: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
143-143: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
159-159: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
161-161: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
183-183: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
193-193: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
203-203: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: Redirect rules - asyncapi-website
- GitHub Check: Header rules - asyncapi-website
- GitHub Check: Pages changed - asyncapi-website
🔇 Additional comments (1)
markdown/blog/2025-Q2-marketing-report.md (1)
86-89: Slack growth inconsistency: +9.4% vs +3.03%Narrative states Slack growth +9.4% (Lines 88-89), while the table shows +3.03% (Line 110-111). Please reconcile these numbers or clarify the basis (e.g., month-over-month vs quarter-over-quarter).
Also applies to: 110-111
|
|
||
| ### Goal 1 — Encourage Adoption of AsyncAPI & EDA | ||
|
|
||
| **Q2 Activities** |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Fix markdownlint MD036: use headings instead of bold for section labels
Bold text is used as headings; convert to proper heading levels for structure and lint compliance.
-**Q2 Activities**
+#### Q2 Activities
-**Evidence**
+#### Evidence
-**Gap/Next steps**
+#### Gaps and next steps
-**Q2 Activities**
+#### Q2 Activities
-**Evidence**
+#### Evidence
-**Next steps**
+#### Next steps
-**Q2 Activities**
+#### Q2 Activities
-**Evidence**
+#### Evidence
-**Next steps**
+#### Next steps
-**Recomendation**
+#### Recommendations
-**User Engagement Insights (Google Analytics)**
+#### User Engagement Insights (Google Analytics)
-**High Traffic, Low Engagement**
+#### High Traffic, Low Engagement
-**High Engagement, Lower Traffic**
+#### High Engagement, Lower Traffic
-**Low Traffic, Moderate Engagement**
+#### Low Traffic, Moderate Engagement
-**Notable Drops**
+#### Notable Drops
-**Key Insights**
+#### Key InsightsAlso applies to: 47-47, 54-54, 61-61, 65-65, 71-71, 78-78, 84-84, 90-90, 96-96, 159-159, 161-161, 171-171, 183-183, 193-193, 203-203
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
39-39: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
🤖 Prompt for AI Agents
In markdown/blog/2025-Q2-marketing-report.md at lines 39, 47, 54, 61, 65, 71,
78, 84, 90, 96, 159, 161, 171, 183, 193, and 203, replace bold text used as
section labels with proper markdown headings by adding appropriate heading
markers (#) to improve document structure and comply with markdownlint MD036.
|
|
||
| **Q2 Activities** | ||
|
|
||
| - AsyncAPI track at APIDays Singapore |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Branding, capitalization, and event copy fixes
- APIdays brand capitalization.
- Clearer wording for CFP promotions.
- Subject-verb agreement and brand casing.
- Consistent capitalization for “Key Insight”.
-- AsyncAPI track at APIDays Singapore
+- AsyncAPI track at APIdays Singapore
-### X (Twitter) Key insight
+### X (Twitter) Key Insight
-- Organized a spotlighted AsyncAPI track at APIDays Singapore.
+- Organized a spotlighted AsyncAPI track at APIdays Singapore.
-- May–June promotion focused on Bangalore CFP Munich and Lagos conference.
+- May–June promotion focused on CFPs for Munich and Lagos conferences.
-- Paris, Developerweek, and Online CFP is now open
+- Paris, DeveloperWeek, and online CFPs are now openAlso applies to: 233-233, 239-241, 145-145
🤖 Prompt for AI Agents
In markdown/blog/2025-Q2-marketing-report.md at lines 41, 145, 233, and 239-241,
fix branding and capitalization issues by correcting "APIdays" to the proper
brand capitalization "APIDays," improve clarity in CFP promotion wording, ensure
subject-verb agreement, and maintain consistent capitalization for the phrase
"Key Insight." Review these lines carefully and update the text accordingly to
align with the brand and style guidelines.
| | **Platform** | **Start of Q2** | **End of Q2** | **% Change** | **Key Insights**| | ||
| |---------|-------------|-----------|-----------|-------------| | ||
| LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts), impressions doubled.click-throughs and engagement increased significantly | ||
| X (Twitter) | 4732 | 4759 | +0.57% | Increased tweet output and engagement. Slight dip in new followers and retweets | ||
| Slack | 6889 | 7098 | +3.03% | Community chats intensified around GSOC and event prep | ||
| Newsletter | ~6.8k | ~7.3k | +7.3% | Open rate ~42%, CTR above industry benchmark | ||
|
|
There was a problem hiding this comment.
Fix markdownlint MD055: add leading/trailing pipes and polish copy in the summary table
The table is missing leading/trailing pipes and has a punctuation issue on the LinkedIn row.
-| **Platform** | **Start of Q2** | **End of Q2** | **% Change** | **Key Insights**|
-|---------|-------------|-----------|-----------|-------------|
-LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts), impressions doubled.click-throughs and engagement increased significantly
-X (Twitter) | 4732 | 4759 | +0.57% | Increased tweet output and engagement. Slight dip in new followers and retweets
-Slack | 6889 | 7098 | +3.03% | Community chats intensified around GSOC and event prep
-Newsletter | ~6.8k | ~7.3k | +7.3% | Open rate ~42%, CTR above industry benchmark
+| Platform | Start of Q2 | End of Q2 | % Change | Key Insights |
+|------------|-------------|-----------|----------|--------------|
+| LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts); impressions doubled; click-throughs and engagement increased significantly |
+| X (Twitter)| 4,732 | 4,759 | +0.57% | Increased tweet output and engagement. Slight dip in new followers and retweets |
+| Slack | 6,889 | 7,098 | +3.03% | Community chats intensified around GSoC and event prep |
+| Newsletter | ~6.8k | ~7.3k | +7.3% | Open rate ~42%, CTR above industry benchmark |📝 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.
| | **Platform** | **Start of Q2** | **End of Q2** | **% Change** | **Key Insights**| | |
| |---------|-------------|-----------|-----------|-------------| | |
| LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts), impressions doubled.click-throughs and engagement increased significantly | |
| X (Twitter) | 4732 | 4759 | +0.57% | Increased tweet output and engagement. Slight dip in new followers and retweets | |
| Slack | 6889 | 7098 | +3.03% | Community chats intensified around GSOC and event prep | |
| Newsletter | ~6.8k | ~7.3k | +7.3% | Open rate ~42%, CTR above industry benchmark | |
| | Platform | Start of Q2 | End of Q2 | % Change | Key Insights | | |
| |------------|-------------|-----------|----------|--------------| | |
| | LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts); impressions doubled; click-throughs and engagement increased significantly | | |
| | X (Twitter)| 4,732 | 4,759 | +0.57% | Increased tweet output and engagement. Slight dip in new followers and retweets | | |
| | Slack | 6,889 | 7,098 | +3.03% | Community chats intensified around GSoC and event prep | | |
| | Newsletter | ~6.8k | ~7.3k | +7.3% | Open rate ~42%, CTR above industry benchmark | |
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
108-108: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe
(MD055, table-pipe-style)
108-108: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe
(MD055, table-pipe-style)
109-109: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe
(MD055, table-pipe-style)
109-109: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe
(MD055, table-pipe-style)
110-110: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe
(MD055, table-pipe-style)
110-110: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe
(MD055, table-pipe-style)
111-111: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe
(MD055, table-pipe-style)
111-111: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe
(MD055, table-pipe-style)
🤖 Prompt for AI Agents
In markdown/blog/2025-Q2-marketing-report.md around lines 106 to 112, the
markdown table lacks leading and trailing pipe characters on each line, which is
required for proper table formatting. Additionally, the LinkedIn row has a
punctuation issue where a period is missing between "impressions doubled" and
"click-throughs." Add the missing leading and trailing pipes to every table row
and insert the missing period to correct the punctuation in the LinkedIn row.
| | **Platform** | **Start of Q2** | **End of Q2** | **% Change** | **Key Insights**| | ||
| |---------|-------------|-----------|-----------|-------------| | ||
| LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts), impressions doubled.click-throughs and engagement increased significantly | ||
| X (Twitter) | 4732 | 4759 | +0.57% | Increased tweet output and engagement. Slight dip in new followers and retweets | ||
| Slack | 6889 | 7098 | +3.03% | Community chats intensified around GSOC and event prep | ||
| Newsletter | ~6.8k | ~7.3k | +7.3% | Open rate ~42%, CTR above industry benchmark | ||
|
|
||
| | **LinkedIn Performance** | **Value** | **Last Quarter Value** | **% Change** | | ||
| |:------------|:-----------|:-------------|:---------------| | ||
| Followers | 4,534 | 4,255 | (+7%) | | ||
| New Followers| 285 | 313 | (-7%) | | ||
| Posts | 78 | 48 | (+63%) | | ||
| Impressions | 48,443 | 23,715 | (+104%) | | ||
| Clicks | 3,007 | 1,495 | (+101%) | | ||
| Engagement Rate | 8.06% | 7.52% | (+11%) | | ||
|
|
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Frontmatter and blog schema parity check with existing posts
Please verify that frontmatter keys (type, tags, authors, cover) match existing blog conventions (some posts use author vs authors, different type values). Also ensure tables render properly on the site theme.
Also applies to: 134-144, 1-15
🏁 Script executed:
#!/bin/bash
# Compare frontmatter patterns against existing blog posts
fd -e md markdown/blog | xargs -I{} sh -c '
echo "== {} ==";
head -n 30 "{}" | sed -n "1,30p" | rg -n "^(title|date|type|tags|cover|author|authors):"
'
echo
echo "Check common values for \`type:\`"
rg -n "^type:\s" markdown/blog | cut -d: -f3 | sort | uniq -c
echo
echo "Sample a known marketing report for reference (if present):"
fd -e md "marketing" markdown/blog | xargs -I{} sh -c 'echo "-- {} --"; head -n 30 "{}"'Length of output: 6054
Frontmatter keys are consistent; tables need proper row delimiters
I’ve verified that the frontmatter in 2025-Q2-marketing-report.md (lines 1–15) uses the same keys as other marketing reports (title, date, type: Communication, tags, cover, authors, excerpt), so no changes are needed there.
However, to ensure both tables render correctly under our site theme, please update the markdown so every data row starts and ends with a pipe. For example:
-
In the first table (lines 106–121), change
LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence…to
| LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence… | -
Apply the same leading/trailing
|to all rows in the second table (lines 134–144).
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
108-108: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe
(MD055, table-pipe-style)
108-108: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe
(MD055, table-pipe-style)
109-109: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe
(MD055, table-pipe-style)
109-109: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe
(MD055, table-pipe-style)
110-110: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe
(MD055, table-pipe-style)
110-110: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe
(MD055, table-pipe-style)
111-111: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe
(MD055, table-pipe-style)
111-111: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe
(MD055, table-pipe-style)
115-115: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
116-116: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
117-117: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
118-118: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
119-119: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
120-120: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
🤖 Prompt for AI Agents
In markdown/blog/2025-Q2-marketing-report.md between lines 106 and 121, the
tables lack leading and trailing pipe characters on each data row, which can
cause rendering issues. Update every row in both tables to start and end with a
pipe character (|), ensuring consistent markdown table syntax for proper display
under the site theme.
| | **LinkedIn Performance** | **Value** | **Last Quarter Value** | **% Change** | | ||
| |:------------|:-----------|:-------------|:---------------| | ||
| Followers | 4,534 | 4,255 | (+7%) | | ||
| New Followers| 285 | 313 | (-7%) | | ||
| Posts | 78 | 48 | (+63%) | | ||
| Impressions | 48,443 | 23,715 | (+104%) | | ||
| Clicks | 3,007 | 1,495 | (+101%) | | ||
| Engagement Rate | 8.06% | 7.52% | (+11%) | | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Fix markdownlint MD055: add leading/trailing pipes to LinkedIn metrics table
Rows are missing leading pipes. Add pipes for consistency and lint compliance.
-| **LinkedIn Performance** | **Value** | **Last Quarter Value** | **% Change** |
-|:------------|:-----------|:-------------|:---------------|
-Followers | 4,534 | 4,255 | (+7%) |
-New Followers| 285 | 313 | (-7%) |
-Posts | 78 | 48 | (+63%) |
-Impressions | 48,443 | 23,715 | (+104%) |
-Clicks | 3,007 | 1,495 | (+101%) |
-Engagement Rate | 8.06% | 7.52% | (+11%) |
+| LinkedIn Performance | Value | Last Quarter Value | % Change |
+|:---------------------|:------|:-------------------|:---------|
+| Followers | 4,534 | 4,255 | (+7%) |
+| New Followers | 285 | 313 | (-7%) |
+| Posts | 78 | 48 | (+63%) |
+| Impressions | 48,443| 23,715 | (+104%) |
+| Clicks | 3,007 | 1,495 | (+101%) |
+| Engagement Rate | 8.06% | 7.52% | (+11%) |📝 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.
| | **LinkedIn Performance** | **Value** | **Last Quarter Value** | **% Change** | | |
| |:------------|:-----------|:-------------|:---------------| | |
| Followers | 4,534 | 4,255 | (+7%) | | |
| New Followers| 285 | 313 | (-7%) | | |
| Posts | 78 | 48 | (+63%) | | |
| Impressions | 48,443 | 23,715 | (+104%) | | |
| Clicks | 3,007 | 1,495 | (+101%) | | |
| Engagement Rate | 8.06% | 7.52% | (+11%) | | |
| | LinkedIn Performance | Value | Last Quarter Value | % Change | | |
| |:---------------------|:------|:-------------------|:---------| | |
| | Followers | 4,534 | 4,255 | (+7%) | | |
| | New Followers | 285 | 313 | (-7%) | | |
| | Posts | 78 | 48 | (+63%) | | |
| | Impressions | 48,443| 23,715 | (+104%) | | |
| | Clicks | 3,007 | 1,495 | (+101%) | | |
| | Engagement Rate | 8.06% | 7.52% | (+11%) | |
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
115-115: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
116-116: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
117-117: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
118-118: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
119-119: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
120-120: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
🤖 Prompt for AI Agents
In markdown/blog/2025-Q2-marketing-report.md around lines 113 to 121, the
LinkedIn metrics table rows are missing leading pipes, which violates
markdownlint rule MD055. Add a leading pipe character at the start of each row
to ensure consistent table formatting and compliance with markdownlint.
| **Twitter/X Performance** | **Value** | **Last Quarter Value** | **% Change** | | ||
| |:------------|:--------------|:-------------|:----------| | ||
| Tweets | 119 | 89 | (+34%) | | ||
| Retweets | 21 | 24 | (-16%) | | ||
| Impressions | 17,500 | 14,621 | (+20%) | | ||
| Engagements | 280 | 278 | (+1%) | | ||
| Replies | 5 | 3 | (+67%) | | ||
| Clicks | 93 | 101 | (-7%) | | ||
| Likes | 110 | 93 | (+18%) | | ||
| New Followers| 27 | 36 | (-25%) | | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Fix markdownlint MD055: add leading/trailing pipes to X (Twitter) metrics table
Rows are missing leading pipes.
-**Twitter/X Performance** | **Value** | **Last Quarter Value** | **% Change** |
-|:------------|:--------------|:-------------|:----------|
-Tweets | 119 | 89 | (+34%) |
-Retweets | 21 | 24 | (-16%) |
-Impressions | 17,500 | 14,621 | (+20%) |
-Engagements | 280 | 278 | (+1%) |
-Replies | 5 | 3 | (+67%) |
-Clicks | 93 | 101 | (-7%) |
-Likes | 110 | 93 | (+18%) |
-New Followers| 27 | 36 | (-25%) |
+| Twitter/X Performance | Value | Last Quarter Value | % Change |
+|:----------------------|:------|:-------------------|:---------|
+| Tweets | 119 | 89 | (+34%) |
+| Retweets | 21 | 24 | (-16%) |
+| Impressions | 17,500| 14,621 | (+20%) |
+| Engagements | 280 | 278 | (+1%) |
+| Replies | 5 | 3 | (+67%) |
+| Clicks | 93 | 101 | (-7%) |
+| Likes | 110 | 93 | (+18%) |
+| New Followers | 27 | 36 | (-25%) |📝 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.
| **Twitter/X Performance** | **Value** | **Last Quarter Value** | **% Change** | | |
| |:------------|:--------------|:-------------|:----------| | |
| Tweets | 119 | 89 | (+34%) | | |
| Retweets | 21 | 24 | (-16%) | | |
| Impressions | 17,500 | 14,621 | (+20%) | | |
| Engagements | 280 | 278 | (+1%) | | |
| Replies | 5 | 3 | (+67%) | | |
| Clicks | 93 | 101 | (-7%) | | |
| Likes | 110 | 93 | (+18%) | | |
| New Followers| 27 | 36 | (-25%) | | |
| | Twitter/X Performance | Value | Last Quarter Value | % Change | | |
| |:----------------------|:------|:-------------------|:---------| | |
| | Tweets | 119 | 89 | (+34%) | | |
| | Retweets | 21 | 24 | (-16%) | | |
| | Impressions | 17,500| 14,621 | (+20%) | | |
| | Engagements | 280 | 278 | (+1%) | | |
| | Replies | 5 | 3 | (+67%) | | |
| | Clicks | 93 | 101 | (-7%) | | |
| | Likes | 110 | 93 | (+18%) | | |
| | New Followers | 27 | 36 | (-25%) | |
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
134-134: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
136-136: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
137-137: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
138-138: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
139-139: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
140-140: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
141-141: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
142-142: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
143-143: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe
(MD055, table-pipe-style)
🤖 Prompt for AI Agents
In markdown/blog/2025-Q2-marketing-report.md around lines 134 to 144, the
markdown table for Twitter/X performance metrics is missing leading pipes on
each row. Add a leading pipe character '|' at the start of every row in the
table to comply with markdownlint MD055 and ensure proper table formatting.
|
|
||
| - However, clicks dipped by 7% and new followers dropped by 25%, indicating that while interaction is happening, conversion to action and follower acquisition needs targeted focus. | ||
|
|
||
| Strategy alignment: The conversational engagement aligns with our community-first approach, but the drop in clicks and followers signals a need to balance interaction with calls-to-action and shareable content. Also we have decided to keep the automated tweets as they serve folks that are not on the Slack channel but still needs our spec and tools update. |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Fix typos and grammar for clarity and professionalism
Addresses LanguageTool findings and general wording.
-Also we have decided to keep the automated tweets as they serve folks that are not on the Slack channel but still needs our spec and tools update.
+Also, we have decided to keep the automated tweets, as they serve folks who are not on the Slack channel but still need our spec and tools updates.
-### Website Performace
+### Website Performance
-### Slack Performace
+### Slack Performance
-... first session is set to happen in September as everyone will be on summer holiday in the most part of Q3. [The initiative documetation was merged in June]...
+... first session is set to happen in September, as many will be on summer holiday for most of Q3. [The initiative documentation was merged in June]...
-Also, we took the libarty to create the [webinar planning template](...) that help us make sure we are on track with the planning and you can stay up-to-date with the webinar [here](...).
+Also, we took the liberty of creating the [webinar planning template](...), which helps us stay on track with planning; you can stay up to date with the webinar [here](...).Also applies to: 157-157, 215-215, 221-221, 223-223
🤖 Prompt for AI Agents
In markdown/blog/2025-Q2-marketing-report.md at lines 155, 157, 215, 221, and
223, fix typos and improve grammar for clarity and professionalism. Review each
sentence for proper punctuation, subject-verb agreement, and consistent tense.
Rephrase awkward or unclear wording to enhance readability while maintaining the
original meaning.
| **Evidence** | ||
|
|
||
| - Strong in-person attendance in Singapore | ||
| - Webinar engagement and repurposed content |
There was a problem hiding this comment.
is it evidence we have or we plan to have as a measure?
| - Strong in-person attendance in Singapore | ||
| - Webinar engagement and repurposed content | ||
| - Newsletter open rate of 42%; | ||
| - AsyncAPI Singapore recap video (1.8k views). |
|
|
||
| - The "Learn With AsyncAPI" webinar series documentation has been merged and the first session is on the 30th of September. | ||
|
|
||
| - Conference workshops and hands-on sessions |
| **Gap/Next steps** | ||
|
|
||
| Multilingual documentation target (one translation by end of Q2) was planned in the strategy, work was but has not been initiated. | ||
| Recommend prioritizing at least one translated guide, and preparing localized workshop materials for Lagos. |
There was a problem hiding this comment.
what are the localized workshop materials for Lagos?
|
|
||
| **Next steps** | ||
|
|
||
| - Scale the Student Ambassador Program promotion and onboarding (Q3 focus) |
There was a problem hiding this comment.
this is not merged, nor in progress? I would pause this initiative, I personally don't think it is needed atm, would leave it for new board to discuss
|
|
||
| | **Platform** | **Start of Q2** | **End of Q2** | **% Change** | **Key Insights**| | ||
| |---------|-------------|-----------|-----------|-------------| | ||
| LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts), impressions doubled.click-throughs and engagement increased significantly |
There was a problem hiding this comment.
| LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts), impressions doubled.click-throughs and engagement increased significantly | |
| LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts), impressions doubled, click-throughs and engagement increased significantly |
|
|
||
| Strategy alignment: The conversational engagement aligns with our community-first approach, but the drop in clicks and followers signals a need to balance interaction with calls-to-action and shareable content. Also we have decided to keep the automated tweets as they serve folks that are not on the Slack channel but still needs our spec and tools update. | ||
|
|
||
| ### Website Performace |
There was a problem hiding this comment.
I love the level of details here, but please can you also provide links to these pages?
|
|
||
| ## Q3 Outlook | ||
|
|
||
| - Host AsyncAPI Munich and AsyncAPI Lagos conferences successfully. |
There was a problem hiding this comment.
it's weird to read it in August, when it already happened
|
|
||
| - Post-event engagement: recap content, speaker highlights, and contributor recognition. | ||
|
|
||
| - Introduce “Meet the Maintainer” and “First Contributor” series. |
There was a problem hiding this comment.
don't start too many new initiatives without first polishing the existing ones
| Clicks | 3,007 | 1,495 | (+101%) | | ||
| Engagement Rate | 8.06% | 7.52% | (+11%) | | ||
|
|
||
| ### LinkedIn Key Insight |
There was a problem hiding this comment.
I like these insignts, but missing deep dive into specific posts. What is our learning here?
- is it that some specific type of posts engage more?
- or is it posts with pictures
- or is it the time they are published? like majority of stuff published on Tuesday are move visible?
- or maybe the only answer is, if you want more engagement, visibility and followers, you should produce much more content - doesn't matter when and what?
I'm also very much interested with our youtube, expecially the educational content with Ace. How promotion of it work, what we learned? maybe we should "repromote", like not share it once and forget, but write about it, in different style, once a month? with shorts, maybe with video shared directly in LinkedIn? not as a YT link
|
Hi @iambami |
|
This pull request has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation. There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
4 participants
Hey folks,
This is the marketing q2 report. It’s still undergoing construction but your reviews are welcome.
Thank you.
@derberg @thulieblack @antoniogarrote @TRohit20
Summary by CodeRabbit