docs: add missing description frontmatter to golden-path docs
Signed-off-by: chanchalkhatri19 <chanchal.khatri01@infosys.com>
This commit is contained in:
@@ -2,6 +2,7 @@
|
||||
id: getting-started
|
||||
sidebar_label: 001 - Getting started
|
||||
title: Getting started with Backstage
|
||||
description: An introduction to the Backstage adoption journey and what to expect
|
||||
---
|
||||
|
||||
The adoption journey is a bit different than the other Golden Paths. The goal of this guide is to prepare you for a successful implementation of Backstage in your organization. A technical understanding of Backstage is not needed for this Golden Path, just a desire to help the technical team that will be owning your Backstage instance.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
id: leadership-buy-in
|
||||
sidebar_label: 002 - Leadership buy-in
|
||||
title: Getting leadership buy-in
|
||||
description: How to build a case for Backstage adoption and secure leadership support
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
id: setting-up-a-poc
|
||||
sidebar_label: 003 - Setting up a PoC
|
||||
title: Setting up a PoC
|
||||
description: How to set up a proof of concept Backstage instance for your organization
|
||||
---
|
||||
|
||||
If you're non-technical, this section should be completed by your technical partner.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
id: first-stakeholder-feedback
|
||||
sidebar_label: 004 - Stakeholder Feedback
|
||||
title: First round of stakeholder feedback
|
||||
description: How to gather and incorporate stakeholder feedback on your Backstage PoC
|
||||
---
|
||||
|
||||
Now that you have a PoC running, let's walk through how to get good feedback. You likely aren't the first person to hear about Backstage or maybe not even the first person to set up a PoC. There may be common pitfalls unique to your company that are worth knowing about - political, organizational or otherwise.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
id: customize-your-instance
|
||||
sidebar_label: 005 - Customizing your instance
|
||||
title: Customizing your instance
|
||||
description: How to customize your Backstage instance based on user feedback
|
||||
---
|
||||
|
||||
You now have the knowledge of what your users want and the go from leadership to continue investing in Backstage. Your job now is to customize your instance for your users to really get the value from. Let's dive in!
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
id: preparing-for-ga
|
||||
sidebar_label: 006 - Preparing for GA
|
||||
title: Preparing for GA
|
||||
description: How to prepare your Backstage instance for a company-wide general availability launch
|
||||
---
|
||||
|
||||
We hope at this point that the developers you're working with have read the [golden path on deploying Backstage](../deployment/index.md). Your Backstage instance should be ready for the scale that comes with a full company launch.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
id: plugin-ownership
|
||||
sidebar_label: 007 - Plugin Ownership
|
||||
title: Plugin Ownership
|
||||
description: How to establish and manage plugin ownership across your organization
|
||||
---
|
||||
|
||||
You're now well on your way to a healthy Backstage instance! It's been launched to the whole company and you're loving the feedback developers are giving you. Some developers have even started broaching writing their own plugins.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
id: full-catalog
|
||||
sidebar_label: 008 - A Full Catalog
|
||||
title: Ensuring your catalog stays complete
|
||||
description: Strategies for maintaining a complete and up-to-date software catalog
|
||||
---
|
||||
|
||||
Along your Backstage journey (and any workflow migration journey), you will hit a point where incremental adoption is no longer easy. The new developers are no longer flowing into your tool like they once did. More and more projects are not being listed in your catalog. Something has to change.
|
||||
|
||||
Reference in New Issue
Block a user