Start here when you are new to the docs, returning after a break, or deciding where to work next. The fastest path is to choose the job you are doing, then follow the route for that track.

Start pages help you choose the right route. When exact SDK exports, component props, API fields, request shapes, response shapes, Search operations, event payloads, or generated types matter, open the package, OpenAPI, Search, event, or reference page for that work.

New to Enad?

If you want the mental model before you choose a surface, start here:

• How Enad works for the short plain-English overview.
• 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, agent guides, or playground.
2. Open the current track page for that surface.
3. Check the version and exact reference route before copying code or asking an agent to make changes.
4. Use package, API, Search, or event reference pages when exact fields, exports, schemas, or payloads matter.
5. Use troubleshooting when a provider, API, Search, theme, or agent-file path does not behave as expected.

Where to start

Build storefront UI with React components from React SDK latest. Use it for component families, provider boundaries, storefront composition, and theming entry points; exact details live in React SDK reference pages and package reference.

Install or wire the React SDK from React SDK setup. Use it for setup order, app shell placement, stylesheet imports, and provider checks.

Add login, signup, password reset, sign-out, or current-user UI from Account and auth UI. Use React SDK reference plus Auth API/OpenAPI when exact contracts matter.

Call Enad from a TypeScript or server runtime with TypeScript SDK latest. Use API reference pages or Search reference when exact request and query details matter.

Add product search, facets, autocomplete, or product lookup from Search latest. Search GraphQL reference and package reference own exact fields, variables, fragments, and generated types.

Choose a REST API from APIs, then open Reference for endpoint, schema, OpenAPI, and Search GraphQL reference routes.

Work with images, assets, DAM, or media delivery from Media. Use DAM/OpenAPI reference pages and media guides for exact behavior.

Understand events from Events, give agents context from Agent guides, try runtime flows in Playground, and recover from setup problems in Troubleshooting.

Good defaults

For new storefront work, open React SDK latest, then React SDK setup.

For customer login or account UI, open Account and auth UI after setup and runtime adapters are in place.

For backend TypeScript work, open TypeScript SDK latest, then APIs or Search latest depending on the job.

For endpoint details, start at APIs, then move to Reference or the relevant OpenAPI-backed route.

For Search GraphQL, start at Search latest. Use the Search GraphQL reference when fields, variables, fragments, or generated types matter.

For agent guidance, start at Agent guides, then provide /llms.txt, /llms-full.txt, or /ai/manifest.json as appropriate.

Version model

Enad docs do 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 or OpenAPI track.
• Search pages follow the Search GraphQL track.
• Event pages should defer to the event catalog when exact payloads matter.
• Agent files route agents to safe docs; they do not replace package, API, Search, or event reference pages.

See Versioning for the full model.