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

docs: marketing report #3436

Closed
wants to merge 14 commits into from
Closed

Conversation

iambami
Copy link
Contributor

@iambami iambami commented Nov 29, 2024

Description

Hey folks 👋

Bami here. After an interesting six months as the chair of the Marketing WG. Here is a report of what we are doing and plan to do.

@thulieblack

Summary by CodeRabbit

Release Notes

  • New Features

    • Introduced the "AsyncAPI Student Ambassador Program" to engage students in promoting AsyncAPI.
    • Added a comprehensive "2024 Marketing Report" detailing the Marketing Working Group's activities and accomplishments.
    • Announced Gravitee as a Platinum Sponsor of the AsyncAPI Initiative.
  • Bug Fixes

    • Removed outdated components including Card, Header, HomeCards, and various ambassador-related pages to streamline the community section.
  • Documentation

    • Updated documentation to reflect the new ambassador program and sponsorship announcement.

These updates enhance community engagement and provide clearer pathways for participation in the AsyncAPI ecosystem.

Copy link

coderabbitai bot commented Nov 29, 2024

Walkthrough

This pull request includes the removal of several React components related to the AsyncAPI community, specifically the Card, Header, HomeCard, and ambassador-related components. Additionally, it introduces two new markdown files: a comprehensive marketing report for the AsyncAPI Initiative and an announcement regarding Gravitee's sponsorship. The changes indicate a significant restructuring of the community's UI components and documentation.

Changes

File Path Change Summary
components/community/Card.tsx Component removed: Card
components/community/Header.tsx Component removed: Header
components/community/HomeCard.tsx Components removed: HomeCards, interface HomeCardProps
pages/community/ambassadors/[id].tsx Methods and component removed: getStaticProps, getStaticPaths, and Index
pages/community/ambassadors/index.tsx Function and default export removed: addAdditionalUserInfo, Index
pages/community/events/index.tsx Component removed: EventIndex
pages/community/index.tsx Component and interface removed: CommunityIndexPage, Event
markdown/blog/2024-marketing-report.md New file created: detailed marketing report for AsyncAPI Initiative
markdown/blog/gravitee-annoucement.md New file created: announcement for Gravitee's sponsorship of AsyncAPI
markdown/docs/community/_section.md Section metadata removed: title: 'Community', weight: 7

Possibly related PRs

  • fix: remove hydration errors #3262: The changes in this PR involve the removal of the Card component, which is relevant as it directly relates to the UI components in the same context as the Header and HomeCard components that were also deleted in the main PR.
  • docs: replace duplicated content with reusable fragments #3269: This PR focuses on enhancing documentation by replacing duplicated content with reusable fragments, which could relate to the overall structure and maintainability of components like Card that were removed in the main PR, as it indicates a shift towards more modular and reusable code practices.

Suggested labels

ready-to-merge

Suggested reviewers

  • thulieblack
  • akshatnema
  • magicmatatjahu
  • devilkiller-ag
  • sambhavgupta0705
  • BhaswatiRoy
  • J0SAL
  • Mayaleeeee
  • anshgoyalevil
  • asyncapi-bot-eve
  • quetzalliwrites
  • TRohit20
  • derberg

🐇 In the garden where ideas bloom,
We waved goodbye to the Card and Home,
A marketing tale now takes the stage,
With Gravitee's support, we turn the page.
New paths for ambassadors to roam,
In the AsyncAPI community, we find our home! 🌼


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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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 Nov 29, 2024

Deploy Preview for asyncapi-website failed.

Built without sensitive environment variables

Name Link
🔨 Latest commit 7e4266b
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/6749f272bd4b220008df6ac4

@iambami iambami changed the title Marketing report docs: marketing report Nov 29, 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: 2

🧹 Outside diff range and nitpick comments (4)
markdown/blog/gravitee-annoucement.md (1)

28-32: Fix list indentation for consistency

The unordered list items are indented with 2 spaces. For better markdown compatibility, remove the indentation.

-  - **Enhance Community Support:** With Gravitee's backing...
-  - **Expand Educational Initiatives:** We will be able...
-  - **Foster Innovation:** This partnership will drive...
+- **Enhance Community Support:** With Gravitee's backing...
+- **Expand Educational Initiatives:** We will be able...
+- **Foster Innovation:** This partnership will drive...
🧰 Tools
🪛 Markdownlint (0.35.0)

28-28: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


30-30: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


32-32: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

pages/blog/asyncapi-student-ambassador-program (3)

17-34: Improve document structure and readability

The introduction would benefit from:

  1. Adding a clear heading (e.g., "## Introduction" or "## About the Program")
  2. A smoother transition between the first two paragraphs
  3. More structured formatting for better readability
+## Introduction
+
 The AsyncAPI community is the driving force behind the initiative. The individuals who dedicated their time to promoting AsyncAPI through talks, articles, workshops, and program direction.
+
 Seeing the significant impact of our existing ambassador program, we are excited to extend this initiative to the student community. By introducing the AsyncAPI Student Ambassador Program, we aim to give back to the community and empower students to contribute to and benefit from the AsyncAPI ecosystem.

39-41: Improve image accessibility

The alt text "heart&brain" is not descriptive enough for screen readers. Consider providing a more detailed description of the image content and its relevance to the context.

-  <img src="https://media.giphy.com/media/v1.Y2lkPTc5MGI3NjExOTgzODZhZDM1MWZhMDJiODNkODFhZTI3MWRjZDExZGQyYzBlNzMwYiZjdD1z/NfBApd81ooX87Od5hk/giphy.gif" alt="heart&brain" />
+  <img src="https://media.giphy.com/media/v1.Y2lkPTc5MGI3NjExOTgzODZhZDM1MWZhMDJiODNkODFhZTI3MWRjZDExZGQyYzBlNzMwYiZjdD1z/NfBApd81ooX87Od5hk/giphy.gif" alt="Animated illustration showing the collaboration between heart and brain, representing the diverse perspectives our ambassadors bring" />

63-63: Update documentation link to use main branch

The link to the Ambassador Program documentation uses a specific commit hash which might become outdated. Consider updating it to reference the main branch instead.

-Learn more about the [Ambassador Program here](https://github.com/asyncapi/community/blob/6c066e0eab6c778d1a37d1beebb1418a4bc700f6/AMBASSADOR_ORGANIZATION.md).
+Learn more about the [Ambassador Program here](https://github.com/asyncapi/community/blob/master/AMBASSADOR_ORGANIZATION.md).
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between e3c6bc9 and 7e4266b.

⛔ Files ignored due to path filters (2)
  • public/img/posts/2024-blog-banner/google.png is excluded by !**/*.png
  • public/img/posts/marketing-images/linkedin-analyze.png is excluded by !**/*.png
📒 Files selected for processing (11)
  • components/community/Card.tsx (0 hunks)
  • components/community/Header.tsx (0 hunks)
  • components/community/HomeCard.tsx (0 hunks)
  • markdown/blog/2024-marketing-report.md (1 hunks)
  • markdown/blog/gravitee-annoucement.md (1 hunks)
  • markdown/docs/community/_section.md (0 hunks)
  • pages/blog/asyncapi-student-ambassador-program (1 hunks)
  • pages/community/ambassadors/[id].tsx (0 hunks)
  • pages/community/ambassadors/index.tsx (0 hunks)
  • pages/community/events/index.tsx (0 hunks)
  • pages/community/index.tsx (0 hunks)
💤 Files with no reviewable changes (8)
  • components/community/Card.tsx
  • components/community/Header.tsx
  • components/community/HomeCard.tsx
  • markdown/docs/community/_section.md
  • pages/community/ambassadors/[id].tsx
  • pages/community/ambassadors/index.tsx
  • pages/community/events/index.tsx
  • pages/community/index.tsx
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2024-marketing-report.md

[grammar] ~50-~50: 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] ~67-~67: Consider removing “of” to be more concise
Context: ...ore were 2363. The goal was to disburse all of the items by December 2024. ![Merchandise ...

(ALL_OF_THE)

🪛 Markdownlint (0.35.0)
markdown/blog/gravitee-annoucement.md

28-28: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


30-30: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


32-32: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

🔇 Additional comments (5)
markdown/blog/gravitee-annoucement.md (4)

3-3: Verify the future publication date

The post is dated June 4, 2024. If this is intentional for scheduled publishing, please ensure your content management system supports future dating. Otherwise, consider updating to a current date.


17-40: Content structure and messaging look great!

The announcement is well-structured with clear sections covering:

  • Introduction
  • About Gravitee
  • Partnership benefits
  • Acknowledgment
  • Call to action with relevant links

The messaging effectively communicates the value of the partnership and its impact on the AsyncAPI community.

🧰 Tools
🪛 Markdownlint (0.35.0)

28-28: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


30-30: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


32-32: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


7-7: Verify the cover image existence

Let's verify that the cover image exists at the specified path.

✅ Verification successful

Cover image path is valid and accessible

The cover image exists at the specified path /img/posts/marketing-images/gravitee-announcement.webp, confirming that the image reference in the markdown file is correct.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the cover image exists
if [ -f "public/img/posts/marketing-images/gravitee-announcement.webp" ]; then
    echo "Cover image exists"
else
    echo "Cover image not found"
fi

Length of output: 120


40-40: Verify external links

Let's verify that the external links are accessible.

✅ Verification successful

External links are valid and accessible

Both external links in the markdown file are working correctly:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the external links are accessible
urls=("https://www.gravitee.io/" "https://www.asyncapi.com/en")

for url in "${urls[@]}"; do
    if curl --output /dev/null --silent --head --fail "$url"; then
        echo "$url is accessible"
    else
        echo "$url is not accessible"
    fi
done

Length of output: 448

pages/blog/asyncapi-student-ambassador-program (1)

53-56: Verify the ambassador registration document link

Let's ensure the referenced document link is accessible and contains the correct information.

✅ Verification successful

Let me verify the content of the document to ensure it's not just accessible but also contains the expected structure for ambassador registration.


Link is valid and document contains correct ambassador registration information

The referenced document is accessible and contains the expected structure for ambassador registration. The JSON file includes detailed information about current ambassadors, including their names, biographical information, and contributions, which aligns with the ambassador program requirements mentioned in the blog post.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the AMBASSADORS_MEMBERS.json file exists and is accessible
curl -s -f -L https://raw.githubusercontent.com/asyncapi/community/master/AMBASSADORS_MEMBERS.json > /dev/null
if [ $? -eq 0 ]; then
    echo "Document is accessible"
else
    echo "Document is not accessible"
fi

Length of output: 173


Script:

#!/bin/bash
# Fetch and examine the content of AMBASSADORS_MEMBERS.json
curl -s https://raw.githubusercontent.com/asyncapi/community/master/AMBASSADORS_MEMBERS.json | jq '.' || echo "Invalid JSON format"

Length of output: 25648

Comment on lines +1 to +2
---
title: "Gravitee Sponsorship Announcement"
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix spelling error in the title

The word "Announcement" is misspelled as "Annoucement".

-title: "Gravitee Sponsorship Annoucement"
+title: "Gravitee Sponsorship Announcement"

Note: The filename also contains the same spelling error and should be renamed to gravitee-announcement.md.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
---
title: "Gravitee Sponsorship Announcement"
---
title: "Gravitee Sponsorship Announcement"

Comment on lines +1 to +15
---
title: "AsyncAPI Student Ambasador Program"
date: 2024-07-31T06:00:00+01:00
type: Communication
tags:
- Student Ambassador Program
cover: /img/posts/ambassador-program/cover.webp
authors:
- name: Atinuke Oluwabamikemi Kayode
photo: /img/avatars/bami.webp
link: https://www.linkedin.com/in/atinuke-oluwabamikemi-kayode-5b838b1b7/
byline: AsyncAPI Community Marketing Specialist
excerpt: Information about AsyncAPI Student Ambassador Program.
featured: true
---
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix typo in title and review publication date

  1. There's a typo in the title: "Ambasador" should be "Ambassador"
  2. The publication date is set to July 31, 2024, which is in the future. This might affect the blog post's visibility. Consider updating it to a current date.
-title: "AsyncAPI Student Ambasador Program"
+title: "AsyncAPI Student Ambassador Program"
-date: 2024-07-31T06:00:00+01:00
+date: 2024-01-31T06:00:00+01:00
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
---
title: "AsyncAPI Student Ambasador Program"
date: 2024-07-31T06:00:00+01:00
type: Communication
tags:
- Student Ambassador Program
cover: /img/posts/ambassador-program/cover.webp
authors:
- name: Atinuke Oluwabamikemi Kayode
photo: /img/avatars/bami.webp
link: https://www.linkedin.com/in/atinuke-oluwabamikemi-kayode-5b838b1b7/
byline: AsyncAPI Community Marketing Specialist
excerpt: Information about AsyncAPI Student Ambassador Program.
featured: true
---
---
title: "AsyncAPI Student Ambassador Program"
date: 2024-01-31T06:00:00+01:00
type: Communication
tags:
- Student Ambassador Program
cover: /img/posts/ambassador-program/cover.webp
authors:
- name: Atinuke Oluwabamikemi Kayode
photo: /img/avatars/bami.webp
link: https://www.linkedin.com/in/atinuke-oluwabamikemi-kayode-5b838b1b7/
byline: AsyncAPI Community Marketing Specialist
excerpt: Information about AsyncAPI Student Ambassador Program.
featured: true
---

@iambami iambami closed this Nov 29, 2024
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.

4 participants