How Tencent’s TDesign Scales an Enterprise Design System Across Multiple Frameworks

1. TDesign Organization

TDesign is Tencent's enterprise‑level design system, open‑sourced at the end of 2021, supporting four frameworks. It was built to unify scattered component libraries, reduce duplication, and meet both internal and external demands through open‑source collaboration.

1.1 Project Management Committee (PMC) Members

PMC members set open‑source goals, hold weekly meetings to discuss issues, review progress, and ensure timely delivery. After open‑sourcing, PMC remains the decision‑making core, assigning tasks to contributors across technology stacks.

1.2 Joint Project Teams

Because many contributors work part‑time, joint teams from various business units share OKRs and handle daily operations, guaranteeing development speed and product quality when component owners are unavailable.

1.3 Contributors

Both occasional bug‑fixers and core contributors participate; active core contributors may be invited to join PMC. The community welcomes external contributors to become PMC members and help grow TDesign.

2. Open‑Source Governance Mechanism

2.1 Rule‑Centric Governance

TDesign defined nine comprehensive specifications covering component development, API design, code style, and project maintenance, which are continuously refined to give contributors clear boundaries.

2.2 Tool Construction

2.2.1 API Design Platform

A unified API specification and CLI tools enable consistent component definitions across all supported frameworks, reducing cross‑stack development friction.

2.2.2 GitHub Automation

GitHub templates streamline issue and PR submission; GitHub Actions automatically assign issues, generate preview links, and run checks, improving contributor experience and preventing feedback loss.

2.3 Documentation Collaboration

Design documentation is shared via a single repository; all framework sites import it as a Git submodule, ensuring UI consistency while allowing each framework to focus on component demos.

3. From Internal to Public Open‑Source

3.1 Code Open‑Source

Instead of a single initial commit, TDesign preserved full commit history by rewriting authorship to external GitHub accounts, ensuring traceability and compliance with security policies.

3.2 Documentation Open‑Source

All internal design docs and key issue discussions were migrated to the GitHub Wiki, making them publicly accessible.

3.3 Process Open‑Source

The team uses GitHub Projects as a public task board, exposing weekly iterations and future plans, inviting the community to follow and contribute to TDesign's roadmap.

4. Contributor Incentives

4.1 Growth Path

Five levels—User, Contributor, Core Contributor, PMC, Honorary Contributor—guide personal development and responsibilities.

4.2 Rewards

Contributors are listed on GitHub and the official site, and receive perks such as swag, custom avatars, cash bonuses, and team‑building events.