Skip to content

Update via pull request #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jumboduck wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update via pull request #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions evaluating-backstage-1-why-backstage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,9 @@ title: "Evaluating Backstage 1: Why Backstage?"
authors:
- Carlos Eduardo Inocencio Alanis
---

NEW SENTENCE AT THE TOP

This article is the first part of the "Evaluating Backstage" series. It covers all the basics around developer portals, introduces Backstage development, and explores how it can help your organization be more efficient and secure.

Backstage is a developer portal that acts as a centralized hub for your organization, providing access to documentation, infrastructure, tooling, and code standards. It gives developers everything they need to create and manage their projects in a consistent and standardized manner. To understand why Backstage exists, and why you should care about it at all, you must first understand the pain points it's trying to alleviate.
Expand Down