# Development of plugins 🧩

Dashboard has an open technology where plugins make up the environment with features in dashboard. Below you find the documentation on how to create plugins to Dashboard. To create a plugin, you need to develope several parts to get a complete plugin. What you see in your Dashboard window on your desktop is most often just the app-part of the plugin but there other parts to make it a functional plugin.

A plugin can in short be described as a built up by several pieces:

1. The mid part symbolizes  the Plugin it self.
2. The piece to the left is the Application that gives View and Presentation you see in Dashboard browser window.
3. Piece that manage plugin Health and display and report health parameters.
4. Agent that manage the Data and communication layer.
5. On top there is a widget piece which makes enrichments to the plugin possible.&#x20;

![](https://3968093108-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LyYD3O_ZPKPSQ4A9j7i%2F-M1Ui6OKee6f2ncQAbNw%2F-M1Ul75LQtJt_9YOpAoc%2FScreenshot%202020-03-03%20at%2010.40.06.png?alt=media\&token=098aba24-629f-4171-9d50-8deafdbf23ba)

Want to just dive deeper into the [anatomy of a plugin](https://docs.infomaker.io/dashboard-plugin/the-anatomy-of-a-plugin) -> which is the first part in the [book about plugin development.](https://docs.infomaker.io/dashboard-plugin/)

{% embed url="<https://docs.infomaker.io/dashboard-plugin/>" %}


---

# Agent Instructions: 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.navigaglobal.com/naviga-dashboard-overview/dashboard-5.4/develop-your-plugins.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.
