Exemplar-y Backstage Templates
summary
Claims that converting Backstage scaffolder templates into exemplar templates — standalone repos instead of embedded Nunjucks files — lets standard tooling run: a tiny custom action does string-replace of templated tokens, fetch_template pulls the repo, Yarn, Renovate, CI, Play tests and S3 deploys run against real projects. Results: PRs merge ~18× faster, each template use saves ~4 hours, and templates auto-update via Renovate with pass/fail signals from builds and integration tests, proving the approach works.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:48New project template pain
- 3:54Backstage template limits
- 5:20Maintaining templates challenges
- 8:10Transition to Exemplar-y
- 9:13Custom actions for templates
- 11:20Real projects as templates
- 13:27Better collaboration and onboarding
- 15:11ROI of Exemplar-y
- 16:13Conclusion and Q&A
related talks
27mIntroduction to Backstage
29mWhat Does Backstage Really Offer – Looking Beyond Catalog and Templates and Into...
28mProject templates with Cookiecuter
19mScaling Team Delivery Using Standardization
35mBackstage: Restoring Order To Your Chaos
26mBackstage Plugin Development: Tales from the Trenches
24mHow to Grow Your Internal Backstage Community with Some Ope...
33mLeading Architectural Change with Backstage