Design Meeting, 16:00 UTC Thursday February 20th 2025

[asyncapi-bot]

Meeting Info	Details
Purpose	Catching up to discuss the conference design and everything related to design, research, accessibility, and related topics.
Time	16:00 UTC | Translate to your time zone with the time zone converter.
Meeting Place	Link
Zoom	Join live.
YouTube	Watch live and interact through live chat.
Twitch	Watch live.
Twitter	Watch live.
LinkedIn	Watch live.
More Info	Details
Meeting Recordings	YouTube Playlist.
AsyncAPI Initiative Calendar	Public URL.
iCal File	Add to your calendar.
Newsletter	Subscribe to get weekly updates on upcoming meetings.

Agenda

Don't wait for the meeting to discuss topics that already have issues. Feel free to comment on them earlier.

1. Q&A
2. Place for your topic
3. Q&A

Notes

Add notes here after the meeting.

[Mayaleeeee]

AsyncAPI Design Working Group Meeting Agenda

📅 Date: February 20th, 2025
⏰ Time: 4 PM UTC
📍 Location: Zoom
📝 Facilitator: Maya

1. Welcome & Housekeeping (5 mins)

• Brief welcome and introductions if needed
• Confirming a note-taker (preferably a person instead of Zoom AI-generated notes)

2. Holopin Design Project Update (5 mins) – Olumide

• Progress so far
• Any blockers or challenges?
• Next steps

3. Conference Design Issues – Discussion & Quick Collaboration (25 mins)

• Overview of open design issues for AsyncAPI Conf
• Assigning tasks to contributors
• Live Design Collaboration (if time allows): Quick brainstorming or initial design work on an issue
• review Tenzin work on the design

4. AsyncAPI Website Redesign & Research Initiative

5. Open Discussion & Next Steps (5 mins)

• Any blockers or challenges?
• Assigning action items and responsibilities
• Confirming the next meeting date: March 6th, 2025

[Mayaleeeee]

Hello, folks

Below is the summary of our design meeting.

Meeting summary for Design Meeting (02/20/2025)
Quick recap
The team discussed various design projects, including the Mentorship Project, the community pages, and the 2025 Conference Speaker banner. They also discussed the redesign of the Asyn Kpi website, emphasizing the importance of UX research before implementation. Lastly, they addressed technical issues and welcomed new members to the team, with a focus on improving engagement and visibility of work.

Next steps
• Olumide to complete the remaining changes on the project badges and submit the report by evening or first thing tomorrow morning.
• Olumide to incorporate feedback on the badges design, including using gradient colors and Async API components.
• Olumide to make the badge design work more visible by sharing it on the Slack general channel and design channel for community feedback.
• Tenzin to improve the speaker card design by making it wider, adding more information, and following the defined size for promotional cards.
• Wuraola to design a Speaker banner for the 2025 Conference using the general Figma file for the Async API 2025 Conference.
• Maya to add Wuraola to the Async API 2025 Conference Figma file.
• All designers to focus more on UX research before implementing website redesigns.
• All team members to prepare for the next design meeting in 2 weeks, same time and day.

Summary
New Team Members and Technical Issues
Maya, the design lead, initiated a meeting with the team, including new members Wuraola, Tenzin, Victoria, and Olumide. The meeting was to be live-streamed on YouTube, with Thulie monitoring the chat and YouTube for engagement. Maya shared the meeting agenda and encouraged the new members to introduce themselves. The team discussed technical issues, such as screen sharing and audio, and welcomed new members to the team.

Mentorship Project Finalization and Feedback
In the meeting, Maya initiated a note-taking task for the agenda items, but no volunteer came forward. The discussion then shifted to updates from the Mentorship Project, with Olumide sharing his experiences and progress on the project. He mentioned that he was done with most of the work and was making some final changes. Maya asked if there were any challenges, but Olumide did not mention any. The conversation ended with Thulie mentioning that she had provided feedback on the design pages and was ready to answer any questions.

Enhancing Community Pages Design and Mascots
Thulie discussed the need for improvement in the design of the community pages, suggesting the use of gradient colors and incorporating new mascots. She emphasized the importance of making work visible to the community for feedback and involvement. Thulie also suggested a more inclusive approach to the 'Maintainer' badge, proposing a single badge that encompasses different aspects of maintenance. Lastly, she encouraged more creativity in using the mascots, suggesting they could be used as stickers or badges. Oluwamidie sought clarification on whether he should create stickers and badges from the mascots, to which Thulie responded affirmatively.

Designing Conference and Mascot Elements
Thulie suggested incorporating mascots into the design, specifically for appreciating maintenance, and provided links with examples. Oluwademilade agreed to communicate any further questions with Thulie. Maya then discussed design issues for the conference, encouraging Oluwademilade to make the work more visible and share it on the Slack channel. Tenzin was instructed to improve the speaker card design, with the size of the elements and promotional cards as key considerations.

Speaker Banner Design Discussion
Maya and Wuraola discussed the design of a Speaker banner for the 2025 Conference. Maya instructed Wuraola to drop a link to the Figma file in a DM so she could add it to the general Figma file for the conference. Maya also explained how to identify open design issues for the conference website, emphasizing the use of tags for design. Wuraola confirmed her understanding of the process. No other issues or questions were raised during the meeting.

Asyn Kpi Website Redesign Discussion
In the meeting, Maya discussed the ongoing redesign of the Asyn Kpi website, highlighting the importance of UX research before implementation. She expressed her desire for the research to be a significant project in the community, not just a design change. Maya also mentioned that she would share the new design and encouraged others to contribute to the research. The conversation ended with Maya asking for feedback on the proposed time for the next meeting. Wuraola confirmed that she had navigated the repo and dropped comments on the speakers banner.