> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/dashboard-plugin/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/dashboard-plugin/getting-started.md).

# Getting started

Dashboard Plugin starter KIT repo on Bitbucket:

{% embed url="<https://bitbucket.org/infomaker/dashboard-plugin/src/master>" %}

This guide will teach you how to build a plugin with an application, agent and widget. Also how to communicate between them and fetching external data.

Before you get started you should read **The anatomy of a plugin** and have understanding of a plugins life cycle.

{% content-ref url="/pages/-LbTZcLptPfj4R4Vu2nh" %}
[The anatomy of a plugin](/dashboard-plugin/the-anatomy-of-a-plugin.md)
{% endcontent-ref %}

#### Introduction

Our scenario is to build a plugin that fetches data from [Krisinformation (SE)](https://www.krisinformation.se/om-krisinformation.se/oppen-data) and displays it in a list with a details view in a modal, we also want to refresh the data on a, by user, selected interval. To let the user know when the latest update was we put that info in a widget. The data should be cached and persisted between users.

#### Prerequisites

* Git
* NodeJS

We also need to get the [Dashboard Developer Plugin](https://bitbucket.org/infomaker/dashboard-plugin). Follow the install instructions in the `README.md`


---

# 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.navigaglobal.com/dashboard-plugin/getting-started.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.