> 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/introduction/server-communication.md).

# Server Communication

As previously described in [System Architecture](/introduction/system-architecture.md), TheOpenPresenter consists of three main frontend applications that users interact with.

### Next.js

The Next.js application communicates with the server primarily through GraphQL, which is powered by [Postgraphile](https://postgraphile.org/). This automatically generates the GraphQL schema directly from our PostgreSQL database. As a result, much of the business logic for user, project, and organization management resides within the database itself.

### Remote/Renderer

While both the Remote and Renderer applications use GraphQL endpoints to fetch certain data, they employ a separate mechanism for project synchronization using Yjs. 

Each plugin maintains its own state within a Yjs document. The Remote interface is used to modify this state, while the Renderer displays output based on the current state.

#### Reactivity

The Renderer operates on reactive programming principles - meaning its display updates automatically in response to changes in the plugin's state. If you're familiar with frameworks like React, this concept will be familiar: the UI is a direct reflection of the current state.

While this approach provides predictability and consistency, it also comes with typical reactive programming considerations. For example, implementing smooth animations and transitions requires careful planning since all changes are state-driven rather than directly manipulated.


---

# 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/introduction/server-communication.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.