Source-backed docs for SDKs, APIs, storefront UI, search, commerce operations, media systems, and AI agents. Start with the job you need to finish, then follow the generated artifact that owns exact package, API, and runtime truth.
If you need the model before you choose a surface, start with How Enad works or browse the shared vocabulary in Start concepts. The surface cards below are still the fastest path once you know which job you are doing.
Each path points to the docs surface that should own your next decision. Use generated references and package artifacts for exact SDK and API facts.
Move from SDK shell to theme handoff to search once the storefront shape is clear.
Start the provider, storefront shell, and component building blocks.
Carry a playground theme into runtime without losing component-set intent.
Plan search context, facets, and autocomplete before wiring storefront flows.
Choose the owning API surface first, then drill into the exact reference it publishes.
Pick Management, Shopper, Auth, DAM, or Search before writing requests.
Trace shopper flows back to the API boundary that owns the data.
Route image, DAM, file, and video work to the right media source.
Use current event docs, generated reference, and AI-facing context when exact truth matters.
Start with the live event and integration boundary before wiring automation.
Check the generated endpoint and schema evidence when behavior must be exact.
Give agents canonical docs, manifests, and prompt-safe guidance.
Docs organizes Enad docs by product surface and source boundary. Package facts come from
enad-packages; API facts come from generated OpenAPI or schema artifacts; the live
playground remains the runtime lab for theme editing, visual examples, and export flows.