Blog
# Blog
Use the blog for practical implementation notes that sit beside the reference pages. Posts should help you choose a surface, understand a tradeoff, or approach a common build path without replacing exact SDK, API, Search, Media, Event, or integration reference pages.
## Latest
Start with [Choosing the right Enad surface](/blog/choosing-the-right-enad-surface) when a task could belong in more than one route family.
Keep [Start](/start), [APIs](/apis), [Reference](/reference), and [Agent guides](/ai) nearby while you decide whether the work belongs in an SDK, API, Search, Media, Events, playground, or agent-guided route.
## What belongs here
- Implementation walkthroughs that connect concepts, SDK pages, and reference pages.
- Release context that helps you understand a product or API change.
- Surface-selection guidance for storefront, backend, Search, Media, Event, and agent-assisted work.
- Agent-facing usage notes that make Enad context easier to give to coding agents.
## What does not belong here
- Endpoint fields, response shapes, enum values, auth behavior, or status-code contracts.
- SDK exports, props, hooks, generated types, package versions, or runtime behavior.
- Event payload facts, webhook schemas, or Search operation shapes that need exact reference pages.
Use [Start](/start), [Reference](/reference), [Agent guides](/ai), or the relevant route family when you need exact documentation instead of learning context.
DocsDocsBlog