Surfaces/Admin/Integration

Admin

Surface layer

IntegrationSurface

Integration

Third-party integration catalog and configurationAdmin surfaces should prove that dense back-office screens can still feel calm, legible, and trustworthy.

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

Classic

Modern

Rustic

1 structure + 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

1 structure + 1 pattern

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

Structures

Page-level scaffolding

Patterns

Pattern-specific widgets

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

Integration

Audit focus

permission-aware actions

operational density

clear recovery paths

Layer fit

Primitives

Patterns

Structures

Surfaces

ImportPublished package entrypoint, ready to copy.

tsx

1 line

Consumption

Runtime-aware snippet

ImportTSX

Quick copy

import { IntegrationSurface } 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 { IntegrationSurface } from '@rottay/design-system';

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