[Docs] Fix relative paths to code (#1662)

* [Docs] Fix relative paths to code

* Update create-a-plugin.md

* Link to existing plugins

* Update README.md

* Update README.md

* Review edits

docs/plugins/create-a-plugin.md

@@ -24,7 +24,7 @@ for your new plugin directly by navigating to
 `http://localhost:3000/my-plugin`._
 
 <p align='center'>
-    <img src='https://github.com/spotify/backstage/raw/master/docs/getting-started/my-plugin_screenshot.png' width='600' alt='my plugin'>
+    <img src='https://github.com/spotify/backstage/raw/master/docs/plugins/my-plugin_screenshot.png' width='600' alt='my plugin'>
 </p>
 
 You can also serve the plugin in isolation by running `yarn start` in the plugin

docs/plugins/existing-plugins.md

@@ -0,0 +1,11 @@
+# Existing plugins
+
+## Open source plugins
+
+The full list of open source plugins can be found
+[here](https://github.com/spotify/backstage/tree/master/plugins).
+
+## Plugin gallery
+
+TODO: In the future we would like to have something similar to
+https://grafana.com/grafana/plugins

docs/plugins/index.md

@@ -5,15 +5,14 @@ Backstage is a single-page application composed of a set of plugins.
 Our goal for the plugin ecosystem is that the definition of a plugin is flexible
 enough to allow you to expose pretty much any kind of infrastructure or software
 development tool as a plugin in Backstage. By following strong
-[design guidelines](https://github.com/spotify/backstage/blob/master/docs/design.md)
-we ensure the the overall user experience stays consistent between plugins.
+[design guidelines](../dls/design.md) we ensure the the overall user experience
+stays consistent between plugins.
 
 ![plugin](my-plugin_screenshot.png)
 
 ## Creating a plugin
 
-To create a plugin, follow the steps outlined
-[here](https://github.com/spotify/backstage/blob/master/docs/getting-started/create-a-plugin.md).
+To create a plugin, follow the steps outlined [here](create-a-plugin.md).
 
 ## Suggesting a plugin
 

docs/plugins/publishing.md

@@ -3,9 +3,10 @@
 ## NPM
 
 NPM packages are published through CI/CD in the
-[.github/workflows/master.yml](../../.github/workflows/master.yml) workflow.
-Every commit that is merged to master will be checked for new versions of all
-public packages, and any new versions will automatically be published to NPM.
+[.github/workflows/master.yml](https://github.com/spotify/backstage/blob/master/.github/workflows/master.yml)
+workflow. Every commit that is merged to master will be checked for new versions
+of all public packages, and any new versions will automatically be published to
+NPM.
 
 ### Creating a new release
 

docs/plugins/structure-of-a-plugin.md

@@ -102,6 +102,6 @@ environment you will probably face challenges like CORS policies and/or
 backend-side authorization. To smooth this process out you can use proxy -
 either the one you already have (like nginx/haproxy/etc) or the proxy-backend
 plugin that we provide for the backstage backend.
-[Read more](../../plugins/proxy-backend/README.md)
+[Read more](https://github.com/spotify/backstage/blob/master/plugins/proxy-backend/README.md)
 
 [Back to Getting Started](../README.md)