@entropy-ui/data-views

Controlled React list, kanban, calendar, timeline, and multi-view database components.


License
MIT
Install
npm install @entropy-ui/data-views@0.1.0-next.3

Documentation

Entropy Data Views

Documentation and live examples · npm

@entropy-ui/data-views is a controlled React component library for showing the same records as a list, kanban board, calendar, or timeline. It also includes a Notion-inspired database shell with saved views and one composable toolbar.

The library owns view layout, interaction, accessibility, transient state, and optimistic presentation. Applications own records, fetching, persistence, permissions, domain forms, and conflict resolution.

The extraction and application migration are complete, and prerelease builds are public on npm. Stable promotion remains a release-owner action; see docs/RELEASE.md.

Workspace commands

pnpm install
pnpm check

Imports

import { DatabaseViews } from "@entropy-ui/data-views"
import { createBuiltInDataViewPlugins } from "@entropy-ui/data-views/adapters"
import { Calendar, CalendarProvider } from "@entropy-ui/data-views/calendar"
import { Kanban, KanbanProvider } from "@entropy-ui/data-views/kanban"
import { DataList, DataListProvider } from "@entropy-ui/data-views/list"
import { Timeline, TimelineProvider } from "@entropy-ui/data-views/timeline"
import "@entropy-ui/data-views/styles.css"

The compiled stylesheet is isolated to data-view roots. Tailwind v4 consumers can instead scan the package from their application stylesheet and use their existing shadcn theme directly; see docs/THEMING.md.

Architecture, ownership, persistence, forms, theming, SSR, migration, release process, verification, and API policy are documented under docs.

Documentation site

The public site is a workspace consumer under apps/docs. It imports only declared package exports and includes live database, list, kanban, calendar, and timeline examples.

pnpm docs:dev
pnpm docs:build
pnpm docs:preview

Merges to main deploy the production build to GitHub Pages after the CI workflow succeeds.