Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(blog): add marketing report #3439

Open
wants to merge 59 commits into
base: master
Choose a base branch
from

Conversation

iambami
Copy link
Contributor

@iambami iambami commented Dec 1, 2024

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

    • Introduced the "2024 Marketing Report," detailing the AsyncAPI Marketing Working Group's initiatives and achievements.
    • Launched the Student Ambassador Program to enhance community ties.
    • Implemented Buffer for improved social media management and analytics.
    • Provided a breakdown of merchandise distribution and financial expenditures related to the online store.
    • Added metadata for the new report, including authorship and cover image.
  • Documentation

    • Added comprehensive insights on community engagement strategies and future focus areas.
    • Included a summary of key accomplishments and future initiatives.

Copy link

coderabbitai bot commented Dec 1, 2024

Walkthrough

A new file, 2024-marketing-report.md, has been created to provide an overview of the AsyncAPI Marketing Working Group's activities over the past year. The report includes an introduction, objectives, key accomplishments, and future focus areas. It discusses the closure of the online store and the reallocation of resources, introduces a Marketing Strategy Document, and emphasizes community engagement and collaboration.

Changes

File Change Summary
markdown/blog/2024-marketing-report.md New file created detailing the AsyncAPI Marketing Working Group's activities, goals, accomplishments, and future plans. Includes metadata such as title, date, type, tags, cover image, authors, and excerpt.

Possibly related PRs

  • chore(blog): google summer of code 2024 summary #3459: The PR summarizes AsyncAPI's participation in the 2024 Google Summer of Code, which, like the main PR, documents community engagement and achievements, highlighting the importance of collaboration and outreach efforts.

Suggested labels

ready-to-merge

Suggested reviewers

  • thulieblack
  • quetzalliwrites
  • derberg

🐰 In the garden where ideas bloom,
A report emerges, dispelling gloom.
With goals and plans, the team takes flight,
Building engagement, shining bright.
From campaigns launched to stories told,
Together we grow, our future bold! 🌼


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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

netlify bot commented Dec 1, 2024

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 0515ce1
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/67652d277516e40008c49b1a
😎 Deploy Preview https://deploy-preview-3439--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

codecov bot commented Dec 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.59%. Comparing base (4e877a5) to head (0515ce1).

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.
📢 Have feedback on the report? Share it here.

@asyncapi-bot
Copy link
Contributor

asyncapi-bot commented Dec 1, 2024

⚡️ Lighthouse report for the changes in this PR:

Category Score
🔴 Performance 41
🟢 Accessibility 98
🟢 Best practices 92
🟢 SEO 100
🔴 PWA 33

Lighthouse ran on https://deploy-preview-3439--asyncapi-website.netlify.app/

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 error

There'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 formatting

The "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 file

Multiple 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

📥 Commits

Reviewing files that changed from the base of the PR and between edc6eca and 54fef3c.

📒 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. ![Merchandise ...

(ALL_OF_THE)

🔇 Additional comments (1)
markdown/blog/2024-marketing-report.md (1)

95-95: Use permanent documentation links instead of PR links

Links to Pull Requests may become less relevant once merged. Consider updating these to point to the final documentation locations.

Once the PRs are merged, update the links to point to the final documentation:

-[Strategy Document](https://github.com/asyncapi/community/pull/1358)
+[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

markdown/blog/2024-marketing-report.md Outdated Show resolved Hide resolved
markdown/blog/2024-marketing-report.md Outdated Show resolved Hide resolved
markdown/blog/2024-marketing-report.md Outdated Show resolved Hide resolved
@iambami
Copy link
Contributor Author

iambami commented Dec 4, 2024

Hello @thulieblack @quetzalliwrites

Still waiting for your review.

Copy link
Collaborator

@TRohit20 TRohit20 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested minor changes, the rest looks good to me. @quetzalliwrites please give the final review :)

markdown/blog/2024-marketing-report.md Outdated Show resolved Hide resolved
markdown/blog/2024-marketing-report.md Outdated Show resolved Hide resolved
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (1)
markdown/blog/2024-marketing-report.md (1)

84-84: Fix bullet point formatting

The "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

📥 Commits

Reviewing files that changed from the base of the PR and between 54fef3c and 7c4bbc5.

📒 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. ![Merchandise ...

(ALL_OF_THE)

🔇 Additional comments (4)
markdown/blog/2024-marketing-report.md (4)

59-59: Fix incorrect date range in analytics section

The analytics date range extends into the future (May to November 2024), which isn't possible for actual data.


62-62: Add descriptive alt text to images for accessibility

The images lack meaningful alt text, which is important for accessibility.

Also applies to: 64-64, 73-73, 90-90, 121-121


88-88: Fix malformed distribution board link

The link to the distribution board appears to be malformed and might not be publicly accessible.


2-3: ⚠️ Potential issue

Update the publication date

The blog post's date is set to December 2024, which is in the future. Please update it to reflect the current or intended publication date.

-date: 2024-12-09T06:00:00+01:00
+date: 2023-12-09T06:00:00+01:00

Likely invalid or redundant comment.

markdown/blog/2024-marketing-report.md Show resolved Hide resolved
@akshatnema
Copy link
Member

@thulieblack @derberg Can someone please review and approve this PR, as I don't have any context around this?

@iambami
Copy link
Contributor Author

iambami commented Dec 9, 2024

@thulieblack ?

@iambami
Copy link
Contributor Author

iambami commented Dec 9, 2024

Can I have the final review on this?

@iambami
Copy link
Contributor Author

iambami commented Dec 17, 2024

@iambami

I think you missed that comment: #3439 (comment) I don't think this data is reliable. X in general is not reliable. If you look closely, the data before 2nd September is falsey, one number, no matter what time period you choose. I assume this date is when our X was connected to Buffer, and Buffer has data only since it got connected to X - no historical data

please look also at nitpicks: #3439 (review)

@derberg I replied... and changed the content.

The question is should the X images be removed?

@derberg
Copy link
Member

derberg commented Dec 17, 2024

I think so, yes

Our performance on X (Twitter) has been extraordinary, with significant growth in tweets, replies, retweets, clicks, impressions, likes, and overall engagements. These results highlight increased visibility, audience interactions, and a stronger community connection.

this statement also needs to change - we simly do not know. We need to make it transparent, where we are, that we honestly do not know if there is a better performance, but we do know we at least can not track performance

some interesting info about X. When you check only for chart data from September till now, you see a drop on performance around time when people started talking more about Blue Sky

@iambami
Copy link
Contributor Author

iambami commented Dec 17, 2024

I think so, yes

Our performance on X (Twitter) has been extraordinary, with significant growth in tweets, replies, retweets, clicks, impressions, likes, and overall engagements. These results highlight increased visibility, audience interactions, and a stronger community connection.

this statement also needs to change - we simly do not know. We need to make it transparent, where we are, that we honestly do not know if there is a better performance, but we do know we at least can not track performance

some interesting info about X. When you check only for chart data from September till now, you see a drop on performance around time when people started talking more about Blue Sky

Okay, I get it.

@iambami
Copy link
Contributor Author

iambami commented Dec 17, 2024

I have fixed that @derberg

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 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 a more concise version that captures the key points.

-excerpt: 'A comprehensive review of AsyncAPI Marketing Working Group achievements in 2024, including social media growth, store closure updates, and future initiatives like the Student Ambassador Program'
+excerpt: 'Key achievements and future initiatives of the AsyncAPI Marketing Working Group in 2024'

41-41: Add context to the impression metrics

The raw number of impressions (5,031) would be more meaningful with a comparison to previous periods or industry benchmarks.

-Launched targeted social media campaigns that reached 5,031 impressions, supported by our community of designers:
+Launched targeted social media campaigns that reached 5,031 impressions (a X% increase from previous quarter), supported by our community of designers:

68-73: Enhance figure accessibility with more descriptive alt text

The current alt text could be more descriptive to better serve users with screen readers.

-  alt="Graph showing AsyncAPI LinkedIn follower growth"
+  alt="Line graph showing AsyncAPI LinkedIn follower growth trend from January to December 2024, with significant upward trajectory"

175-175: Make the Slack contact information more accessible

Consider adding alternative contact methods for those not yet in the Slack workspace.

-If you have any questions, suggestions, or ideas, please feel free to reach out to me on Slack [Atinuke (Bami) Kayode](https://asyncapi.slack.com/archives/D070U11CU1G).
+If you have any questions, suggestions, or ideas, please feel free to reach out to me on [Slack](https://asyncapi.slack.com/archives/D070U11CU1G) or connect with me on [LinkedIn](https://www.linkedin.com/in/atinuke-oluwabamikemi-kayode-5b838b1b7/).
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2fcb098 and 4f797d9.

📒 Files selected for processing (1)
  • markdown/blog/2024-marketing-report.md (1 hunks)
🧰 Additional context used
🪛 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)


[style] ~96-~96: 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] ~163-~163: 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 (2)
markdown/blog/2024-marketing-report.md (2)

120-120: ⚠️ Potential issue

Fix or remove the broken distribution board link

The Google Sheets link appears to be malformed. Consider either:

  1. Updating with the correct URL, or
  2. Removing it since the Open Collective link provides transparency
-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 transparency, all expenses are tracked on 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.


140-140: 🛠️ Refactor suggestion

Clarify the Student Ambassador Program's status

The text should be more explicit about the program being in the proposal stage.

-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) (currently under discussion), which would aim to nurture future AsyncAPI advocates and contributors at the student level.

Likely invalid or redundant comment.

@derberg derberg changed the title docs: bami added marketing report chore(blog): add marketing report Dec 18, 2024
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
markdown/blog/2024-marketing-report.md (1)

89-89: Minor grammar improvements

Consider 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

📥 Commits

Reviewing files that changed from the base of the PR and between 4f797d9 and c1a3d12.

📒 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: ⚠️ Potential issue

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: ⚠️ Potential issue

Fix broken distribution board link

The Google Sheets link is malformed and inaccessible. Consider:

  1. Updating with the correct URL
  2. 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (1)
markdown/blog/2024-marketing-report.md (1)

89-89: Fix grammar and improve clarity

There 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

📥 Commits

Reviewing files that changed from the base of the PR and between 4f797d9 and 8186889.

📒 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:

  1. The follower growth from 2,988 to 3,910 indeed represents approximately a 48% increase
  2. 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
  3. 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: ⚠️ Potential issue

Fix broken distribution board link

The Google Sheets link is malformed and inaccessible. Consider either:

  1. Updating with the correct URL
  2. Removing it if the information is sensitive
  3. 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.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

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 AsyncAPI

Also applies to: 151-151

markdown/blog/2024-marketing-report.md Outdated Show resolved Hide resolved
markdown/blog/2024-marketing-report.md Outdated Show resolved Hide resolved
@thulieblack
Copy link
Member

@iambami please address the reviews from coderabbit

@thulieblack
Copy link
Member

@derberg last review?

@derberg
Copy link
Member

derberg commented Dec 18, 2024

@iambami
all good for me, great work 👏🏼
now you can tract socials performance on regular monthly basis and we can start cleanup of automated posting and see if it affected performance or not

just please look at coderabbit suggestion, it's a smart beast with good ideas 😄

@iambami
Copy link
Contributor Author

iambami commented Dec 19, 2024

I have implemented the changes except for line 151; we are stating the future focus: "launching the Student Ambassador Program." The statement is correct.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
markdown/blog/2024-marketing-report.md (2)

89-89: Fix grammar and improve readability

A 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 descriptions

The 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

📥 Commits

Reviewing files that changed from the base of the PR and between 8186889 and 3ace5fe.

📒 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: ⚠️ Potential issue

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 networks

Likely invalid or redundant comment.


123-123: ⚠️ Potential issue

Fix or remove the broken distribution board link

The Google Sheets link appears to be malformed. Consider:

  1. Using the correct URL format without duplicate /edit/ segments
  2. Ensuring the sheet has proper access permissions
  3. 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:

  1. Include the baseline numbers from the previous period for context
  2. 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)

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
markdown/blog/2024-marketing-report.md (2)

40-48: Consider adding metrics for the social media campaigns

For 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 visualization

While the alt text and caption are descriptive, consider adding:

  1. The exact starting follower count for better context
  2. Key milestone points in the growth trend
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3ace5fe and e98ed87.

📒 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: ⚠️ Potential issue

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 networks

Likely invalid or redundant comment.


122-122: ⚠️ Potential issue

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: ⚠️ Potential issue

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.

markdown/blog/2024-marketing-report.md Show resolved Hide resolved
Copy link
Member

@thulieblack thulieblack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👌🏿

@iambami
Copy link
Contributor Author

iambami commented Dec 19, 2024

@akshatnema @TRohit20 @derberg, can you approve the PR?

We want to add it to the newsletter going out tomorrow morning.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants