From a531a1709eaa5904f4ec9acac6f387a1d888f5c8 Mon Sep 17 00:00:00 2001 From: bergquist Date: Thu, 24 Mar 2016 11:55:36 +0100 Subject: [PATCH] docs(plugin): add apps page --- docs/mkdocs.yml | 1 + docs/sources/plugins/developing_plugins.md | 5 +++++ 2 files changed, 6 insertions(+) diff --git a/docs/mkdocs.yml b/docs/mkdocs.yml index b527fa8f046..1ecefe85c68 100644 --- a/docs/mkdocs.yml +++ b/docs/mkdocs.yml @@ -88,6 +88,7 @@ pages: - ['plugins/overview.md', 'Plugins', 'Overview'] - ['plugins/installation.md', 'Plugins', 'Installation'] +- ['plugins/app.md', 'Plugins', 'App plugins'] - ['plugins/datasources.md', 'Plugins', 'Datasource plugins'] - ['plugins/panels.md', 'Plugins', 'Panel plugins'] - ['plugins/development.md', 'Plugins', 'Plugin development'] diff --git a/docs/sources/plugins/developing_plugins.md b/docs/sources/plugins/developing_plugins.md index c78bd45c0e4..def5b825df9 100644 --- a/docs/sources/plugins/developing_plugins.md +++ b/docs/sources/plugins/developing_plugins.md @@ -24,6 +24,11 @@ You can use any build system you like that support systemjs. All the built conte All our example plugins have build scripted configured. +## module.(js|ts) + +This is the entry point for every plugin. This is the place where you should export your plugin implementation. Depending on what kind of plugin you are developing you will be expected to export different things. You can find whats expected for [datasource](http://docs.grafana.org/v3.0/plugins/datasources/), [panels](http://docs.grafana.org/v3.0/plugins/panels/) and [apps](http://docs.grafana.org/v3.0/plugins/app/) +plugins in the documentation. + ## Start developing your plugin There are two ways that you can start developing a Grafana plugin. 1. Setup a Grafana development environment. [(described here)](https://github.com/grafana/grafana/blob/master/DEVELOPMENT.md) and place your plugin in the ```data/plugins``` folder.