docs: bami added marketing report #3439
Conversation
iambami
requested review from
thulieblack,
quetzalliwrites,
derberg,
akshatnema,
magicmatatjahu,
anshgoyalevil,
Mayaleeeee and
asyncapi-bot-eve
as code owners
WalkthroughA new file, Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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 site configuration. |
asyncapi-bot
requested review from
devilkiller-ag,
sambhavgupta0705,
BhaswatiRoy,
J0SAL,
TRohit20 and
VaishnaviNandakumar
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3439 +/- ##
=======================================
Coverage 77.22% 77.22%
=======================================
Files 21 21
Lines 663 663
=======================================
Hits 512 512
Misses 151 151 ☔ View full report in Codecov by Sentry. |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-3439--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: 3
🧹 Outside diff range and nitpick comments (4)
markdown/blog/2024-marketing-report.md (4)
13-13: Consider shortening the excerpt for better readability.The current excerpt is quite lengthy. Consider condensing it to focus on the key message while maintaining its impact.
-excerpt: 'Marketing plays a crucial role in the success of open source projects, bridging the gap between technical excellence and community engagement. In this Marketing Working Group report, we explore how strategic campaigns, streamlined social media efforts, and targeted programs like the Student Ambassador initiative drive awareness and foster growth in the AsyncAPI community.' +excerpt: 'Discover how the AsyncAPI Marketing Working Group drives community growth through strategic campaigns, social media efforts, and initiatives like the Student Ambassador program in this comprehensive six-month report.'
47-47: Fix grammatical errorThere's a grammatical error in the sentence.
-Here are some of the benefit of using the Buffer subscription +Here are some of the benefits of using the Buffer subscription
82-82: Fix list formattingThe "Ambassadors" entry is missing a bullet point, breaking the list formatting.
-Ambassadors: 2 packages were sent to two new ambassadors, each containing 11 items. +- **Ambassadors:** 2 packages were sent to two new ambassadors, each containing 11 items.
125-127: Remove extra empty lines at end of fileMultiple empty lines at the end of the file should be removed.
If you have any questions, suggestions, or ideas, please feel free to reach out to me on Slack @Bami. Here's to another successful year of growth, collaboration, and impact. -
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (1)
markdown/blog/2024-marketing-report.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2024-marketing-report.md
[grammar] ~52-~52: Did you mean to use the verb ‘assure’ here?
Context: ...team members to draft posts for review, ensuring high-quality content that aligns with A...
(ENSURE_ASSURE)
[style] ~69-~69: Consider removing “of” to be more concise
Context: ...ore were 2383. The goal was to disburse all of the items by December 2024. 
+[Strategy Document](https://github.com/asyncapi/community/blob/master/marketing/strategy.md)
-[Student Ambassador Program](https://github.com/asyncapi/community/pull/1333)
+[Student Ambassador Program](https://github.com/asyncapi/community/blob/master/ambassadors/README.md)Also applies to: 97-97
|
Hello @thulieblack @quetzalliwrites Still waiting for your review. |
There was a problem hiding this comment.
Suggested minor changes, the rest looks good to me. @quetzalliwrites please give the final review :)
Co-authored-by: Rohit <[email protected]>
Co-authored-by: Rohit <[email protected]>
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (1)
markdown/blog/2024-marketing-report.md (1)
84-84: Fix bullet point formattingThe "Ambassadors" section breaks the consistent formatting of the list. Add a bullet point to maintain consistency with other items.
-Ambassadors: 2 packages were sent to two new ambassadors, each containing 11 items. +- **Ambassadors:** 2 packages were sent to two new ambassadors, each containing 11 items.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (1)
markdown/blog/2024-marketing-report.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2024-marketing-report.md
[grammar] ~54-~54: Did you mean to use the verb ‘assure’ here?
Context: ...team members to draft posts for review, ensuring high-quality content that aligns with A...
(ENSURE_ASSURE)
[style] ~71-~71: Consider removing “of” to be more concise
Context: ...ore were 2383. The goal was to disburse all of the items by December 2024. 
|
@thulieblack @derberg Can someone please review and approve this PR, as I don't have any context around this? |
|
Can I have the final review on this? |
|
|
||
| - **Community Events and Giveaways:** 25 items for various online and offline events throughout the year. | ||
|
|
||
| So far, $8,264.37 has been spent on maintaining the store and logistics. As part of the benefit of closing the store, merchandise will be made locally at the event location, and others will be made as per request. [Here](https://docs.google.com/spreadsheets/d/1K7xo-ihlHcVoSYRg1U6SsvQDreEF1S6z/r/edit/edit?gid=1275706868#gid=1275706868) is the link to the distribution board. |
There was a problem hiding this comment.
The spreadsheet link is not opening
Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
Yeah, sure. |
Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
markdown/blog/2024-marketing-report.md (2)
13-13: Consider shortening the excerpt for better readabilityThe current excerpt is quite lengthy. Consider condensing it while maintaining the key message.
-excerpt: 'Marketing plays a crucial role in the success of open source projects, bridging the gap between technical excellence and community engagement. In this Marketing Working Group report, we explore how strategic campaigns, streamlined social media efforts, and targeted programs like the Student Ambassador initiative drive awareness and foster growth in the AsyncAPI community.' +excerpt: 'Discover how the AsyncAPI Marketing Working Group drives community growth through strategic campaigns, social media efforts, and targeted programs in this comprehensive report.'
127-127: Add direct Slack profile linkConsider adding a direct link to your Slack profile for easier access.
-If you have any questions, suggestions, or ideas, please feel free to reach out to me on Slack @Bami. +If you have any questions, suggestions, or ideas, please feel free to reach out to me on [Slack](https://asyncapi.slack.com/team/U02DHQE6VBZ) (@Bami).
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (1)
markdown/blog/2024-marketing-report.md(1 hunks)
🧰 Additional context used
📓 Learnings (1)
markdown/blog/2024-marketing-report.md (1)
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.
🪛 LanguageTool
markdown/blog/2024-marketing-report.md
[grammar] ~54-~54: Did you mean to use the verb ‘assure’ here?
Context: ...team members to draft posts for review, ensuring high-quality content that aligns with A...
(ENSURE_ASSURE)
[style] ~71-~71: Consider removing “of” to be more concise
Context: ...ore were 2383. The goal was to disburse all of the items by December 2024. 
+
-
+91-91: Add alt text to store report image
The monthly store spend image needs descriptive alt text for accessibility.
-
+122-122: Add alt text to Buffer analytics image
The general Buffer report image needs descriptive alt text for accessibility.
-
+89-89:
Fix the malformed distribution board link
The Google Sheets link appears to be malformed and may not be accessible.
-[You can find all the information on the distribution board](https://docs.google.com/spreadsheets/d/1K7xo-ihlHcVoSYRg1U6SsvQDreEF1S6z/r/edit/edit?gid=1275706868#gid=1275706868)
+[You can find all the information on the distribution board](https://docs.google.com/spreadsheets/d/1K7xo-ihlHcVoSYRg1U6SsvQDreEF1S6z/edit?gid=1275706868)Likely invalid or redundant comment.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (3)
markdown/blog/2024-marketing-report.md (3)
13-13: Consider shortening the excerpt for better readabilityThe current excerpt is quite lengthy. Consider making it more concise while maintaining the key message.
-excerpt: 'Marketing plays a crucial role in the success of open source projects, bridging the gap between technical excellence and community engagement. In this Marketing Working Group report, we explore how strategic campaigns, streamlined social media efforts, and targeted programs like the Student Ambassador initiative drive awareness and foster growth in the AsyncAPI community.' +excerpt: 'Discover how the AsyncAPI Marketing Working Group drives community growth through strategic campaigns, social media efforts, and initiatives like the Student Ambassador program.'
53-53: Consider adding specific metrics and goalsWhile the analytics benefits are mentioned, it would be valuable to include specific engagement targets or KPIs that you're aiming to achieve with these insights.
127-127: Enhance contact informationConsider adding:
- A direct link to your Slack profile
- Alternative contact methods (e.g., GitHub handle)
- Preferred contact hours or response time expectations
-If you have any questions, suggestions, or ideas, please feel free to reach out to me on Slack @Bami. +If you have any questions, suggestions, or ideas, please feel free to reach out to me on [Slack](https://asyncapi.slack.com/team/U02DHQH6TD6) (@Bami) or [GitHub](https://github.com/iambami). I typically respond within 24 hours.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (1)
markdown/blog/2024-marketing-report.md(1 hunks)
🧰 Additional context used
📓 Learnings (1)
markdown/blog/2024-marketing-report.md (1)
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.
🪛 LanguageTool
markdown/blog/2024-marketing-report.md
[grammar] ~54-~54: Did you mean to use the verb ‘assure’ here?
Context: ...team members to draft posts for review, ensuring high-quality content that aligns with A...
(ENSURE_ASSURE)
[style] ~71-~71: Consider removing “of” to be more concise
Context: ...ore were 2383. The goal was to disburse all of the items by December 2024. ![Merchandise ...
(ALL_OF_THE)
🔇 Additional comments (1)
markdown/blog/2024-marketing-report.md (1)
71-86: Verify merchandise numbers
There appears to be a discrepancy in the numbers:
- Total items: 2383
- Sum of distributed items: 1970 (1518+335+40+30+22+25)
- Difference: 413 items unaccounted for
Please clarify if there are additional distributions or if some items are still in storage.
🧰 Tools
🪛 LanguageTool
[style] ~71-~71: Consider removing “of” to be more concise
Context: ...ore were 2383. The goal was to disburse all of the items by December 2024. 
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (1)
markdown/blog/2024-marketing-report.md(1 hunks)
🧰 Additional context used
📓 Learnings (1)
markdown/blog/2024-marketing-report.md (1)
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.
🪛 LanguageTool
markdown/blog/2024-marketing-report.md
[grammar] ~54-~54: Did you mean to use the verb ‘assure’ here?
Context: ...team members to draft posts for review, ensuring high-quality content that aligns with A...
(ENSURE_ASSURE)
[style] ~71-~71: Consider removing “of” to be more concise
Context: ...ore were 2383. The goal was to disburse all of the items by December 2024. 
+
-
+
-
+
-
+
-
+Also applies to: 64-64, 73-73, 91-91, 122-122
89-89:
Fix malformed distribution board link
The Google Sheets link contains duplicate edit segments in the URL.
-[You can find all the information on the distribution board](https://docs.google.com/spreadsheets/d/1K7xo-ihlHcVoSYRg1U6SsvQDreEF1S6z/r/edit/edit?gid=1275706868#gid=1275706868)
+[You can find all the information on the distribution board](https://docs.google.com/spreadsheets/d/1K7xo-ihlHcVoSYRg1U6SsvQDreEF1S6z/edit?gid=1275706868)100-100: 🛠️ Refactor suggestion
Clarify Student Ambassador Program status
The current wording implies the program is already launched, but it's still in the planning phase.
-Additionally, we're excited to introduce the [Student Ambassador Program](https://github.com/asyncapi/community/pull/1333), which aims to nurture future AsyncAPI advocates and contributors at the student level.
+Additionally, we're planning to introduce the [Student Ambassador Program](https://github.com/asyncapi/community/pull/1333), which will aim to nurture future AsyncAPI advocates and contributors at the student level.Likely invalid or redundant comment.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (1)
markdown/blog/2024-marketing-report.md (1)
127-127: Consider adding a clickable Slack linkTo make it easier for readers to reach out, consider adding a direct link to your Slack profile:
-please feel free to reach out to me on Slack @Bami +please feel free to reach out to me on [Slack](https://asyncapi.slack.com/team/U02DHQE6B02)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (1)
markdown/blog/2024-marketing-report.md(1 hunks)
🧰 Additional context used
📓 Learnings (1)
markdown/blog/2024-marketing-report.md (1)
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.
🪛 LanguageTool
markdown/blog/2024-marketing-report.md
[grammar] ~54-~54: Did you mean to use the verb ‘assure’ here?
Context: ...team members to draft posts for review, ensuring high-quality content that aligns with A...
(ENSURE_ASSURE)
[style] ~71-~71: Consider removing “of” to be more concise
Context: ...ore were 2383. The goal was to disburse all of the items by December 2024. ![Merchandise ...
(ALL_OF_THE)
🔇 Additional comments (4)
markdown/blog/2024-marketing-report.md (4)
1-15: LGTM! Metadata is well-structured and complete.
The frontmatter contains all necessary fields and follows the correct format.
62-64: Add descriptive alt text to images for accessibility
The LinkedIn and X analytics images lack meaningful alt text, which is important for accessibility.
122-122: Add alt text to Buffer General Report image
For accessibility, add descriptive alt text to the Buffer analytics image.
100-100: 🛠️ Refactor suggestion
Clarify the Student Ambassador Program status
The current wording implies the program is already active. Consider revising to clearly indicate it's a planned initiative:
-Additionally, we're excited to introduce the [Student Ambassador Program]
+Additionally, we're excited to announce our upcoming [Student Ambassador Program]Likely invalid or redundant comment.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
markdown/blog/2024-marketing-report.md (2)
13-13: Consider shortening the excerpt for better readabilityThe current excerpt is quite lengthy. Consider making it more concise while maintaining the key message.
-excerpt: 'Marketing plays a crucial role in the success of open source projects, bridging the gap between technical excellence and community engagement. In this Marketing Working Group report, we explore how strategic campaigns, streamlined social media efforts, and targeted programs like the Student Ambassador initiative drive awareness and foster growth in the AsyncAPI community.' +excerpt: 'Discover how the AsyncAPI Marketing Working Group drives community growth through strategic campaigns, social media efforts, and initiatives like the Student Ambassador program.'
127-127: Add Slack profile link for easier contactConsider adding a direct link to your Slack profile for easier contact.
-If you have any questions, suggestions, or ideas, please feel free to reach out to me on Slack @Bami. +If you have any questions, suggestions, or ideas, please feel free to reach out to me on [Slack @Bami](https://asyncapi.slack.com/team/U02DHQH1TH4).
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (1)
markdown/blog/2024-marketing-report.md(1 hunks)
🧰 Additional context used
📓 Learnings (1)
markdown/blog/2024-marketing-report.md (1)
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.
🪛 LanguageTool
markdown/blog/2024-marketing-report.md
[grammar] ~54-~54: Did you mean to use the verb ‘assure’ here?
Context: ...team members to draft posts for review, ensuring high-quality content that aligns with A...
(ENSURE_ASSURE)
[style] ~71-~71: Consider removing “of” to be more concise
Context: ...ore were 2383. The goal was to disburse all of the items by December 2024. 
+
-
+73-73: Add descriptive alt text to store-related images
The merchandise and store report images lack meaningful alt text.
-
+
-
+Also applies to: 91-91
122-122: Add descriptive alt text to Buffer analytics image
The Buffer general report image lacks meaningful alt text.
-
+89-89:
Fix the malformed distribution board link
The Google Sheets link appears to be malformed. Consider using the Open Collective link exclusively since it's publicly accessible and contains the relevant information.
-So far, $8,264.37 has been spent on maintaining the store and logistics. As part of the benefit of closing the store, merchandise will be made locally at the event location, and others will be made as per request. [You can find all the information on the distribution board](https://docs.google.com/spreadsheets/d/1K7xo-ihlHcVoSYRg1U6SsvQDreEF1S6z/r/edit/edit?gid=1275706868#gid=1275706868).
+So far, $8,264.37 has been spent on maintaining the store and logistics. As part of the benefit of closing the store, merchandise will be made locally at the event location, and others will be made as per request. For detailed information about store expenses, please refer to our [Open Collective page](https://opencollective.com/asyncapi/expenses?type=INVOICE&period=2023-12-31T23%3A00%3A00.000Z%E2%86%92all&searchTerm=Pinnacle+Branding&offset=0&limit=10).Likely invalid or redundant comment.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (3)
markdown/blog/2024-marketing-report.md (3)
13-13: Enhance the excerpt for better clarity and professionalismThe current excerpt uses the abbreviation "SM" and could be more specific about AsyncAPI's marketing initiatives.
-excerpt: 'Marketing is key to open source success, connecting technical excellence with community engagement. It highlights strategic initiatives and SM efforts' +excerpt: 'Discover how AsyncAPI's marketing initiatives are bridging technical excellence with community engagement through strategic campaigns and social media outreach'
151-154: Add implementation timelines for key initiativesConsider adding specific timelines or target dates for the implementation of these key initiatives to help set clear expectations for the community.
-**Implementing the Strategy Document:** Utilizing our strategic roadmap to guide all our activities and initiatives +**Implementing the Strategy Document (Q1 2024):** Utilizing our strategic roadmap to guide all our activities and initiatives -**Launching the Student Ambassador Program:** Engaging students worldwide to represent and support AsyncAPI within their schools and networks +**Launching the Student Ambassador Program (Q2 2024):** Engaging students worldwide to represent and support AsyncAPI within their schools and networks
184-184: Update the Slack mention with proper link formatThe Slack mention should use the proper link format for better accessibility.
-If you have any questions, suggestions, or ideas, please feel free to reach out to me on Slack [@Bami](U070DE02VQX). Here's to another successful year of growth, collaboration, and impact. +If you have any questions, suggestions, or ideas, please feel free to reach out to me on [Slack](https://asyncapi.slack.com/team/U070DE02VQX) (@Bami). Here's to another successful year of growth, collaboration, and impact.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (1)
markdown/blog/2024-marketing-report.md(1 hunks)
🧰 Additional context used
📓 Learnings (1)
markdown/blog/2024-marketing-report.md (1)
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.
🪛 LanguageTool
markdown/blog/2024-marketing-report.md
[grammar] ~54-~54: Did you mean to use the verb ‘assure’ here?
Context: ...team members to draft posts for review, ensuring high-quality content that aligns with A...
(ENSURE_ASSURE)
[style] ~113-~113: Consider removing “of” to be more concise
Context: ...ore were 2383. The goal was to disburse all of the items by December 2024. .
+So far, $8,264.37 has been spent on maintaining the store and logistics. As part of the benefit of closing the store, merchandise will be made locally at the event location, and others will be made as per request.Likely invalid or redundant comment.
90-102: Verify the reported percentage increases for X (Twitter) metrics
The reported percentage increases appear unusually high (e.g., 25,300% for tweets, 5.04M% for impressions). Consider:
- Verifying the calculation methodology
- Providing context about the baseline period
- Using absolute numbers instead of percentages if the baseline was near zero
✅ Verification successful
Based on the search results, I can see that this is a marketing report for 2024 and there's a clear context about social media metrics. Looking at the file path markdown/blog/2024-marketing-report.md, I can see this is the first marketing report for 2024, and there's no previous monthly or quarterly report from 2024 to compare with.
The high percentage increases make more sense now as they are likely comparing current metrics with a period of very low or initial activity. This is common when organizations start actively using a social media platform or significantly change their social media strategy.
Let me generate the final response:
High percentage increases are expected due to initial low baseline metrics
The reported percentage increases, while appearing unusually high, are likely accurate as they represent growth from a period of minimal activity. This is a common pattern when:
- Starting fresh on a platform
- Reactivating a dormant account
- Implementing a new social media strategy
For better context in future reports, consider:
- Including absolute numbers for both periods
- Specifying the exact baseline period
- Using month-over-month growth rates once baseline stabilizes
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Search for any previous reports or metrics in the repository
rg -i "twitter|x.*metrics|social.*media.*report" --type md
Length of output: 39433
|
Hey all, I have updated the PR. Can it get a final review? |
|
|
||
| The Marketing Working Group (MWG) is the driving force behind the AsyncAPI Initiative’s external engagement, community growth, and brand awareness efforts. Our mission is to encourage an active, informed, and passionate community by promoting the tools, resources, and stories that make AsyncAPI unique. | ||
|
|
||
| We aim to: |
There was a problem hiding this comment.
I am assuming the points mentioned are key ones and the list is definitely non-exhaustive, hence suggesting this change
| We aim to: | |
| Some of the things we aim to accomplish: |
| - **Highlight Impact:** Share stories, case studies, and successes from the community to inspire and inform potential contributors, users, and partners. | ||
|
|
||
| - **Drive Growth:** Attract new users, contributors, and partners through partnerships, events, and online activities that underscore AsyncAPI’s value in the tech landscape. | ||
| By aligning our goals with AsyncAPI’s mission, the Marketing WG seeks to empower both seasoned and new members to engage deeply with the initiative. |
There was a problem hiding this comment.
| By aligning our goals with AsyncAPI’s mission, the Marketing WG seeks to empower both seasoned and new members to engage deeply with the initiative. | |
| By aligning our goals with AsyncAPI’s mission, the MWG seeks to empower both seasoned and new members to engage deeply with the initiative. |
| Below is a summary of what we’ve accomplished this year and our priorities moving forward. | ||
|
|
||
| ## Accomplishments and Milestones | ||
| We’ve focused on laying the groundwork for long-term growth and engagement for the last six months. Our marketing initiatives have been designed to elevate AsyncAPI’s visibility, simplify our communication strategy, and ensure we’re prepared to grow alongside our community. Here’s a summary of what we’ve done so far: |
There was a problem hiding this comment.
| We’ve focused on laying the groundwork for long-term growth and engagement for the last six months. Our marketing initiatives have been designed to elevate AsyncAPI’s visibility, simplify our communication strategy, and ensure we’re prepared to grow alongside our community. Here’s a summary of what we’ve done so far: | |
| We’ve focused on laying the groundwork for long-term growth and engagement for the last six months. Our marketing initiatives have been designed to elevate AsyncAPI’s visibility, simplify our communication strategy, and ensure we’re prepared to grow alongside our community. | |
| Here’s a summary of what we’ve done so far: |
|
|
||
| ## Accomplishments and Milestones | ||
| We’ve focused on laying the groundwork for long-term growth and engagement for the last six months. Our marketing initiatives have been designed to elevate AsyncAPI’s visibility, simplify our communication strategy, and ensure we’re prepared to grow alongside our community. Here’s a summary of what we’ve done so far: | ||
|
|
| To improve the efficiency and security of our social media management, we’ve introduced a paid version of Buffer for posting content across our platforms. This change enables us to streamline content scheduling, ensuring consistent, professional updates without compromising security. Importantly, using Buffer restricts access to the main social media accounts, adding a layer of protection and allowing us to manage permissions efficiently. | ||
|
|
||
| Here are some of the benefits of using the Buffer subscription | ||
|
|
There was a problem hiding this comment.
Minor changes left but your Alt text is not showing https://deploy-preview-3439--asyncapi-website.netlify.app/blog/2024-marketing-report
| The X (Twitter) performance overview indicates our incredible performance growth: | ||
|
|
||
| - **Tweets:** Shared an impressive 254 tweets, marking a staggering 25,300% increase. | ||
| - **Replies:** Engaged in 10 replies, growing by 1,000%, highlighting our community members are beginning to take interest in our X posts. |
There was a problem hiding this comment.
| - **Replies:** Engaged in 10 replies, growing by 1,000%, highlighting our community members are beginning to take interest in our X posts. | |
| - **Replies:** Engaged in 10 replies, growing by 1,000%, highlighting our community members are beginning to take an interest in our X posts. |
|  | ||
|
|
||
|
|
||
| The images above show the LinkedIn performance is great. Here’s a breakdown of our LinkedIn metrics from Buffer’s analysis: |
There was a problem hiding this comment.
| The images above show the LinkedIn performance is great. Here’s a breakdown of our LinkedIn metrics from Buffer’s analysis: | |
| The images above show that LinkedIn's performance is great. Here’s a breakdown of our LinkedIn metrics from Buffer’s analysis: |
|
|
||
| ## Sponsor Involvement in the Marketing Working Group | ||
|
|
||
| The Marketing Working Group thrives on collaboration, and we’re fortunate to have active participation from representatives of our sponsors, including Christophe Dujarric from Bump.sh and Georgie Burrows from Gravitee.io. Their insights, ideas, and expertise are invaluable in shaping the group’s direction and ensuring that AsyncAPI’s marketing strategies align with the broader goals of our sponsors and the community. |
There was a problem hiding this comment.
Add links to their profiles, and company page
|
|
||
| The working group is designed to be inclusive, welcoming not just sponsor representatives but also any community members who wish to contribute. Whether it’s sharing ideas, providing feedback, or helping execute campaigns. | ||
|
|
||
| This collaborative approach ensures that we have diverse perspectives guiding our efforts and allows the Marketing Working Group to act as a bridge between AsyncAPI’s community and its stakeholders. If you have ideas or want to contribute, we’d love to hear from you! |
There was a problem hiding this comment.
| This collaborative approach ensures that we have diverse perspectives guiding our efforts and allows the Marketing Working Group to act as a bridge between AsyncAPI’s community and its stakeholders. If you have ideas or want to contribute, we’d love to hear from you! | |
| This collaborative approach ensures that diverse perspectives guide our efforts and allows the Marketing Working Group to act as a bridge between AsyncAPI’s community and its stakeholders. We'd love to hear from you if you have ideas or want to contribute! |
|
|
||
| ## Who can Join the Marketing Working Group? | ||
|
|
||
| The working group is designed to be inclusive, welcoming not just sponsor representatives but also any community members who wish to contribute. Whether it’s sharing ideas, providing feedback, or helping execute campaigns. |
There was a problem hiding this comment.
| The working group is designed to be inclusive, welcoming not just sponsor representatives but also any community members who wish to contribute. Whether it’s sharing ideas, providing feedback, or helping execute campaigns. | |
| The working group is designed to be inclusive and welcoming, not just sponsor representatives but also any community members who wish to contribute. Whether it’s sharing ideas, providing feedback, or helping execute campaigns. |
Description
Hey folks,
It's been six months since we launched the marketing working group. Here is a report stating what we have been doing, are currently doing, and our future focus.
Kindly read it and provide your feedback. Should there be any questions or suggestions? Please feel free to contact me on Slack.
@thulieblack
Summary by CodeRabbit
New Features
Documentation