github marigold-ui/marigold @marigold/cli@0.3.0

latest releases: @marigold/components@17.8.0, @marigold/system@17.8.0, @marigold/theme-rui@5.4.1...
9 hours ago

Minor Changes

  • 7877bc6: feat(DST-1421): marigold examples commands to expose application patterns

    Adds marigold examples list and marigold examples get <slug> so AI agents (and humans) can discover and retrieve Marigold's application-level reference patterns from the terminal, mirroring the library-first architecture of the docs/list commands.

    • CLI: new listExamples() / getExample(slug) library functions and a examples command wrapping them, with --format markdown|json|plain, --fresh and --offline (reusing the existing cache layer). Tab completion and telemetry are extended to cover the new command and example slugs.
    • Docs: a new build-examples.mjs registry step emits public/mcp/examples.json and public/mcp/examples/<slug>.json from colocated *.marigold-pattern.yaml sidecars. Examples are discovered by sidecar presence (App-Shell placeholder pages are excluded automatically), and a malformed sidecar fails the build. Sidecars ship for the filter, form and inventory examples.
    • A global framework-transformation note (marigold docs getting-started/examples-for-agents) documents porting examples from the Next.js App Router to other frameworks (Vite, etc.) once, rather than per example.
  • d84dfeb: feat(DST-1445): surface non-component docs pages in the CLI

    marigold docs <name-or-slug> now resolves any docs page, not just components — Foundations, Patterns, and Getting-Started pages are reachable by slug (docs foundations/accessibility) or name (docs installation). Full slugs route by prefix (components/… to a component, otherwise a page); bare names try components first and fall back to pages.

    marigold list now also lists those pages, grouped under Foundations, Patterns, and Getting Started headings, and accepts --category foundations|patterns|getting-started (the top-level segment, so --category patterns returns every pattern page). The --format json payload gains an additive top-level pages array ({ title, slug, category, description }); the existing categories shape is unchanged. Shell completion now suggests page slugs for docs and page categories for --category.

    The package README was updated to document the new page support: the docs command reference now covers slugs and page categories, and the list reference reflects that pages are listed and searchable alongside components.

    Note: the internal getComponentDocs / ComponentDocs exports were renamed to getPageDocs / PageDocs.

Don't miss a new marigold release

NewReleases is sending notifications on new releases.