Skip to content

Create a Unified Iconography System for Marketing & Tooling #119

Description

@Mayaleeeee

Background

In the past, there was an effort to audit and categorize icons used across AsyncAPI’s ecosystem. That issue is now outdated and has been closed in favor of this clearer, more scoped task aligned with the current design system and brand.

This task builds on the existing AsyncAPI design system by creating a unified icon set for use across marketing (e.g., website, docs, social graphics) and tooling (e.g., product UIs, dev tools).

Problem

Currently, icons used across our brand ecosystem are inconsistent, scattered across different files, and not aligned with our new design system. Some are legacy, some are borrowed from libraries, and others are ad hoc creations with different visual styles (stroke weights, shapes, color use).

This leads to:

  • Brand inconsistency across websites, docs, and UI
  • Inefficiencies for contributors needing icons
  • Visual clutter or confusion

Why This Is Needed

Icons are essential building blocks of both our marketing and product design. A unified, reusable icon system will:

  • Reinforce visual consistency and brand identity
  • Reduce design debt and duplicated work
  • Improve usability and accessibility in our tooling
  • Make it easier for contributors to use the correct icons

Deliverables

  • Audit existing icons across marketing and tooling
  • Identify inconsistencies and duplicates
  • Map icons to existing design system icons
  • Define icon usage rules (stroke, grid, style)
  • Document icon guidelines + contribution process
  • Organize icons in Figma
  • Fill only missing icons if absolutely needed

Reference

This issue replaces: #10 - Brand Refresh: Iconography

Metadata

Metadata

Assignees

Labels

🎨 designDesign thinking/mockups neededarea/designSpecify what technical area given issue relates to. Its goal is to ease filtering good first issues.bountyAsyncAPI Bounty

Type

No type

Projects

Status
Completed

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions