π 1. /docs/README.md
`
The GitDigital Emoji Library is the visual language of the GitDigital ecosystem.
It defines the emojis used for repositories, teams, roles, badges, workflows, and contributorβeconomy systems.
This library acts as the source of truth for:
- Emoji taxonomy
- Repo prefix mapping
- Contributor badges
- Governance roles
- Protocol categories
- Design system rules
- Machineβreadable registry for bots
Every GitDigital organization, repo, and product should reference this library to ensure consistency, clarity, and contributorβfriendly UX.
Why Emojis?
Emojis provide:
- Instant cognitive recognition
- A universal visual language
- A friendly, modern contributor experience
- A consistent identity across 300+ repositories
- A foundation for gamification and contributor rewards
emoji-library/ β βββ taxonomy/ βββ sets/ βββ mappings/ βββ design-system/ βββ badges/ βββ docs/ βββ registry.json
Each folder contains a specific part of the emoji operating system.
- Choose emojis from the taxonomy or sets.
- Apply mappings to repos, teams, or workflows.
- Follow design-system rules for consistency.
- Use badges for contributor recognition.
- Reference registry.json for automation and bots.
All new emoji proposals must include:
- Category
- Purpose
- Justification
- Example usage
- Suggested mappings
Submit proposals via emoji-proposal.md template (coming soon).
Open-source, permissive, and contributor-friendly. `
`
The GitDigital Emoji System is more than decoration β it is a functional design language.
It exists to:
- Reduce cognitive load
- Improve contributor onboarding
- Make repo scanning effortless
- Reinforce GitDigitalβs identity
- Support gamification and recognition
- Provide a universal visual vocabulary
Emojis act as microβlogos.
They make the ecosystem feel alive, intuitive, and welcoming.
This philosophy guides every decision in this library. `
`
This guide explains how to integrate the emoji system into GitDigital repos, teams, bots, and workflows.
Prefix repos with emojis based on their category:
- π§± Infrastructure β π§±-infra-*
- π€ Automation β π€-bot-*
- π Security β π-sec-*
- π Documentation β π-docs-*
- π§ͺ Experimental β π§ͺ-exp-*
Teams should use emojis that reflect their domain:
- π‘ Governance Team
- π§ Protocol Architects
- π Builder Team
- π€ Automation Team
Use emojis to mark sections:
- π Overview
- π§© Components
- βοΈ Setup
- π§ͺ Testing
- π‘ Security Notes
Bots consume registry.json to:
- Validate repo naming
- Enforce emoji usage
- Generate badges
- Apply contributor XP
- Tag PRs with emoji categories
Emojis should appear in:
- Repo titles
- Issue templates
- PR templates
- Wiki navigation
- Contributor profiles
`
`
This document defines how emojis are used in naming across the GitDigital ecosystem.
Format: --
- π§±-infra-core
- π€-bot-sync-engine
- π-sec-audit-runner
- π-docs-style-guide
- π§ͺ-exp-prototype-01
Format:
- π‘ Governance Team
- π§ Protocol Architects
- π Builder Squad
- π€ Automation Crew
Format:
- π§ Expert Architect
- π¦Ύ Automation Master
- π Builder Tier 2
- π§ Navigator Maintainer
Format:
- π Sync Repos
- β‘ Fast Merge
- π‘ Security Scan `
`
This file defines the core emoji categories used across the GitDigital ecosystem.
π§± Infrastructure
βοΈ Systems
π Tools
π§© Modules
π¦ Packages
π€ Automation
π Sync
β‘ Fast Actions
π§ Smart Logic
π Security
π‘ Governance
π Compliance
π§Ύ Audits
𧬠Core Protocol
π Onβchain
π API
π‘ Gateway
π° Network
π Docs
π Notes
π Guides
π§ Knowledge
π₯ Gold
π₯ Silver
π₯ Bronze
π§ Expert
π Builder
π§ Navigator
π£ New Contributor
π¦Ύ Automation Master
π§ͺ Lab
π§ WIP
π₯ Hot
`
`
Defines emojis for protocol layers.
- 𧬠Core Protocol
- π Onβchain Logic
- π API Layer
- π‘ Gateway Layer
- π° Network Layer
- π§© Modules
- π Extensions
`
`
- π‘ Governance Team
- π§ Protocol Architects
- π Builder Team
- π€ Automation Team
- π Documentation Team
- π§ͺ Research & Lab Team
`
`
- π§ Navigator (Maintainer)
- π Builder
- π§ Architect
- π‘ Guardian (Security)
- π¦Ύ Automation Specialist
- π£ New Contributor
`
`
XP Tiers
π£ Beginner
π Builder
π§ Expert
π¦Ύ Automation Master
π§ Architect
π₯ Streak
β‘ Fast Merge
π‘ Governance Guardian
π§© Modular Master
π Documentation Hero
`
`
- π Builder Lane
- π§ Expert Lane
- π§ Maintainer Lane
- π¦Ύ Automation Lane
- π Documentation Lane
- π§ͺ Research Lane
`
`
- π§± Infrastructure
- π€ Automation
- π Security
- π Documentation
- π§ͺ Experimental
- π§© Modules
- π Tools
`
`
- Emojis must be consistent with taxonomy.
- New emojis require proposal + approval.
- Repo prefixes must match category.
- Badges must use approved emoji sets.
- Bots enforce naming and usage.
`
`
This is the primary emoji set used across GitDigital.
π§± π€ π π π§ͺ π π§ π§ 𦾠𧬠π π π‘ π°
`
`
Used for optional or specialized contexts.
π₯
`
`
Used for events, holidays, and special releases.
π π π π β¨
`
`
Used for prototypes, labs, and early-stage ideas.
π§ͺ π§ π₯
`
`
π§± β infra-*
π€ β bot-*
π β sec-*
π β docs-*
π§ͺ β exp-*
π β tools-*
π§© β module-*
`
`
GitDigital Products β π§±
GitDigital Solana β π
OpenGrantStack β π―
Compliance Registry β π
Automation Suite β π€
`
`
Proof-of-Contribution Protocol β π§¬
Compliance Registry β π
RepoSync AI β π€
AutoDocs Generator β π
Governance Validator β π‘
`
`
π Repo Sync
β‘ Fast Merge
π‘ Security Scan
π Docs Build
π§ͺ Test Suite
`
`
π€ Automation
π Sync
β‘ Speed
π§ Smart Logic
π‘ Safety Checks
`
`
- Use emojis consistently.
- Use only approved emojis.
- Place emojis at the start of names.
- Avoid mixing categories.
- Keep meanings stable over time.
`
`
- Use emojis as prefixes
- Use emojis to clarify meaning
- Use emojis in docs and workflows
- Use random emojis
- Change meanings without approval
- Overload names with multiple emojis
`
`
- Always pair emojis with text
- Avoid relying on emoji alone
- Ensure screen readers can interpret names
`
`
Recommended UI color pairings for emoji categories.
π§± Infrastructure β Gray / Blue
π€ Automation β Purple / Neon
π Security β Red / Black
π Docs β Blue / White
π§ͺ Experimental β Yellow / Orange
`
`
Use clean, readable fonts with emojis.
Recommended:
- Inter
- Roboto
- SF Pro
- Open Sans
`
`
- π£ New Contributor
- π Builder
- π§ Expert
- π§ Maintainer
- π¦Ύ Automation Master
`
`
Tier 1 β π£
Tier 2 β π
Tier 3 β π§
Tier 4 β π¦Ύ
Tier 5 β π§
`
`
π₯ Streak
β‘ Fast Merge
π‘ Governance Guardian
π§© Modular Master
π Documentation Hero
`
`
π‘ Security Guardian
π§ Navigator
π§ Protocol Architect
`
{ "categories": { "infrastructure": "π§±", "automation": "π€", "security": "π", "docs": "π", "experimental": "π§ͺ" }, "badges": { "builder": "π ", "expert": "π§", "automation_master": "π¦Ύ" }, "repo_prefixes": { "infra": "π§±", "bot": "π€", "sec": "π", "docs": "π", "exp": "π§ͺ" } }