chore(blog): add 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!
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 86.59% 86.59%
=======================================
Files 21 21
Lines 664 664
=======================================
Hits 575 575
Misses 89 89 ☔ 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? |
derberg
changed the title
Co-authored-by: Lukasz Gornicki <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
markdown/blog/2024-marketing-report.md (1)
89-89: Minor grammar improvementsConsider adding a comma for better readability.
-We do not have data that we could share and show how our performance improved as we do not have such. +We do not have data that we could share and show how our performance improved, as we do not have such.🧰 Tools
🪛 LanguageTool
[uncategorized] ~89-~89: Possible missing comma found.
Context: ...ould share and show how our performance improved as we do not have such. ## Closing ...(AI_HYDRA_LEO_MISSING_COMMA)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 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] ~59-~59: 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)
[uncategorized] ~89-~89: Possible missing comma found.
Context: ...ould share and show how our performance improved as we do not have such. ## Closing ...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~98-~98: Consider removing “of” to be more concise
Context: ...ore were 2383. The goal was to disburse all of the items by December 2024. <Figure src...
(ALL_OF_THE)
🔇 Additional comments (5)
markdown/blog/2024-marketing-report.md (5)
1-15: LGTM! Metadata is well-structured and complete.
The frontmatter contains all necessary information including title, date, type, tags, cover image, and author details.
1-179: Overall, the report is well-structured and informative
The document effectively communicates the Marketing Working Group's activities, achievements, and future plans. The content is organized logically and provides valuable insights into the group's work.
🧰 Tools
🪛 LanguageTool
[grammar] ~59-~59: 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)
[uncategorized] ~89-~89: Possible missing comma found.
Context: ...ould share and show how our performance improved as we do not have such. ## Closing ...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~98-~98: Consider removing “of” to be more concise
Context: ...ore were 2383. The goal was to disburse all of the items by December 2024. <Figure src...
(ALL_OF_THE)
142-142:
Update Student Ambassador Program status
The program is still in the proposal stage and not yet launched. Please update the text to reflect its current status.
-Additionally, we are planning 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 have proposed a [Student Ambassador Program](https://github.com/asyncapi/community/pull/1333) initiative, which would aim to nurture future AsyncAPI advocates and contributors at the student level.Likely invalid or redundant comment.
122-122:
Fix broken distribution board link
The Google Sheets link is malformed and inaccessible. Consider:
- Updating with the correct URL
- Using only the Open Collective link for transparency if the sheet contains sensitive information
-[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)
+[For detailed distribution information, 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.
68-73: 🛠️ Refactor suggestion
Enhance image accessibility for LinkedIn metrics figure
The alt text should be more descriptive and include the time period.
- alt="Graph showing AsyncAPI LinkedIn follower growth"
+ alt="Graph showing AsyncAPI LinkedIn follower growth from January to December 2024, demonstrating consistent increase in followers"Likely invalid or redundant comment.
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (1)
markdown/blog/2024-marketing-report.md (1)
89-89: Fix grammar and improve clarityThere are a few grammatical issues that could be improved:
-Tracking our performance on X (formally Twitter) has not been easy. Buffer does not have access to historical data. We can see numbers that show our performance since we connected Buffer in September. We do not have data that we could share and show how our performance improved as we do not have such. +Tracking our performance on X (formerly Twitter) has not been easy. Buffer does not have access to historical data. We can only see performance numbers since connecting Buffer in September, making it difficult to demonstrate historical improvements. -The working group is designed to be inclusive and welcoming, not just sponsor representatives but also any community members who wish to contribute. +The working group is designed to be inclusive and welcoming to both sponsor representatives and any community members who wish to contribute.Also applies to: 165-165
🧰 Tools
🪛 LanguageTool
[uncategorized] ~89-~89: Possible missing comma found.
Context: ...ould share and show how our performance improved as we do not have such. ## Closing ...(AI_HYDRA_LEO_MISSING_COMMA)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 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] ~59-~59: 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)
[uncategorized] ~89-~89: Possible missing comma found.
Context: ...ould share and show how our performance improved as we do not have such. ## Closing ...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~98-~98: Consider removing “of” to be more concise
Context: ...ore were 2383. The goal was to disburse all of the items by December 2024. <Figure src...
(ALL_OF_THE)
[uncategorized] ~165-~165: Possible missing comma found.
Context: ...coming, not just sponsor representatives but also any community members who wish to ...
(AI_HYDRA_LEO_MISSING_COMMA)
🔇 Additional comments (3)
markdown/blog/2024-marketing-report.md (3)
87-87: Verify consistency of reported metrics
Please verify the accuracy and consistency of the reported metrics:
- LinkedIn impressions are reported as 100,328
- Social media campaign impressions are reported as 5,031
Also applies to: 41-41
✅ Verification successful
Based on the search results, I can verify the consistency of the metrics. Let me analyze the progression of LinkedIn metrics across different reports:
- 2023 Summary (markdown/blog/2023-summary.md:58): 2,988 followers by end of 2023
- 2024 Marketing Report: 3,910 total followers, representing a 48% increase
For impressions:
- The marketing report mentions 100,328 impressions (104% increase)
- It also separately mentions 5,031 impressions specifically for targeted social media campaigns
These numbers are consistent because:
- The follower growth from 2,988 to 3,910 indeed represents approximately a 48% increase
- The 5,031 impressions mentioned in line 41 specifically refers to targeted campaigns, while the 100,328 impressions represents the total LinkedIn impressions for the period
- The progression of followers from previous years (2022: ~2,139, 2023: 2,988, 2024: 3,910) shows a consistent growth pattern
Metrics are accurately reported and consistent with historical data
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Search for any other metrics in markdown files for cross-reference
rg -n "impressions|followers|engagement" --type md
Length of output: 13733
2-3: Verify the publication date
The post is dated December 19, 2024, which is in the future. While this might be intentional for scheduling purposes, please confirm if this is the desired publication date.
✅ Verification successful
Future date is intentional and consistent with other December posts
The December 19, 2024 publication date appears to be intentional and aligns with other December 2024 posts in the blog. There are multiple posts scheduled for December 2024:
2024-december-and-paris.md(December 16, 2024)2024-gsoc-wrap.md(December 18, 2024)2024-marketing-report.md(December 19, 2024)
The repository consistently contains blog posts with future dates throughout 2024, indicating this is part of the normal content scheduling workflow.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check if there are other blog posts with future dates
rg -l "date: 2024-" --type md
Length of output: 891
Script:
#!/bin/bash
# Let's check the actual dates in these 2024 files to understand the pattern
rg "date: 2024-" --type md -A 1
Length of output: 2939
122-122:
Fix broken distribution board link
The Google Sheets link is malformed and inaccessible. Consider either:
- Updating with the correct URL
- Removing it if the information is sensitive
- Using only the Open Collective link for transparency
-[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)
+[For detailed distribution information, 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.
|
|
||
| ## Conclusion | ||
|
|
||
| This report highlights the strides made by the AsyncAPI Marketing Working Group, including targeted campaigns, streamlined social media management with Buffer, impactful merchandise distribution, the introduction of a comprehensive strategy document, and the launch of the Student Ambassador Program. We've also made strategic decisions, such as closing the online store, to optimize our budget for initiatives that deliver greater value to the community. |
There was a problem hiding this comment.
Align Student Ambassador Program status messaging
There are inconsistencies in how the Student Ambassador Program's status is presented. In some places it's mentioned as launched, while in others it's still in the proposal stage.
-This report highlights the strides made by the AsyncAPI Marketing Working Group, including... and the launch of the Student Ambassador Program.
+This report highlights the strides made by the AsyncAPI Marketing Working Group, including... and the proposal of the Student Ambassador Program.
-**Launching the Student Ambassador Program:** Engaging students worldwide to represent and support AsyncAPI
+**Developing the Student Ambassador Program:** Planning to engage students worldwide to represent and support AsyncAPIAlso applies to: 151-151
|
@iambami please address the reviews from coderabbit |
|
@derberg last review? |
|
@iambami just please look at coderabbit suggestion, it's a smart beast with good ideas 😄 |
|
I have implemented the changes except for line 151; we are stating the future focus: "launching the Student Ambassador Program." The statement is correct. |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
markdown/blog/2024-marketing-report.md (2)
89-89: Fix grammar and improve readabilityA few minor grammatical improvements would enhance readability:
-Tracking our performance on X (formally Twitter) has not been easy. Buffer does not have access to historical data. We can see numbers that show our performance since we connected Buffer in September. We do not have data that we could share and show how our performance improved as we do not have such. +Tracking our performance on X (formally Twitter) has not been easy. Buffer does not have access to historical data. We can see numbers that show our performance since we connected Buffer in September, but we do not have historical data to demonstrate performance improvements. -The working group is designed to be inclusive and welcoming, not just sponsor representatives but also any community members who wish to contribute. +The working group is designed to be inclusive and welcoming, not just for sponsor representatives, but also for any community members who wish to contribute.Also applies to: 166-166
🧰 Tools
🪛 LanguageTool
[uncategorized] ~89-~89: Possible missing comma found.
Context: ...ould share and show how our performance improved as we do not have such. ## Closing ...(AI_HYDRA_LEO_MISSING_COMMA)
69-71: Enhance image accessibility descriptionsThe alt text and captions could be more descriptive to better serve users with screen readers:
- alt="Line graph showing AsyncAPI LinkedIn follower growth trends throughout 2024" - caption="AsyncAPI LinkedIn follower growth trends from January to December 2024" + alt="Line graph showing AsyncAPI LinkedIn follower growth increasing from 2,000 to 3,910 followers throughout 2024" + caption="AsyncAPI LinkedIn follower growth trends showing 48% increase from January to December 2024" - alt="Image showing AsyncAPI LinkedIn performance including follower growth, engagement rates, and post performance over time" - caption="AsyncAPI LinkedIn performance statistics from Buffer analytics." + alt="Dashboard showing AsyncAPI LinkedIn metrics: 3,910 total followers, 100,328 impressions, 4,295 clicks, and 5.32% engagement rate" + caption="AsyncAPI LinkedIn performance dashboard showing key metrics from Buffer analytics for 2024"Also applies to: 78-80
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 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] ~59-~59: 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)
[uncategorized] ~89-~89: Possible missing comma found.
Context: ...ould share and show how our performance improved as we do not have such. ## Closing ...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~98-~98: Consider removing “of” to be more concise
Context: ...ore were 2383. The goal was to disburse all of the items by December 2024. <Figure src...
(ALL_OF_THE)
[uncategorized] ~166-~166: Possible missing comma found.
Context: ...coming, not just sponsor representatives but also any community members who wish to ...
(AI_HYDRA_LEO_MISSING_COMMA)
🔇 Additional comments (3)
markdown/blog/2024-marketing-report.md (3)
152-152:
Align Student Ambassador Program status messaging
The program's status is inconsistently presented throughout the document. Based on the PR discussion, it's still in the proposal phase.
-**Launching the Student Ambassador Program:** Engaging students worldwide to represent and support AsyncAPI within their schools and networks
+**Developing the Student Ambassador Program:** Planning to engage students worldwide to represent and support AsyncAPI within their schools and networksLikely invalid or redundant comment.
123-123:
Fix or remove the broken distribution board link
The Google Sheets link appears to be malformed. Consider:
- Using the correct URL format without duplicate
/edit/segments - Ensuring the sheet has proper access permissions
- Relying on the Open Collective link as the primary source for transparency
-[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)
+[For detailed distribution information, 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.
87-89: Verify LinkedIn performance metrics
The reported metrics show significant percentage increases (48% followers, 104% impressions, etc.). Since these are substantial changes, it would be helpful to:
- Include the baseline numbers from the previous period for context
- Explain the time period for these comparisons
✅ Verification successful
LinkedIn metrics verified with baseline data
The reported metrics in the 2024 marketing report are accurate and consistent with previous data:
- The 48% follower increase from 2,988 (end of 2023) to 3,910 (2024) is correctly calculated
- The time period for comparison is clearly year-over-year (2023 vs 2024)
- Other metrics (impressions, engagement, clicks) represent new measurements for 2024, with their percentage increases calculated against their respective 2023 baselines
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Search for any previous reports or documentation of LinkedIn metrics
# to validate the baseline numbers and growth percentages
# Look for previous marketing reports or analytics
rg -i "linkedin.*performance|linkedin.*metrics|linkedin.*analytics" --type md
Length of output: 1326
Script:
#!/bin/bash
# Let's search for any previous marketing reports or analytics data from 2023
# that might contain baseline numbers for comparison
# Search for 2023 marketing reports
fd "2023.*marketing.*report" --type f
# Also search for specific LinkedIn numbers in any markdown files from 2023
rg -i "linkedin.*followers|linkedin.*impressions|linkedin.*engagement" --type md | grep -i "2023"
Length of output: 310
🧰 Tools
🪛 LanguageTool
[uncategorized] ~89-~89: Possible missing comma found.
Context: ...ould share and show how our performance improved as we do not have such. ## Closing ...
(AI_HYDRA_LEO_MISSING_COMMA)
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
markdown/blog/2024-marketing-report.md (2)
40-48: Consider adding metrics for the social media campaignsFor the targeted social media campaigns, consider adding specific metrics to demonstrate their impact:
- Engagement rates for #AsyncAPIParis2024
- Reach and interaction stats for #YourAsyncAPIStory
67-72: Enhance the LinkedIn metrics visualizationWhile the alt text and caption are descriptive, consider adding:
- The exact starting follower count for better context
- Key milestone points in the growth trend
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 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] ~58-~58: 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] ~97-~97: Consider removing “of” to be more concise
Context: ...ore were 2383. The goal was to disburse all of the items by December 2024. <Figure src...
(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 with appropriate values. The excerpt provides a clear summary, and the author information is complete with photo and social links.
151-151:
Update Student Ambassador Program status in future focus areas
Align the program's status with its current state of development.
-- **Launching the Student Ambassador Program:** Engaging students worldwide to represent and support AsyncAPI within their schools and networks
+- **Developing the Student Ambassador Program:** Planning to engage students worldwide to represent and support AsyncAPI within their schools and networksLikely invalid or redundant comment.
122-122:
Fix the malformed Google Sheets link
The distribution board link appears to be broken due to 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)Likely invalid or redundant comment.
140-142:
Maintain consistency in describing the Student Ambassador Program status
The program's status varies between "proposed," "planning to introduce," and "launching" throughout the document. Maintain consistent messaging about its current status.
-Additionally, we are planning 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 have proposed the [Student Ambassador Program](https://github.com/asyncapi/community/pull/1333), which aims to nurture future AsyncAPI advocates and contributors at the student level. The program is currently under discussion and development.Likely invalid or redundant comment.
|
@akshatnema @TRohit20 @derberg, can you approve the PR? We want to add it to the newsletter going out tomorrow morning. Thank you. |
|
/rtm |
|
Hello, @akshatnema! 👋🏼 |
|
/rtm |
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