Use Library when
You already know the exact component, section, or pattern you want to inspect.
Starter pages sit one level above bundles. They turn a sensible reference stack into an assembled layout that teams can review as a full product page before breaking it back down into individual parts.
You already know the exact component, section, or pattern you want to inspect.
You want a recommended stack of references for a use case like docs, dashboard, marketing, or workspace admin.
You want to see the assembled result as one page before deciding which references to keep, swap, or simplify.
Every starter page is tied to a bundle. Bundles explain the recommended stack. Starter pages show that stack as an assembled layout. Use both views together when you want planning and page context at the same time.
An assembled dashboard page that combines navigation, analytics, search, and data tables into one product-ready shell.
An assembled docs page with search, reference navigation, reading surfaces, and fallback states for larger content systems.
An assembled public-facing launch page that connects hero framing, pricing evaluation, signup, and footer conversion.
An assembled private workspace page that connects invite-based access, settings governance, and operational control surfaces.