Surfaces/Operations/Kanban

Operations

Surface layer

KanbanSurface

Kanban

Kanban board page with lane managementOperations surfaces need to stay readable under live change, queue pressure, and multi-step decision making.

SummarySurface-owned framing, app-owned wiring, and runtime switching stay cleanly separated here.

Classic

Modern

Rustic

2 structures + 1 pattern

Runtime proofSidebar runtime switches should change the surface without page-local restyling.

Runtime

Platform

Rottay

Rottay / ModernPlatform Flagship

Primary

Radius

Density

Compact runtime evidence across 3+ token signals.

Composition

Recipe map and contract boundary

2 structures + 1 pattern

Surfaces are page recipes: structures hold the frame, patterns carry reusable tasks, and the app provides domain state, permissions, and routing.

Structures

CollectionHeader

SearchCommandBar

Patterns

PatternKanbanBoard

Boundary flow

Route and permissions gate access before the surface renders.

Surface config defines layout, actions, and data hooks for the page recipe.

Structures establish the page chrome and stable navigation frame.

Patterns fill the work area while product-owned logic stays outside the DS contract.

API and code

Import and usage contract

Kanban

Audit focus

real-time signal

queue priority

exception handling

Layer fit

Primitives

Patterns

Structures

Surfaces

ImportPublished package entrypoint, ready to copy.

tsx

1 line

Consumption

Runtime-aware snippet

ImportTSX

Quick copy

import { KanbanSurface } from '@rottay/design-system';

Usage contractPaste-ready example that shows the base contract first.

tsx

11 lines

Consumption

Runtime-aware snippet

Usage contractTSX

Quick copy

import { KanbanSurface } from '@rottay/design-system';

<KanbanSurface
  config={{
    title: 'Your page title',
    dataSource,
    actions,
    permissions,
    routing,
  }}
/>