paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 40 Packages Projects Releases Wiki Activity

Apply suggestions from code review

Browse Source 
Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
This commit is contained in:
Patrik Oldsberg
2024-05-20 12:56:47 +02:00
committed by GitHub
parent 596dea1261
commit 1b0ed555c6
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
beps/0007-docs-personas-framework-portal/README.md
+3 -3
View File
@@ -1,12 +1,12 @@
---
title: Enhancing Backstage Documentation, Personas, Framework, and Developer Portal
title: Improved Backstage Documentation with Personas
status: provisional
authors:
- '@waldirmontoya25'
- '@aramissennyeyd'
owners:
project-areas:
- Documentation
- core
creation-date: 2024-03-18
---
@@ -67,7 +67,7 @@ The proposed restructuring of the Backstage documentation revolves around two co
2. Defining the personas participating in Backstage adoption journeys to improve documentation navigation. The identified personas are:
- **User**: A person who uses Backstage to find information, use plugins, and consume the developer portal.
- **End User**: A person who uses Backstage to find information, use plugins, and consume the developer portal.
- **Administrator/Operator**: A person who configures, secures, and deploys the developer portal, manages plugins, and oversees the general administration of the developer portal.
- **Integrator/Builder**: A person who builds plugins, customizes the code and design, and creates custom-built developer portals based on the Backstage framework. This includes developers and designers and anyone adding new functionality to their own Backstage instance.
- **Product Manager/Business stakeholders**: A person who defines the strategy for adopting Backstage, identifies use cases, communicates the value proposition for adopting Backstage and connects the developer portal to the business strategy.