Skip to main content
Presentation context is the information available when Presenton interprets an editing request. Depending on the workflow, it can include the current deck, source material, outline, and recent instructions. Diagram showing the current deck, source material, outline, and user request feeding editing context, which produces a proposed update Context helps with follow-up instructions such as “make this slide more concise” or “use the same tone in the next section.” It is not a guarantee that every earlier detail will be recalled or preserved.

​
Write an actionable edit request

Use this pattern:

​
Protect important information

  • Repeat exact facts that must survive an edit.
  • Name the slide, section, or element being changed.
  • Point to the relevant source when the request depends on it.
  • Split unrelated changes into separate requests.
  • Review the visible result after every AI-assisted edit.
Treat the saved presentation—not assumed model memory—as the record of the current deck. If a detail matters, make it explicit in the request and verify it afterward.

​
Context and persistence

Cloud manages application storage for the hosted workflow. In a self-hosted deployment, keep /app_data persistent so presentations, uploads, generated assets, settings, and local application state survive container replacement.

Storage and processing

Configure persistence for a self-hosted deployment.