Support
We offer support through our GitHub issue tracker. Please file bugs or information requests. We also have comprehensive documentation, all of which is available through our MCP server.
What makes a good bug report
The more precisely you can describe the problem, the sooner we can reproduce it — and a bug we can reproduce is a bug we can fix. A good report includes:
- What you did — the steps to trigger it, ideally as a short, self-contained example. The live demo on any component's page is an easy place to build one.
- What you expected to happen, and what actually happened instead.
- Which component and version you were using, and which framework — plain web components, React, or Blazor.
- Your environment — browser and operating system. Rendering bugs in particular often live in one engine and not the others.
- Screenshots or a short recording when the problem is visual.
Leave out anything you cannot share, but the shape above gets us moving quickly.
Where the docs live
Most questions are answered in the documentation you are reading now:
- Get started — install, register, and theme in a few lines
- Browse the components — all 58, each rendered live
- Theming overview — how one seed color becomes a whole theme
If the docs do not answer your question, that is itself worth an issue — a gap in the documentation is a bug too.