From f6f0c6176c550e9791bc7a02ed07a0c72cfb1cdb Mon Sep 17 00:00:00 2001 From: "Grot (@grafanabot)" <43478413+grafanabot@users.noreply.github.com> Date: Wed, 13 Sep 2023 17:58:57 +0200 Subject: [PATCH] [v9.0.x] [v8.5.x] Docs: removed dead link (#74856) [v8.5.x] Docs: removed dead link (#74851) Removed link (cherry picked from commit 1b89928ec3f0bb0cc51680e98b585161642df5a4) Co-authored-by: Isabel <76437239+imatwawana@users.noreply.github.com> --- docs/sources/whatsnew/whats-new-in-v7-0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/whatsnew/whats-new-in-v7-0.md b/docs/sources/whatsnew/whats-new-in-v7-0.md index a84453846ee..f6dbb691c15 100644 --- a/docs/sources/whatsnew/whats-new-in-v7-0.md +++ b/docs/sources/whatsnew/whats-new-in-v7-0.md @@ -136,7 +136,7 @@ In Grafana 7.0 we are maturing our panel and front-end datasource plugins platfo Plugins can use the same React components that the Grafana team uses to build Grafana. Using these components means the Grafana team will support and improve them continually and make your plugin as polished as the rest of Grafana’s UI. The new [`@grafana/ui` components library](https://developers.grafana.com/ui) is documented with Storybook (visual documentation) and is available on NPM. -The `@grafana/data`, `@grafana/runtime`, `@grafana/e2e packages` (also available via NPM) aim to simplify the way plugins are developed. We want to deliver a set of [reliable APIs](https://grafana.com/docs/grafana/latest/packages_api/) for plugin developers. +The `@grafana/data`, `@grafana/runtime`, `@grafana/e2e packages` (also available via NPM) aim to simplify the way plugins are developed. We want to deliver a set of reliable APIs for plugin developers. With [@grafana/toolkit](https://www.npmjs.com/package/@grafana/toolkit) we are delivering a simple CLI that helps plugin authors quickly scaffold, develop and test their plugins without worrying about configuration details. A plugin author no longer needs to be a grunt or webpack expert to build their plugin.