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

Merge pull request #16318 from backstage/rugvip/folds

Browse Source 
microsite: add fold to last two blog posts
This commit is contained in:
Patrik Oldsberg
2023-02-14 10:09:59 +01:00
committed by GitHub
parent 9659bb524f 08b7ac6f07
commit 65fb9d3ca4
2 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
microsite/blog/2023-01-31-incremental-entity-provider.md
+3 -1
View File
@@ -4,10 +4,12 @@ author: Paul Cowan & Taras Mankovski
authorURL: https://frontside.com/
---
At the heart of [Backstage](https://backstage.io/) is the [Backstage Software Catalog](https://backstage.io/docs/features/software-catalog/software-catalog-overview), which is a data store that allows an organization to centralize and visualize its many software services and components. Backstage inspects and transforms an organization's disparate software services and parts into a centralized data store.
At the heart of [Backstage](https://backstage.io/) is the [Backstage Software Catalog](https://backstage.io/docs/features/software-catalog/software-catalog-overview), which is a data store that allows an organization to centralize and visualize its many software services and components. Backstage inspects and transforms an organization's disparate software services and parts into a centralized data store. This blog post introduces the concept of incremental entity providers, which allow Backstage to scale ingestion to even larger datasets.
![catalog pipeline](assets/2023-01-31/catalog-pipeline.png)
<!--truncate-->
A common use case is for an organization to want to surface ownership and metadata about repositories. Backstage provides a mechanism for discovering and transforming repository information into a standard data structure and persisting it into the Backstage [Catalog](https://backstage.io/docs/features/software-catalog/software-catalog-overview). This process is known as ingestion, where all data is transformed into a standard Backstage data structure known as an entity. Entities in the Catalog’s data store are accessible to the Backstage App via the REST API.
Data is transformed into entities via what is known as the ingestion and processing loop, which can be thought of as an [extract, transform and load (ETL) pipeline](https://en.wikipedia.org/wiki/Extract,_transform,_load), where raw data such as GitHub repositories are loaded from GitHub, transformed into entities and outputted to the Catalog.
microsite/blog/2023-02-06-whats-ahead-in-2023.md
+2
View File
@@ -10,6 +10,8 @@ authorURL: https://github.com/leemills83
Okay, everyone. Time to move on from all the 2022 reflections, Top 10 lists, and Wrapped(s), and turn our gaze in the other direction — towards 2023. As the Backstage team moves into the new year, we find ourselves asking those perennial questions: How can we continue to grow and enhance the Backstage community? How can we improve the experience for those adopting Backstage? How can we give the best support to Backstage contributors?
<!--truncate-->
Well, we don’t have all the answers, but we do have some. So we wanted to share more on three ongoing initiatives aimed at moving the needle forward for these three distinct, yet interrelated, questions.
- Grow your influence by climbing the contribution ladder