Contribute to Bridge UI—parity between React and Vue, and shared work in core.
Bridge UI is open source under the MIT license. Contributions of all sizes are welcome—bugs, docs, and new features.
Repository: github.com/Bridge-UI/core
Principles
From the project’s contributing guidance:
- Parity — React and Vue components should stay aligned (API, variants, behavior).
- Shared logic in core — types, tokens, and framework-agnostic logic belong in @bridge-ui/core; keep adapters thin.
- Discuss first when large — open an issue for API changes or new components before a big PR.
Ways to help
| Contribution | Where |
|---|---|
| Bug reports | GitHub Issues |
| Feature ideas | Issues or discussions on the core repo |
| Package code | Pull requests against Bridge-UI/core |
| Documentation site | This docs/site repo—add pages in both en-us and pt-br |
Suggested workflow (core)
-
Fork and clone
Fork and clone Bridge-UI/core.
-
Install and verify
Install dependencies and follow the repo’s scripts for type-check, test, and package builds.
-
Implement with parity
Implement shared changes in packages/core when possible; update packages/react and packages/vue together.
-
Cover both adapters
Add or update tests for both adapters when behavior changes.
-
Open a PR
Open a PR with a clear description and screenshots/GIFs for UI changes.
Exact commands live in the core repository README and package scripts—check those out as the source of truth for the monorepo toolchain.
Docs contributions
When editing this site:
- Mirror content in src/content/docs/en-us/ and src/content/docs/pt-br/.
- Keep React and Vue examples in parity under src/examples/.
- Prefer CodeBlock / FrameworkContent / Playground for framework-specific snippets.
License
By contributing, you agree that your work will be available under the same MIT license as the project.
Related
- Project structure — package responsibilities
- Dual apps — why parity matters for product teams
- Overview — product strengths