Start

# Start Use this page when you are new to the docs, returning after a break, or deciding which Enad surface owns the next step. The fastest path is to choose the job you are doing, then follow the route that owns that track. > Start pages route you to the right source. Exact SDK exports, component props, API fields, request shapes, response shapes, Search operations, event payloads, and generated types remain owned by package artifacts, OpenAPI, Search artifacts, event catalogs, and source repositories. ## New to Enad? If you want the mental model before you choose a surface, start here: - [How Enad works](/start/how-enad-works) for the short plain-English overview. - [Start concepts](/start/concepts) for the shared vocabulary and reading order. Once the model is clear, come back to this page and choose the surface that owns your next technical step. ## First-run path 1. **Pick the surface**: storefront UI, TypeScript SDK, API, Search, Media, Events, AI docs, or playground. 2. **Open the current track page** for that surface. 3. **Check the version or source boundary** before copying code or asking an agent to make changes. 4. **Use generated or source-owned artifacts** when exact fields, exports, schemas, or payloads matter. 5. **Use troubleshooting** when a provider, API, Search, theme, or AI-docs path does not behave as expected. ## Where to start | I want to... | Start here | Use this route for | Source-truth boundary | | --- | --- | --- | --- | | Build storefront UI with React components | [React SDK latest](/react-sdk/latest) | Component families, provider boundaries, storefront composition, theming entry points | Package artifacts and `enad-packages` own exports, props, hooks, and runtime behavior | | Install or wire the React SDK for the first time | [React SDK setup](/react-sdk/latest/setup) | Setup order, app shell placement, stylesheet/provider checks | Package artifacts and source own exact imports and runtime contracts | | Add login, signup, password reset, sign-out, or current-user UI in React | [Account and auth UI](/react-sdk/latest/guides/account-and-auth-ui) | React account surface, `client/user` routing, and app-owned auth boundaries | Package artifacts own exact React exports and hook shape; Auth API/OpenAPI owns request and response truth | | Use Enad from a TypeScript or server runtime | [TypeScript SDK latest](/ts-sdk/latest) | SDK entry point, API client direction, Search package boundary | Package artifacts own exact exports, methods, generated types, and version facts | | Add product search, facets, autocomplete, or product lookup | [Search latest](/search/latest) | Search GraphQL guidance, app-scoped context, generated document boundaries | Search schema/artifacts and package-generated documents own operation and field truth | | Decide which REST API family to use | [APIs](/apis) | Management, Shopper, Auth, and DAM family routing | OpenAPI/generated reference artifacts own endpoint, parameter, and response truth | | Look up generated reference surfaces | [Reference](/reference) | Generated endpoint/reference routes as they land | Generated reference, OpenAPI, and source artifacts own exact contract truth | | Work with images, assets, DAM, or media delivery | [Media](/media) | Media overview and DAM API routing | DAM/OpenAPI artifacts and source systems own exact asset API behavior | | Understand event surfaces or integration signals | [Events](/events) | Event track entry point and current event guidance | Canonical event catalogs or source systems own event names and payload truth | | Give an AI agent safe Enad context | [AI Docs](/ai) | llms routes, manifest, prompt routing, source-boundary guidance | AI docs route agents; package/API/Search/event artifacts still own exact facts | | Try flows in a live sandbox | [Playground](/playground) | Runtime experimentation and theme/playground handoff | The live playground owns sandbox behavior; docs explain how to use it safely | | Recover from a broken setup or confusing docs path | [Troubleshooting](/start/troubleshooting) | Symptom-based recovery paths and source-of-truth order | Troubleshooting is guidance only; verify exact contracts in owning artifacts | ## Good defaults - **Starting new storefront work?** Open [React SDK latest](/react-sdk/latest), then [React SDK setup](/react-sdk/latest/setup). - **Need customer login or account UI in that storefront?** Open [Account and auth UI](/react-sdk/latest/guides/account-and-auth-ui) after setup and runtime adapters are in place. - **Calling Enad from backend code?** Open [TypeScript SDK latest](/ts-sdk/latest), then [APIs](/apis) or [Search latest](/search/latest) depending on the job. - **Looking for endpoint details?** Start at [APIs](/apis), then move to [Reference](/reference) or the relevant OpenAPI-backed route. - **Working with Search GraphQL?** Start at [Search latest](/search/latest). Use generated Search artifacts when fields, variables, fragments, or generated types matter. - **Helping an AI agent?** Start at [AI Docs](/ai), then provide the agent with `/llms.txt`, `/llms-full.txt`, or `/ai/manifest.json` as appropriate. ## Version and source model Docs-v3 does not have one global version. Each package or API track moves on its own: - React SDK and TypeScript SDK pages follow their package tracks. - API pages follow their API family or generated spec track. - Search pages follow the Search GraphQL/source-artifact track. - Event pages should defer to the canonical event catalog when exact payloads matter. - AI docs and llms outputs route agents to safe docs surfaces; they do not replace package, API, Search, or event artifacts. See [Versioning](/start/versioning) for the full model. ## Coverage and migration inventory Use [Current docs parity inventory](/start/current-docs-parity) to understand what the docs migration tracks from the public docs corpus, generated references, route maps, and playground inventory. It is a coverage and routing aid, not a replacement for the live source of truth.