Contact
How to reach me — and what to include so I can actually help
Start here
Opensource UI is still in an early, hands-on phase. I maintain the site, ship components, answer mail, and handle sponsorships myself. That is why this page points at my personal inbox instead of some faceless support bot — one person reads the thread and replies.
I am streamlining how people reach out so messages do not pile up as vague "hi I want to contribute" notes with no context. Tell me what you need, give enough detail, and I can answer faster.
Ways to connect
- Site: opensourceui.in
- GitHub: github.com/bidyut10/opensourceui
- Portfolio: bidyut.cc
- Twitter/X: @BidyutKundu12
- Email: Click to copy
Click the address to copy it — paste into your mail app when you write.
Why personal email
There is no support desk behind Opensource UI yet. Early on I tried to keep everything simple: ship components, keep the MIT license clear, and stay reachable without building a ticket system I cannot staff. So mail comes to me — Bidyut Kundu — at Click to copy.
That also means reply time is not instant. Nights and weekends get most of the attention. If your message is clear, I can usually get back within a few days. Please skip marketing blasts and cold sales pitches; I ignore those.
Support questions
Stuck copying a component, confused by a prop, or unsure how something should look in your app? Email me. Include:
- The component name or page URL (for example /components/phone)
- What you expected vs what happened
- Framework (React / Next.js) and roughly which Tailwind setup you use
- Short snippet or screenshot if it helps
I cannot debug every private codebase end-to-end, but I will help you understand how the piece is meant to work and where to look next.
Sponsorships and brand placement
Plans and checkout live on the sponsor page. After you pay, email your brand assets so I can publish the placement. Say which tier you bought (Silver, Gold, or Platinum) and attach what that tier needs — name, link, short line, logo.
Questions before you buy — invoice needs, logo sizes, wording on the docs card — same inbox. Subject line tip: start with "Sponsor:" so I can spot it quickly.
Found a bug or issue
Prefer GitHub when something is broken in the library or the site. Open an issue on the issues list or start a new issue.
Useful reports include:
- Steps to reproduce
- What you saw vs what you expected
- Browser or environment notes if it matters
- Component slug or file path if you know it
If you already have a fix, skip straight to a pull request (next section). If you only have a report, an issue is enough — do not email a huge dump unless GitHub is blocked for you.
Pull requests
Fixes and small improvements are welcome. Before you open a PR, check existing pull requests and related issues so we do not double work.
Please follow this shape:
- Fork the repo and branch from the default branch
- Keep the change focused — one problem per PR when you can
- Match the project design rules (neutral stage, no purple chrome, base + md: only, no sm:)
- Describe what changed and why in the PR body
- Link the issue if there is one
Huge drive-by refactors or new components with no prior conversation are harder to review. If the change is large, email or open an issue first so we agree on direction.
Want to contribute
See CONTRIBUTING.md on GitHub for local setup and PR basics. Contribution paths are still being shaped in practice — docs, components, design polish, triage. I would rather align first than get a vague "I just want to contribute" message with no scope.
Do not send only "I want to contribute." Tell me what kind of help you mean, for example:
- New component idea (what it does, where it would live)
- Bug fix or accessibility pass on an existing piece
- Docs or copy improvements
- Design review / visual QA
- Something else — name it
In that first email, include:
- Which contribution type from the list above
- One-paragraph proposal — scope, not a novel
- Your GitHub username
- Rough timeline if you have one
- Any constraints (time, stack comfort)
Write to Click to copy with subject "Opensource UI contribution". I will reply with whether it fits right now, and the next step (issue, branch, or wait). Random drive-by PRs without that context may sit longer or get closed with a note to email first.
Related
Story and roadmap vibes: About. Hiring reality check: Careers. Legal: Terms and Privacy.
