From 6ba936fa27d8b2c4563448da219fd019d2a13868 Mon Sep 17 00:00:00 2001 From: Jeff Feng <46946747+fengypants@users.noreply.github.com> Date: Tue, 22 Dec 2020 11:04:07 -0500 Subject: [PATCH] Update 2020-12-22-stability-index.md Adding truncate tag so post previews on /blog with Read More button. --- microsite/blog/2020-12-22-stability-index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/microsite/blog/2020-12-22-stability-index.md b/microsite/blog/2020-12-22-stability-index.md index 77381ef801..95074a13a2 100644 --- a/microsite/blog/2020-12-22-stability-index.md +++ b/microsite/blog/2020-12-22-stability-index.md @@ -8,6 +8,8 @@ authorURL: https://github.com/Rugvip ![Animation cycling between stability index scores](assets/2020-12-22/stability-index-hero.gif) + + Backstage has a great and growing community of users and contributors. With so much valuable feedback, this inevitably means that sometimes we will go back and revise design decisions that introduce breaking changes. Furthermore, as we continue to ship new features and systems, we’ll continue this cycle of iterating, gathering feedback, and iterating again before reaching a stable API. This rapid evolution can create uncertainty around which parts of the project are considered stable and which are not. Regardless of whether you're contributing to the project directly, setting up your own Backstage, or building plugins, you will be using various parts of the project that vary in stability. While many API surfaces of Backstage are reasonably solid and are unlikely to see any big breaking changes, others are more unstable or experimental.