v1.0
Registry / Page 03·01

Registry introduction

Composable Flexiboards components, copied into your project and styled by your shadcn theme.

The registry provides styled Svelte components built on the Flexiboards primitives. The CLI copies them into your app, where you can edit the source. They use your existing shadcn theme.

Start here for installation details, then choose a component below.

Components

ComponentUse it for
DashboardFree-form tiles with headers, content, grabbers, and resizers.
Sortable ListReorderable rows with any content you need.
BoardCustom layouts and multiple targets on one board.
GrabberA themed drag handle for any widget.
ResizerA themed resize handle for any resizable widget.

Each page has a working preview, source example, installation command, and API notes. The docs framework menu selects the API and examples throughout.

Motion

Boards, dashboards, and sortable lists animate movement by default and respect reduced motion. Compare CSS and spring presets, or disable transitions through the existing configuration.

Composition

Families use namespace imports: Dashboard.Root, Dashboard.Item, Dashboard.Header, and so on. You control the content and decide where handles belong. The wrappers preserve the underlying configuration and controller APIs.

Compose the components around your application’s content, navigation, and actions.

Your theme, your source

Start with a Tailwind project configured for shadcn-svelte, including its theme variables and cn utility.

The CLI copies source and resolves the required framework adapter, icons, and utility.

Surfaces inherit card, card-foreground, border, and muted; handles inherit accent and ring. Your existing light and dark theme applies automatically. No fonts, global CSS, or color variables are overwritten.

Use class to adjust the defaults. Widget class functions can respond to controller state, and consumer classes are merged last. For deeper changes, edit the installed source.

Registry endpoints

The registry index lists the installable items.

flexi-handles remains available as a combined grabber/resizer install, and the old convenience sortable list API is retained.

The registry is currently unversioned. Review source diffs before asking the CLI to overwrite an existing installation; copied files do not update automatically with npm package upgrades.

Two meanings of registry

This source registry is separate from FlexiBoard.config.registry. The latter maps widget types to renderers when restoring saved layouts. The installed components can be used in those renderers, but installing them does not register persisted widget types for you.