Skip to content

Create a Unified Conference Asset System #126

@Mayaleeeee

Description

@Mayaleeeee

Problem

Our conference-related design assets (banners, presentations, social graphics, etc.) are scattered across GitHub repos and Figma files. There is no centralized structure, documentation, or easy way to find or reuse them. This creates duplication, inconsistencies, and wasted effort when preparing for each event.

Why This Is Needed

AsyncAPI conferences are one of our biggest opportunities to showcase our community and brand. A unified asset system will:

  • Improve discoverability and reuse of assets across teams

  • Ensure brand consistency across all event materials

  • Save time for designers and contributors

  • Provide a single source of truth for future events

Deliverables

  • Audit existing conference assets across GitHub and Figma

  • Collect and organize assets in a single GitHub repo folder (with links to Figma files where applicable)

  • Create a README.md that includes:

  • Recommend missing or useful assets to add

Metadata

Metadata

Assignees

Labels

bountyAsyncAPI Bounty

Type

No type

Projects

Status

Completed

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions