Link to marketplace issue from roadmap (#2010)

* Link to marketplace issue from roadmap

* Update roadmap.md

* Update roadmap.md

* Update roadmap.md

docs/overview/roadmap.md

@@ -5,17 +5,17 @@ title: Project roadmap
 
 ## Current status
 
-Backstage is currently in Alpha. This means that you can expect APIs and
-features to change until we reach our
-[Backstage Beta milestone](https://github.com/spotify/backstage/milestone/19).
-Before we have API stability, plugins will need ongoing maintenance. It is also
-recommended that teams who adopt Backstage today upgrades their installation as
-new [releases](https://github.com/spotify/backstage/releases) are available.
+> Backstage is currently in Alpha. This means that you can expect APIs and
+> features to change until we reach our
+> [Backstage Beta milestone](https://github.com/spotify/backstage/milestone/19).
+> Before we have API stability, plugins will need ongoing maintenance. It is
+> also recommended that teams who adopt Backstage today upgrades their
+> installation as new [releases](https://github.com/spotify/backstage/releases)
+> are available.
 
 ## Phases
 
-We have divided the project into three high-level _phases_ and we have already
-begun work on various aspects of these phases:
+We have divided the project into three high-level _phases_:
 
 - 🐣 **Phase 1:** Extensible frontend platform (Done ✅) - You will be able to
   easily create a single consistent UI layer for your internal infrastructure
@@ -35,22 +35,81 @@ begun work on various aspects of these phases:
 
 ## Detailed roadmap
 
+If you have questions about the roadmap or want to provide feedback, we would
+love to hear from you! Please create an
+[Issue](https://github.com/spotify/backstage/issues/new/choose), ping us on
+[Discord](https://discord.gg/EBHEGzX) or reach out directly at
+[alund@spotify.com](mailto:alund@spotify.com).
+
+Want to help out? Awesome ❤️ Head over to
+[CONTRIBUTING](https://github.com/spotify/backstage/blob/master/CONTRIBUTING.md)
+guidelines to get started.
+
 ### Ongoing work 🚧
 
-- [Plugins for managing micro services end-2-end](https://github.com/spotify/backstage/milestone/14)
-- [TechDocs v1](https://github.com/spotify/backstage/milestone/16)
-- [Initial GraphQL API](https://github.com/spotify/backstage/milestone/13)
-- Backstage Design Language System (DLS)
-- Cloud Cost Insights plugin (from Spotify)
+- **[Plugins for managing micro services end-2-end](https://github.com/spotify/backstage/milestone/14)** -
+  Out of the box Backstage will ship with a set of plugins (Overview, CI, API
+  and Docs) that will demonstrate how a user can manage a micro service and
+  follow a change all the way out in production. Completing this work will make
+  it much easier to see how a plugin can be built that integrates with the
+  Backstage Service Catalog.
+
+- **Backstage Design System** - By providing design guidelines for common plugin
+  layouts together, rich set of reusable UI components
+  ([Storybook](https://backstage.io/storybook)) and Figma design resources. The
+  Design System will make it easy to design and build plugins that are
+  consistent across the platform -- supporting both developers and designers.
+
+- **[TechDocs v1](https://github.com/spotify/backstage/milestone/16)** - Our
+  docs-like-code feature TechDocs working end to end.
+
+- **[Initial GraphQL API](https://github.com/spotify/backstage/milestone/13)** -
+  A GraphQL API will open up the rich metadata provided by Backstage in a single
+  query. Plugins can easily query this API as well as extend the model where
+  needed.
+
+- **Production deployments** - Provide instructions and default configurations
+  (e.g. through Helm charts) for easy deployments of Backstage and its
+  subsystems on Kubernetes.
+
+- **Cloud Cost Insights plugin (from Spotify)** - Spotify teams are fully
+  responsible for their own software, including the cost of the cloud resources
+  they use. By making our internal cost insights plugin available as open source
+  you will also be able to treat cost as an engineering problem, and make it
+  easy for your engineers to see their spend and where there's opportunity to
+  reduce waste.
+
 - Further improvements to platform documentation
 
 ### Future work 🔮
 
-- [Backstage Beta](https://github.com/spotify/backstage/milestone/19)
-- [Global search](https://github.com/spotify/backstage/issues/1499)
-- [[TechDocs V.2] Stabilization release](https://github.com/spotify/backstage/milestone/17)
-- Deploy a product demo at `demo.backstage.io`
-- Plugin marketplace
+- **[Backstage Beta](https://github.com/spotify/backstage/milestone/19)** - The
+  platform APIs and features are stable and can be dependent on for production
+  use. After this plugins will require little to no maintenance.
+
+- **[Plugin marketplace](https://github.com/spotify/backstage/issues/2009)** -
+  As the ecosystem of Backstage plugins continues to grow it is becoming
+  increasingly hard to keep track of what plugins are available. To solve this
+  we imagine a "Plugin marketplace" that helps with discovery and installation
+  of plugins.
+
+- **Deploy a product demo at `demo.backstage.io`** - Deploy a typical Backstage
+  deployment available publicly so that people can click around and get a feel
+  for the product without having to install anything.
+
+- **[Global search](https://github.com/spotify/backstage/issues/1499)** - Extend
+  the basic search available in the Backstage Service Catalog with a global
+  search experience. Long term this search solution should be extensible, making
+  it possible for you add custom search results.
+
+- **[[TechDocs V.2] Stabilization release](https://github.com/spotify/backstage/milestone/17)** -
+  Platform stability and compatibility improvements.
+
+- **Additional auth providers** - Backstage should work for most (all!) auth
+  solutions. Since Backstage can be used by companies regardless of what cloud
+  (or on prem) you are using we are especially keen to get auth support for
+  [AWS](https://github.com/spotify/backstage/issues/290),
+  [Azure](https://github.com/spotify/backstage/issues/348) and others.
 
 ### Completed milestones ✅