> For the complete documentation index, see [llms.txt](https://docs.theopenpresenter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theopenpresenter.com/scratch-pad/ambition.md).

# Ambition

**Server as a local app**

Alternatively, the server is also available as a local app. This is the preferred method for locations with unreliable or no internet connection.

In this configuration, you can download and install an app that will handle everything, just like how other presentation software is designed.

\
**3a. Browser rendering**

Browser rendering is the default rendering method. It is the simplest and the recommended way for anything simple.

**Media cache**

Since rendering is done in this part, we use media cache to ensure smooth media playback and transition. If there are multiple renderer connected, each of them will need a cache of their own.

**3b. Server rendering**

Server rendering renders the final picture in the server. This is required if we want an output in a specific format.\
For example: Video stream like NDI/SDI/HDMI/RTSP and the like.

The benefit is that there won't need to be a client. Or at least it can be a very simple client.


---

# 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:

```
GET https://docs.theopenpresenter.com/scratch-pad/ambition.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.