Components
Each one is source you copy into your app, not a package you depend on. Pick a component to see it running, read how it is put together, and take it.
- JSON Schema builderDrag a field to any depth, select ten and move them together, add your own types. Four presets over one set of parts, and the keywords it has no UI for survive the round trip untouched.
- Rich inputA run matching a pattern you declared becomes one object: the caret steps over it and Backspace takes the whole thing. The value underneath stays a plain string.
- Rich textareaEverything the rich input does, with newlines. Enter breaks a line instead of doing nothing, and the value keeps them.
Every page reads the same way
Component pages are not written freehand. They are rendered from one shape, so the section you want is where it was on the last page you read, and a page cannot quietly drop Installation or invent a heading of its own.
- 1Example the component running, with the file behind it one click away.
- 2Installation the CLI command, and the manual copy for when you want it.
- 3Usage the imports and the smallest thing that works.
- 4Composition the element tree: what you write inside what.
- 5Examples one running demo per idea, each with its own file.
- 6API reference the whole surface, as a signature.
Every Code tab holds the example's whole file, read from disk at build, with the import path rewritten to where the CLI puts it. Nothing on these pages is a snippet typed out beside the thing it claims to show.