> For the complete documentation index, see [llms.txt](https://umber.gitbook.io/umber/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://umber.gitbook.io/umber/why-umber/just-in-time-experience.md).

# Just-in-Time Experience

Deploying an asset update traditionally means a slow, manual process: someone — usually a DevOps engineer — has to navigate folder structures, rename files consistently across environments, and coordinate the change with whoever owns the code that references it. It's easy to get wrong and hard to do quickly.

Umber removes that friction. Deploying a new version into any environment takes a few clicks in the dashboard (or one command via the [Umber CLI](/umber/cli-tools/umber-cli.md)) — with no filename changes and no code changes required on your end, because the delivery URL for an asset stays the same across versions. That also means rollbacks are just as fast: reverting to a previous version doesn't touch your codebase either.

The result is that non-engineers can safely own asset releases, and engineers stop being a bottleneck for what should be a content change, not a deploy.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://umber.gitbook.io/umber/why-umber/just-in-time-experience.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.