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

# Publishing

Publish to any channel or presentation layer. The Writer is part of a Publishing Universe. The Universe has its parts represented in the image below as circles for different applications and services.

Starting from the left the **Writer** is the authoring environment where content is created. The circle **Dashboard** is an interface for integration of smart functions on your desktop, that give a complete environment for publishing. Writer can be run as an app in Dashboard and in that setup you get the Writer surrounded by smart Dashboard apps, such as article search, planning tools, wire and image services.

The content repository **Open Content**, serves as publishing engine and as storage. It has two separte circles. The first is the editorial content and the other represents the part of your contenty that will be published, ie **Public.** The Presention part of the Universe gives possiblities to have Mobile, [Web](https://docs.infomaker.io/everyware) and E-editions (Replica) output from the same content. The Replica is normally based on a traditional printsystem, which can have the Writer as the authoring tool (see the second image).

![](/files/-Llpq0HRSpXETilAgN0g)

Adding more details to the description of the parts that can be connected to Writer, Dashboard and Open Content, there are tools for planning and publishing overviews, they are called **Newsroom Planner** and **Publication Planner**. There are also administrative tools for Metadata and concepts for Metadata.

![](/files/-MU7ZTLbaLvUsjpcuGmF)

## Print integration

Intergrations are most often very customer-specific and as you see in the circles in the bottom to the left, there are integrations to [Newspilot](https://wiki.infomaker.se/display/NPM42SVE/Newspilot+Digital+Writer) or [NCS Content](https://docs.infomaker.io/ncs-content-integration).

## Engagement

Naviga's user engagement tools are connected to the presentation's layer to engage and manage what type of content that different user (ie readers or watchers of published content) are presented with at different circumstances and behaviour. The engagement tools can be combined with Naviga subscription solutions as well as the steps that may exist before subscribing. If you are interested in the Naviga Engagement solution, follow [this link](https://navigaglobal.com/solutions/enrich/naviga-engage/) for more information.


---

# 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://docs.navigaglobal.com/writer/introduction/publishing.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.