Chore: fix docs anchors (#1778)

Author: tolzhabayev

.gitignore

@@ -30,6 +30,8 @@ yarn-error.log*
 # Generated files
 .docusaurus
 .cache-loader
+docusaurus/website/scripts/plugin.schema.json
+*.bak
 
 # Allow vscode config inside templates
 !packages/create-plugin/templates/*/.vscode

docusaurus/docs/e2e-test-a-plugin/get-started.md

@@ -50,7 +50,7 @@ Open a new terminal and run the test script from within your local plugin develo
 
 ### Step 3: Run tests in CI
 
-The [`grafanaDependency`](../reference/metadata.md#properties-1) property in the `plugin.json` file specifies what versions of Grafana the plugin is compatible with. As a best practice, run your Playwright end-to-end tests targeting all the supported versions. The GitHub workflow that can be included when scaffolding plugins with `create-plugin` ensures this is the case.
+The [`grafanaDependency`](../reference/metadata.md#dependencies) property in the `plugin.json` file specifies what versions of Grafana the plugin is compatible with. As a best practice, run your Playwright end-to-end tests targeting all the supported versions. The GitHub workflow that can be included when scaffolding plugins with `create-plugin` ensures this is the case.
 
 If you chose to not add a GitHub workflow when you scaffolded the plugin, as a best practice follow the instructions in the [CI](./ci.md) guide to run Playwright end-to-end tests targeting all versions of Grafana that your plugin supports.
 

docusaurus/docs/migration-guides/update-from-grafana-versions/v7.x-v8.x.md

@@ -199,7 +199,7 @@ import { cx, css } from '@emotion/css';
 
 ## Update needed for app plugins using dashboards
 
-To make side navigation work properly - app plugins targeting Grafana `8.+` and integrating into the side menu via [addToNav](/reference/metadata.md#properties-6) property need to adjust their `plugin.json` and all dashboard json files to have a matching `uid`.
+To make side navigation work properly - app plugins targeting Grafana `8.+` and integrating into the side menu via [addToNav](/reference/metadata.md#includes) property need to adjust their `plugin.json` and all dashboard json files to have a matching `uid`.
 
 **`plugin.json`**
 

docusaurus/docs/publish-a-plugin/build-automation.md

@@ -20,7 +20,7 @@ to ensure that your plugin will be built and packaged in the correct format.
 
 Additionally, we recommend using the zip file produced from this workflow to test the plugin.
 
-If a Grafana Access Policy Token is included in your [Github repository secrets](https://docs.github.com/en/codespaces/managing-codespaces-for-your-organization/managing-development-environment-secrets-for-your-repository-or-organization), a signed build is automatically created, which you can use to test the plugin locally before submission. The [sign a plugin](./sign-a-plugin.md#generate-an-access-policy-token/) documentation includes guidance on how to create this token.
+If a Grafana Access Policy Token is included in your [Github repository secrets](https://docs.github.com/en/codespaces/managing-codespaces-for-your-organization/managing-development-environment-secrets-for-your-repository-or-organization), a signed build is automatically created, which you can use to test the plugin locally before submission. The [sign a plugin](./sign-a-plugin.md#generate-an-access-policy-token) documentation includes guidance on how to create this token.
 
 By creating a release tag, the whole process becomes automated, resulting in a zip file that you can submit for publication to the [Grafana plugin catalog](https://grafana.com/plugins)
 

docusaurus/docs/publish-a-plugin/publishing-best-practices.md

@@ -25,7 +25,7 @@ Metadata plays a crucial role in making your Grafana plugin discoverable and use
 
 Here’s a breakdown of the key components to focus on:
 
-**[Plugin name](../reference/plugin-json#properties)**
+**[Plugin name](../reference/plugin-json)**
 
 `name`
 
@@ -67,7 +67,7 @@ Ensure your screenshots are a suitable resolution and file type (e.g. png, jpeg,
 
 :::
 
-**[Sponsorship link](../reference/plugin-json#links)**
+**[Sponsorship link](../reference/plugin-json#infolinks)**
 
 `info.links`
 

docusaurus/docs/reference/metadata.md

@@ -121,7 +121,7 @@ You don't need to register all your pages inside `includes` in your `plugin.json
 
 :::tip
 
-You can limit which users have access to pages in the navigation menu by using the [`role`](/reference/plugin-json#properties-7) property.
+You can limit which users have access to pages in the navigation menu by using the [`role`](/reference/plugin-json#includes) property.
 
 :::
 

docusaurus/docs/tutorials/build-an-app-plugin.md

@@ -31,6 +31,7 @@ const config: Config = {
   baseUrl: 'developers/plugin-tools/',
   onBrokenLinks: 'throw',
   onBrokenMarkdownLinks: 'warn',
+  onBrokenAnchors: 'throw',
   favicon: 'img/favicon.png',
   // GitHub pages deployment config.
   // If you aren't using GitHub pages, you don't need these.

docusaurus/website/docusaurus.config.ts

@@ -19,14 +19,10 @@ fi
 npx --yes jsonschema2mk --partials "$PARTIALS" --schema "$INPUT_FILE" > "$OUTPUT_FILE"
 
 # Detect OS and set sed options accordingly
-if [[ "$OSTYPE" == "darwin"* ]]; then
-    SED_OPTS="-i ''"
-else
-    SED_OPTS="-i"
-fi
+
 
 # Add docusaurus header to the top of the file
-sed $SED_OPTS "1i\\
+sed -i.bak "1i\\
 ---\\
 id: plugin-json\\
 title: Metadata (plugin.json)\\
@@ -45,5 +41,6 @@ sidebar_position: 10\\
 " "$OUTPUT_FILE"
 
 rm -f "$INPUT_FILE"
+rm -f "$OUTPUT_FILE.bak"
 
 echo "Markdown generation complete!"