Skip to main content

Blocks Pro

Blocks are the bigger pieces of an app: a kanban board, a calendar, a pricing table. Each is one component with props for the simple case and render props for the rest. They're built on patine-ui, so they follow your theme and design and work with a keyboard and a screen reader. They animate only through the library's motion, so they're still when the OS asks to reduce motion.

import { Kanban, EventCalendar, PricingTable } from '@patine-ui/pro';
BlockWhat it's for
Stats rowA dashboard's key figures with their change and trend; tiles can switch a chart
TimelineEvents along a line: a history, a shipment, an incident
Activity feedWho did what, newest first, by day, with filters and unread dots
Order trackerWhere an order is, with the carrier's scans
WizardA task in steps, with validation and a finish
Pricing tablePlans as cards, a comparison table or a phone paywall list
Product cardA product in a grid, with swatches, wishlist and Add to cart
Review listCustomer reviews with their summary, filters and Helpful votes
KanbanColumns of cards to drag, with WIP limits and a Move to menu
AgendaThe days ahead as a list under a week strip
Event calendarEvents by month, week or day
GanttA project's tasks on a timeline, dragged to reschedule
AI usage meterTokens or credits used against the plan's limit
Agent activityWhat an AI agent is doing, step by step
Approval cardAn assistant's change, held until the person approves it
Onboarding, Sign in, Paywall, Settings, Profile, CheckoutWhole single screens, each built from free components. For whole apps, see the templates

What every block shares​

  • design and theme: the look of the provider, or the block's own.
  • density: 'compact', 'comfortable' (default) or 'spacious'.
  • animate: entries fade and rise in, changes glide; off with reduce motion or animate={false}.
  • loading, error with onRetry, emptyTitle, emptyDescription and renderEmpty: a skeleton of the content, a calm error with Try again, or a helpful empty state.
  • Controlled or not: state like the selected tile or the current step takes value and onValueChange (or defaultValue), and callbacks fire only for what the user does.
  • labels: every word they show, for your language. Layouts use start and end, so they mirror in right-to-left languages.
  • accessibilityLabel, style and testID.