Files
Oleg Isonen d6c1a3c763 fix: Show one Alert styling target in Markdown Embed (#6411)
Markdown Embed currently adds one general Alert descendant plus five
variant-specific descendants. This shows six Alert entries in the
Navigator even though they represent one element type.

This keeps one Alert descendant. Note, tip, important, warning, and
caution still render normally and retain their state-specific default
backgrounds.

Ref #6278

## Implementation

- Remove the five variant-specific Alert descendants from the Markdown
Embed template.
- Keep the shared Alert descendant and its `data-state` style rules.
- Add a regression test for the single Alert styling target.

## Checklist

- [x] Reproduce the six Alert descendants in a failing test.
- [x] Keep one Alert descendant.
- [x] Preserve default styles for all five variants.
- [x] Run the SDK components test suite.
- [x] Run SDK components typecheck and declaration generation.
- [x] Run repository lint.
- [x] Review documentation impact: no documentation change is needed
because Markdown syntax and rendered behavior are unchanged.
- [x] Review fixture impact: no fixture inputs or generated fixture
bundles are affected.
2026-09-18 11:14:59 +02:00
..

Webstudio SDK Components

Webstudio SDK is a TypeScript API that lets you use your Webstudio project or some components in your custom codebase or just render a complete Remix Document.

Component Registry Metadata

Webstudio component discovery uses a shadcn-compatible registry item shape with Webstudio-specific metadata stored in meta. The top-level registry fields stay compatible with shadcn conventions, while meta.runtime, meta.authoring, and meta.builder describe Webstudio component ids, props, content models, templates, insertion rules, and Builder/MCP guidance.

This package is not published as an installable shadcn registry yet; the shape is used internally by Builder and MCP discovery.