Unblocking Backstage Projects Without Forking

on YouTube ↗05m

" summary

Explains concrete ways to avoid forking Backstage packages: check the code first to avoid unnecessary forks, note that forking locks a codebase to a fast-moving upstream and copied code often has no tests so maintenance costs explode, use the theme API to restyle UI without copying components, apply temporary fixes with patch package while opening upstream PRs and planning work around Backstage release cycles to minimize long-term debt.

AI-written summary · about

" chapters (5)

1. 0:00Introduction
2. 1:12Check if you need to Fork
3. 1:51Customize UI components
4. 2:16Patch packages
5. 3:16Conclusion

" related talks

• 24mHow to Grow Your Internal Backstage Community with Some Ope...Djamaile Rahamat, Mitchell Hentges · BackstageCon NA 2024
• 39mUnlocking Backstage's potential: insights and solutions for a smoother developer experienceGermelinda Musliaj, Abel Guillen · XConf Europe 2024
• 34mPanel: Building a Healthy Backstage Plugins EcosystemAramis Sennyey, Paul S, Hope H, Heikki H, Peter M · BackstageCon Europe 2026
• 26mBackstage Plugin Development: Tales from the TrenchesDebabrata Panigrahi · Kubernetes Community Days Bengaluru 2023
• 35mImproving Developer Experience with Open Source 1Suzanne Daniels · DevOpsDays Eindhoven 2022
• 04mKeynote: 10x the Effectiveness of Dev Teams with BackstageDavid Tuite · BackstageCon North America 2022
• 47mImproving Developer Experience with BackstageSuzanne Daniels · Emerging OS Forum @ Open Source Summit Europe 2022
• 22mUnlocking Backstage’s Potential: Driving Adoption and Maturity With Your Develope...Stanley Nicholl · BackstageCon Europe 2025