Playground
Connect implementation guidance with the live SDK sandbox.
Open the live SDK sandbox at sdk.enad.io/sandbox.
Use this route to move from implementation guidance into the live playground. The docs explain setup, route boundaries, and stable guidance. The playground gives you a browser runtime for trying SDK behavior before you move that setup into an app.
Use the live playground for runtime work
The playground is the right place to experiment with SDK components in a running browser. Use it to preview component variants, tune theme state, export the reviewed result, and sandbox live-data behavior before wiring app-owned sources.
Treat playground output as a handoff into your app, not as a source of consumer-app internals. Copy documented setup patterns from these docs, then use the playground to validate the runtime result.
Use docs for implementation guidance
Use these docs to find setup guides for providers, stylesheets, theming, and Search context. They also cover Storyblok storefront boundaries, curated React SDK examples, and runtime-route pointers.
Use docs routes when you need stable references for plans, PRs, support notes, Agent guides, or Agent files such as /llms.txt, /llms-full.txt, and /ai/manifest.json.
Consumer apps should follow the package docs and reference pages for public imports, provider placement, props, and integration boundaries. The playground can prove a setup works, but the package and reference pages own exact contracts.
Stable routes
- Start with React SDK setup when wiring a new app shell.
- Use React SDK theming for provider boundaries, theme hashes, and component-set guidance.
- Follow Restore a theme from the playground when moving an exported playground theme into an app.
- Read Storyblok storefront bridge when Storyblok-authored storefront content needs the public React SDK surface.
- Use React SDK examples for curated Storybook, sandbox, and showcase starting points.
- Read React SDK playground for the React SDK-specific docs and playground boundary.
- Visit Agent guides for route guidance.
- Use Agent files when a tool needs
/llms.txt,/llms-full.txt, or/ai/manifest.jsonexplained. - Use React SDK agent theme and icons when theme export, provider nesting, or runtime icon boundaries are the real question.