Your work can shape better public services
Report a problem, improve the UX4G web design system, or share a website, portal, app, pattern, or service you built with UX4G.
Start in the right place
GitHub is for issues and code. The contributor form is for design work, end-to-end projects, research, and public showcase submissions.
Found a bug or want a feature?
Search existing issues, then open one with steps, environment details, and sanitised evidence.
Ready to change the system?
Read the repository guide, discuss larger changes, fork the project, and open a focused pull request.
Designed or built something with UX4G?
Submit it for review, possible publication, and contributor attribution.
What a repository-ready contribution includes
The official web design system has a concrete contribution contract. Use it before opening a pull request.
- 01
Put it in the right layer
Tokens in src/tokens, semantic mappings in src/semantic, utilities in src/utilities, components in src/components, and patterns in src/pattern or src/pattern-html.
- 02
Document the behaviour
Add or update a Storybook story with a clear title, component description, and at least an Introduction export.
- 03
Regenerate project context
Run npm run generate-llm-context so llms.txt, llms-full.txt, and catalog.json remain current.
- 04
Prove quality
Run the build and verify semantic HTML, keyboard use, visible focus, WCAG 2.1 AA, assistive technology, and automated checks.
Your name stays connected to accepted work
With your consent, an accepted component, pattern, resource, or showcase may be published with your display name and organisation. Future NeGD or MeitY certificates and awards may be introduced, but submission does not promise certification, endorsement, or acceptance.
What reviewers look for
4 Evaluation CriteriaClear Usage & Rights
Original work with clear usage, open distribution, and IP rights.
Broad Public Value
Solves real problems and can be reused across public digital services.
UX4G Design Alignment
Strict alignment with tokens, semantics, and responsive layout rules.
Tested Accessibility
Complete keyboard focus, semantic HTML, and WCAG 2.1 AA compliance.
Submit your contribution
Use this guided form to submit design resources, public showcases, case studies, or proposal reviews.
What happens after you submit
Review is collaborative. A complete submission makes the first response faster, but it does not guarantee publication.
Triage
We check scope, ownership, safety, completeness, and duplicates.
Review
Design, engineering, content, and accessibility reviewers assess the work.
Improve
You may receive focused requests before the contribution can be accepted.
Publish
Accepted work is merged or showcased with the attribution you approved.