+
+## Enabling app plugins
+After installing an app it have to be enabled before it show up as an datasource or panel. You can do that on the app page in the config tab.
+
+## README.md
+
+The readme file in the mounted folder will show up in the overview tab on the app page.
+
+## Module exports
+```javascript
+export {
+ ExampleAppConfigCtrl as ConfigCtrl,
+ StreamPageCtrl,
+ LogsPageCtrl
+};
+```
+The only required export is the ConfigCtrl. Both StreamPageCtrl and LogsPageCtrl are custom pages defined in plugin.json
+
+## Custom pages
+Custom pages are defined in the plugin.json like this.
+```json
+"pages": [
+ { "name": "Live stream", "component": "StreamPageCtrl", "role": "Editor"},
+ { "name": "Log view", "component": "LogsPageCtrl", "role": "Viewer"}
+]
+```
+The component field have to match one of the components exported in the module.js in the root of the plugin.
+
+## Bundled plugins
+
+When Grafana starts it will scan all directories within an app plugin and load folders containing a plugin.json as an plugin.
diff --git a/docs/sources/plugins/datasources.md b/docs/sources/plugins/datasources.md
index 6bd11242f52..c44cd842844 100644
--- a/docs/sources/plugins/datasources.md
+++ b/docs/sources/plugins/datasources.md
@@ -4,7 +4,7 @@ page_description: Datasource plugins for Grafana
page_keywords: grafana, plugins, documentation
---
- > Our goal is not to have a very extensive documentation but rather have actual code that people can look at. An example implementation of a datasource can be found in the grafana repo under /examples/datasource-plugin-genericdatasource
+ > Our goal is not to have a very extensive documentation but rather have actual code that people can look at. An example implementation of a datasource can be found in this [example datasource repo](https://github.com/grafana/simple-json-datasource)
# Datasources
diff --git a/docs/sources/plugins/developing_plugins.md b/docs/sources/plugins/developing_plugins.md
index b235fa8d3de..91d1ff3f84e 100644
--- a/docs/sources/plugins/developing_plugins.md
+++ b/docs/sources/plugins/developing_plugins.md
@@ -22,9 +22,7 @@ The easiset way to try your plugin with grafana is to [setup grafana for develop
## Examples / boilerplate
We currently have three different examples that you can fork to get started developing your grafana plugin.
- - [generic-datasource](https://github.com/grafana/grafana/tree/master/examples/datasource-plugin-genericdatasource) (small datasource plugin for quering json data from backends)
+ - [simple-json-datasource](https://github.com/grafana/simple-json-datasource) (small datasource plugin for quering json data from backends)
- [panel-boilderplate-es5](https://github.com/grafana/grafana/tree/master/examples/panel-boilerplate-es5)
- - [nginx-app](https://github.com/grafana/grafana/tree/master/examples/nginx-app)
+ - [example-app](https://github.com/grafana/example-app)
-## Publish your plugin
-We are currently working on this.
diff --git a/docs/sources/plugins/installation.md b/docs/sources/plugins/installation.md
index d3a8013ce2b..7a4ed1889f9 100644
--- a/docs/sources/plugins/installation.md
+++ b/docs/sources/plugins/installation.md
@@ -17,30 +17,30 @@ On Linux systems the grafana-cli will assume that the grafana plugin directory i
List available plugins
```
-grafana-cli list-remote
+grafana-cli plugins list-remote
```
Install a plugin type
```
-grafana-cli install Each organization contains their own dashboards, data sources and configuration, and cannot be shared between orgs. While users may belong to more than one, mutiple organization are most frequently used in multi-tenant deployments.
- +