Open Design is built by people, in public. Skills, DESIGN.md systems, plugins, docs — every commit is a brushstroke. Pick an issue, send a PR, and earn a one-of-one honor card the moment you're merged.
Open a local atelier. Convene the meetups, the demos, the late-night critiques — the studio carries the work with budget, materials, and a line straight to the team.
Ambassadors turn Open Design from a repository into something contributors can meet — in a room, with ink on the table and coffee gone cold.
Designers, developers, organizers — the kind who already gather others. We give the gathering a flag.
Not a volunteer badge. A working bond — with budget, standing, and access.
A modest commitment, but binding. Extended absence folds into alumni status — the circle stays small and serious.
Maintainers protect the direction and quality of Open Design: they review contributions, keep the standard coherent, and make room for more contributors to earn their place in the project.
Nagendhra brings a data engineer's instinct for production truth: find the failure, measure the edge case, and fix it properly. In Open Design, that shows up in deploy preflight work, asset-bundling hardening, and Windows fixes that make the project feel trustworthy when contributors ship.
Sid is the generalist engineer with a designer's eye for detail: the kind of maintainer who notices both the broken CLI path and the crooked interaction affordance. In Open Design, Sid keeps export flows, plugin actions, Windows shims, MIME handling, and agent plumbing sharp enough for a community to build on.
A long-running record of talented contributors who keep turning ideas, fixes, and craft into the shared Open Design standard.
The long tail matters: design systems, docs fixes, examples, and small repairs are how an open design language becomes dependable.
A snapshot of sharp contributors landing PRs, improving the product, and making Open Design feel alive.
A contributor taking the lead with focused, generous work.
Live from label:“good first issue” on the Open Design repo. Comment on an issue to claim it — a maintainer will assign it within a day.
Whether you're a designer, a writer, an engineer, or someone who just spotted a typo — there's a contribution shape for you. Here's the path.
Browse the good-first-issues list above, or open a new issue describing something you'd improve. Designers — DESIGN.md systems are the easiest entry.
Fork, branch, push. Mark it draft — it signals you want feedback early. Mention which issue it closes. The CI is fast; bot-cards stays on its own branch.
A maintainer reviews within 24h. We're kind, specific, and never gatekeep. If you're stuck, drop the PR link in Discord #help.
The bot mints your honor card the moment you're merged and pushes it to the bot-cards branch. Share it on X with #openDesign — we repost the best ones.
Our Discord is where contributors show shipped work, discuss plugins, join beta tests, and get help when a PR gets stuck. No fake activity counters — just the channels people can actually use.