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 mascot blog #3733

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

Conversation

nwanduka
Copy link

@nwanduka nwanduka commented Feb 24, 2025

Description
This blog post covers the redesign of the AsyncAPI mascots, Eve and Chan, and their backstory.

Summary by CodeRabbit

  • Documentation
    • Added a new blog post detailing the redesigned mascots, Eve and Chan, including their origin, design evolution, and upcoming community initiatives.

Copy link
Contributor

coderabbitai bot commented Feb 24, 2025

Walkthrough

This pull request adds a new markdown file to the blog titled AsyncAPI Mascot Redesign: The Biography of Eve and Chan. The file contains complete metadata including publication date, tags, cover image, and authorship details. Its body presents the mascots' narrative with headings and subheadings that detail their origin, design evolution, and community involvement. The file invites further engagement from the AsyncAPI community.

Changes

File Summary
markdown/blog/asyncapi-mascot-redesign.md New blog post with metadata and a narrative explaining the AsyncAPI mascots' redesign, origin, and future use.

Possibly related PRs

Suggested labels

ready-to-merge

Suggested reviewers

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

Poem

I’m hopping through the code, so light and free,
New tales of mascots sprout in our digital tree.
Eve and Chan shine in lines so neat,
A redesign journey with a rhythmic beat.
CodeRabbit cheers with a joyful hop,
Celebrating fresh ideas that never stop! 🐇
Let your code bloom as bright as a spring crop!


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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

Copy link

netlify bot commented Feb 24, 2025

Deploy Preview for asyncapi-website failed.

Built without sensitive environment variables

Name Link
🔨 Latest commit 8bd367b
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/67bcfbe4309d340008a0019a

Copy link

codecov bot commented Feb 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (89c7f7a) to head (8bd367b).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #3733   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           20        20           
  Lines          732       732           
=========================================
  Hits           732       732           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@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/asyncapi-mascot-redesign.md (2)

26-26: Stylistic Suggestion: Replace "exactly"

Consider substituting the word "exactly" with an alternative such as "precisely" to avoid repetition and enhance the narrative’s tone.

🧰 Tools
🪛 LanguageTool

[style] ~26-~26: Consider an alternative for the overused word “exactly”.
Context: ...ife beyond the Figma canvas, and that’s exactly how I feel about the new mascots. Thro...

(EXACTLY_PRECISELY)


28-30: Typographical Improvement: Remove Comma Before "if you will"

In the sentence "This is the story of Eve and Chan—their biography, if you will.", removing the comma before "if you will" may improve readability.

🧰 Tools
🪛 LanguageTool

[typographical] ~30-~30: Usually, there’s no comma before “if”.
Context: ...he story of Eve and Chan—their biography, if you will. ## The Birth of Eve and Cha...

(IF_NO_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 89c7f7a and 8bd367b.

📒 Files selected for processing (1)
  • markdown/blog/asyncapi-mascot-redesign.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/asyncapi-mascot-redesign.md

[style] ~26-~26: Consider an alternative for the overused word “exactly”.
Context: ...ife beyond the Figma canvas, and that’s exactly how I feel about the new mascots. Thro...

(EXACTLY_PRECISELY)


[typographical] ~30-~30: Usually, there’s no comma before “if”.
Context: ...he story of Eve and Chan—their biography, if you will. ## The Birth of Eve and Cha...

(IF_NO_COMMA)

⏰ Context from checks skipped due to timeout of 180000ms (1)
  • GitHub Check: Lighthouse CI
🔇 Additional comments (9)
markdown/blog/asyncapi-mascot-redesign.md (9)

1-17: Metadata Front Matter Integrity

The YAML front matter is comprehensive, including the title, publication date, tags, cover image, authorship details, and excerpt. Verify that the publication date aligns with the intended release schedule.


19-25: Table of Contents Structure

The table of contents is clear and well-organized. It effectively guides readers through the blog post sections.


33-42: Engaging Narrative on Mascot Origins

The section "The Birth of Eve and Chan" provides a clear and engaging backstory, linking the design origins to community engagement and initial creative ideation.


45-47: Image Reference and Accessibility Check

The image reference for the poll is appropriately formatted. Please ensure that the image path and alt text provide sufficient context for accessibility.


48-50: Detailed Explanation for Dual Mascots

The explanation behind having two mascots is informative and adds valuable depth to the narrative. The conversational tone is engaging.


51-55: Clear Redesign Rationale

The "Why the Redesign?" section clearly outlines the motivations behind updating the mascots. The contextual details and reference link add credibility to the narrative.


57-63: Introduction of Redesigned Mascots

The "Meet Eve and Chan" section successfully introduces the redesigned mascots. The inclusion of imagery supports visual storytelling nicely.


66-70: Engaging Future Outlook

The "What's Next for Eve and Chan?" segment effectively sets an anticipatory tone, inviting the community to look forward to upcoming engagements involving the mascots.


72-74: Verification of Reference Links

Ensure that the image paths and descriptions for the referenced assets (poll image and mascots image) are correct and that the corresponding files exist.

@thulieblack thulieblack changed the title chore(blog): mascot blog chore(blog): add mascot blog Feb 25, 2025

AsyncAPI’s mascots, Eve and Chan, have had a brand refresh, and I’m proud to say that I had a hand in their redesign. Now, seeing the community use them in different ways just warms my heart. Any designer will tell you that nothing beats the feeling of seeing your work come to life beyond the Figma canvas, and that’s exactly how I feel about the new mascots.

Throughout the redesign process, I kept asking myself questions to ensure the new look stayed true to their original purpose. Whose idea was it to have the mascots? Why the names Eve and Chan? Who designed them originally? Who are Eve and Chan, really?
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Throughout the redesign process, I kept asking myself questions to ensure the new look stayed true to their original purpose. Whose idea was it to have the mascots? Why the names Eve and Chan? Who designed them originally? Who are Eve and Chan, really?
Throughout the redesign process, I kept asking myself questions to ensure the new look stayed true to its original purpose. Whose idea was it to have the mascots? Why the names Eve and Chan? Who designed them originally? Who are Eve and Chan?

- [Meet Eve and Chan](#meet-eve-and-chan)
- [What’s Next for Eve and Chan?](#whats-next-for-eve-and-chan)

AsyncAPI’s mascots, Eve and Chan, have had a brand refresh, and I’m proud to say that I had a hand in their redesign. Now, seeing the community use them in different ways just warms my heart. Any designer will tell you that nothing beats the feeling of seeing your work come to life beyond the Figma canvas, and that’s exactly how I feel about the new mascots.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
AsyncAPI’s mascots, Eve and Chan, have had a brand refresh, and I’m proud to say that I had a hand in their redesign. Now, seeing the community use them in different ways just warms my heart. Any designer will tell you that nothing beats the feeling of seeing your work come to life beyond the Figma canvas, and that’s exactly how I feel about the new mascots.
AsyncAPI’s mascots, Eve and Chan, have had a brand refresh, and I’m proud to say that I helped redesign them. Seeing the community use them in different ways warms my heart. Any designer will tell you that nothing beats seeing your work come to life beyond the Figma canvas, and that’s exactly how I feel about the new mascots.


Throughout the redesign process, I kept asking myself questions to ensure the new look stayed true to their original purpose. Whose idea was it to have the mascots? Why the names Eve and Chan? Who designed them originally? Who are Eve and Chan, really?

As it turns out, I’m not the only one with these questions. Within and outside the AsyncAPI community, folks have often wondered about the origins of these characters. So, I recently sat down with Fran Mendez, the founder of AsyncAPI, to get their backstory. This is the story of Eve and Chan—their biography, if you will.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
As it turns out, I’m not the only one with these questions. Within and outside the AsyncAPI community, folks have often wondered about the origins of these characters. So, I recently sat down with Fran Mendez, the founder of AsyncAPI, to get their backstory. This is the story of Eve and Chan—their biography, if you will.
As it turns out, I’m not the only one with these questions. Within and outside the AsyncAPI community, folks have often wondered about the origins of these characters. So, I recently sat down with Fran Mendez, the founder of AsyncAPI, to get their backstory. This is the story of Eve and Chan—their biography.


## The Birth of Eve and Chan

It was Fran’s idea to have a mascot that people could easily associate with the AsyncAPI brand. Most open-source projects and companies use mascots to reinforce their brand identity, so why not AsyncAPI? You know how Linux has Tux the penguin, and GitHub has Octocat? Fran wanted something like that for AsyncAPI.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
It was Fran’s idea to have a mascot that people could easily associate with the AsyncAPI brand. Most open-source projects and companies use mascots to reinforce their brand identity, so why not AsyncAPI? You know how Linux has Tux the penguin, and GitHub has Octocat? Fran wanted something like that for AsyncAPI.
[Fran Méndez’s](https://www.linkedin.com/in/fmvilas) idea was to have a mascot that people could easily associate with the AsyncAPI brand. Most open-source projects and companies use mascots to reinforce their brand identity, so why not AsyncAPI? Since Linux has Tux, the Penguin, and GitHub has Octocat, Fran wanted something like that for AsyncAPI.


It was Fran’s idea to have a mascot that people could easily associate with the AsyncAPI brand. Most open-source projects and companies use mascots to reinforce their brand identity, so why not AsyncAPI? You know how Linux has Tux the penguin, and GitHub has Octocat? Fran wanted something like that for AsyncAPI.

Originally, he envisioned just one character, something eye-catching that could also work well on merch. The goal was to create swag people would actually want to buy. Not everyone would wear a hoodie with just a logo slapped on it. But a mascot? That’s stylish, versatile, and could be worn anywhere.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Originally, he envisioned just one character, something eye-catching that could also work well on merch. The goal was to create swag people would actually want to buy. Not everyone would wear a hoodie with just a logo slapped on it. But a mascot? That’s stylish, versatile, and could be worn anywhere.
Initially, he envisioned just one eye-catching character that could work well on merch. The goal was to create swag people would want to buy. Not everyone would wear a hoodie with just a logo slapped on it. But a mascot? That’s stylish, versatile, and could be worn anywhere.

It was Fran’s idea to have a mascot that people could easily associate with the AsyncAPI brand. Most open-source projects and companies use mascots to reinforce their brand identity, so why not AsyncAPI? You know how Linux has Tux the penguin, and GitHub has Octocat? Fran wanted something like that for AsyncAPI.

Originally, he envisioned just one character, something eye-catching that could also work well on merch. The goal was to create swag people would actually want to buy. Not everyone would wear a hoodie with just a logo slapped on it. But a mascot? That’s stylish, versatile, and could be worn anywhere.
Ultimately, the mascot was to serve two purposes: strengthen AsyncAPI’s brand identity and help raise funds for the project through merch sales.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Ultimately, the mascot was to serve two purposes: strengthen AsyncAPI’s brand identity and help raise funds for the project through merch sales.
Ultimately, the mascot served two purposes: strengthening AsyncAPI’s brand identity and helping raise funds for the project through merch sales.

Originally, he envisioned just one character, something eye-catching that could also work well on merch. The goal was to create swag people would actually want to buy. Not everyone would wear a hoodie with just a logo slapped on it. But a mascot? That’s stylish, versatile, and could be worn anywhere.
Ultimately, the mascot was to serve two purposes: strengthen AsyncAPI’s brand identity and help raise funds for the project through merch sales.

The first version of the mascots was designed by an illustrator from a studio in Colombia. He came up with two characters: a bold female lead and a quirky extraterrestrial. Now the mascots were ready—but what’s a mascot without a name?
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
The first version of the mascots was designed by an illustrator from a studio in Colombia. He came up with two characters: a bold female lead and a quirky extraterrestrial. Now the mascots were ready—but what’s a mascot without a name?
An illustrator from a studio in Colombia designed the first version of the mascots. He created two characters: a bold female lead and a quirky extraterrestrial. Now the mascots were ready—but what’s a mascot without a name?


The first version of the mascots was designed by an illustrator from a studio in Colombia. He came up with two characters: a bold female lead and a quirky extraterrestrial. Now the mascots were ready—but what’s a mascot without a name?

Fran took to his socials and asked the community for suggestions. Someone came up with Eve and Chan—Eve for "events" and Chan for "channels." Not only were they catchy, but they actually tied back to what AsyncAPI does. Real names with real meaning. It was brilliant.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Fran took to his socials and asked the community for suggestions. Someone came up with Eve and Chan—Eve for "events" and Chan for "channels." Not only were they catchy, but they actually tied back to what AsyncAPI does. Real names with real meaning. It was brilliant.
Fran took to his socials and asked the community for suggestions. Someone came up with Eve and Chan—Eve for "events" and Chan for "channels." Not only were they catchy, but they also tied back to what AsyncAPI does. Real names with real meaning. It was brilliant.

![Poll for mascot name suggestions][poll]


If you’re wondering, like I did, why there are two mascots instead of just one, it’s because they were designed to tell a story. Eve is the skilled, knowledgeable one who always does things the right way, while Chan is a bit clumsy, representing the mistakes people often make in event-driven architectures.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
If you’re wondering, like I did, why there are two mascots instead of just one, it’s because they were designed to tell a story. Eve is the skilled, knowledgeable one who always does things the right way, while Chan is a bit clumsy, representing the mistakes people often make in event-driven architectures.
If you’re wondering, like I was, why there are two mascots instead of just one, it’s because they were designed to tell a story. Eve is the skilled, knowledgeable one who always does things correctly, while Chan is slightly clumsy. Together, they represent the mistakes people often make in event-driven architecture.


## Why the Redesign?

About two years after their debut in 2019, the mascots were due for a visual refresh. While the original designs were charming, they were also too detailed for AsyncAPI’s needs. The goal was to simplify their look—using basic shapes, fewer curves, and minimal shading—to make them more versatile and easier to use across different formats. This redesign aimed to create a cleaner, more adaptable style while preserving the essence of the original concept.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
About two years after their debut in 2019, the mascots were due for a visual refresh. While the original designs were charming, they were also too detailed for AsyncAPI’s needs. The goal was to simplify their look—using basic shapes, fewer curves, and minimal shading—to make them more versatile and easier to use across different formats. This redesign aimed to create a cleaner, more adaptable style while preserving the essence of the original concept.
About two years after their debut in 2019, the mascots were due for a visual refresh. While the original designs were charming, they were too detailed for AsyncAPI’s needs. The goal was to simplify their look—using basic shapes, fewer curves, and minimal shading—to make them more versatile and easier to use across different formats. This redesign aimed to create a cleaner, more adaptable style while preserving the essence of the original concept.


Designing Eve and Chan was both a challenge and an honor, and I can’t wait to see all the fun and creative ways the community brings them to life. You’ve probably already seen them in some of our social media posts, and they’re now the face of AsyncAPI’s GitHub bots. We’re looking to feature them on swag, in documentation, at community events, and more.

So, if you’ve ever wondered about the story behind these little characters, now you know. And if you’re part of the AsyncAPI community, get ready. You’ll be seeing a lot more of them.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
So, if you’ve ever wondered about the story behind these little characters, now you know. And if you’re part of the AsyncAPI community, get ready. You’ll be seeing a lot more of them.
So, if you’ve ever wondered about the story behind these little characters, now you know, and if you’re part of the AsyncAPI community, get ready. You’ll be seeing a lot more of them.

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.

Minor changes on the blog, I'm super proud of you @nwanduka

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.

3 participants