@sps-woodland/cards

SPS Woodland Design System card, insight card, and scrollable container components.

Heads up — this is a wrapper package. The component source now lives in @sps-woodland/core, split into three independent families: cards, insight-card, and scrollable-container. This package re-exports from all three so existing imports keep working, but new code should prefer the mono-package paths.

Why three families and not one?

The legacy @sps-woodland/cards wrapper bundled three semantically distinct things: layout cards (Card, CardHeader, CardFooter, CardTitle), data display widgets (InsightCard, InsightCardSet), and a layout utility (ScrollableContainer). They share no code. InsightCard's CSS alone is roughly 9× the size of the entire Card family combined. Splitting them lets a consumer who only needs Card ship just Card's styles, not InsightCard's.

Preferred imports (mono-package)

// Cards (layout container family)
import { Card, CardHeader, CardFooter, CardTitle } from "@sps-woodland/core/cards";
import "@sps-woodland/core/cards/style.css";

// Insight cards (data-display widget family — migrated to @sps-woodland/core)
import { InsightCard, InsightCardSet } from "@sps-woodland/core/insight-card";
import "@sps-woodland/core/insight-card/style.css";

// Scrollable container (layout utility)
import { ScrollableContainer } from "@sps-woodland/core/scrollable-container";
import "@sps-woodland/core/scrollable-container/style.css";

Card pieces also have their own flat subpaths if you only need one: @sps-woodland/core/card, /card-header, /card-footer, /card-title.

Legacy imports (still supported)

import {
  Card, CardHeader, CardFooter, CardTitle,
  InsightCard, InsightCardSet,
  ScrollableContainer,
} from "@sps-woodland/cards";
import "@sps-woodland/cards/style.css"; // concatenated bundle of all three