From 8786240ddff8efa98cea5b93abcd4bb6620dd9d4 Mon Sep 17 00:00:00 2001 From: Alvin Bryan <107407814+alvinometric@users.noreply.github.com> Date: Wed, 7 Aug 2024 09:08:24 +0200 Subject: [PATCH] Updated for 11 principles article (#7779) Made the `<title>` and the h1 different --- .../docs/topics/feature-flags/feature-flag-best-practices.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/docs/topics/feature-flags/feature-flag-best-practices.md b/website/docs/topics/feature-flags/feature-flag-best-practices.md index 2cdc0d4645..22615bfd5e 100644 --- a/website/docs/topics/feature-flags/feature-flag-best-practices.md +++ b/website/docs/topics/feature-flags/feature-flag-best-practices.md @@ -1,7 +1,9 @@ --- -title: "Feature flags: Best practices for building and scaling feature flag systems" +title: "Feature flags: Best practices for building and scaling" --- +# Feature flags: Best practices for building and scaling feature flag systems + import Figure from '@site/src/components/Figure/Figure.tsx' Feature flags, sometimes called feature toggles or feature switches, are a software development technique that allows engineering teams to decouple the release of new functionality from software deployments. With feature flags, developers can turn specific features or code segments on or off at runtime, without the need for a code deployment or rollback. Organizations who adopt feature flags see improvements in all key operational metrics for DevOps: Lead time to changes, mean-time-to-recovery, deployment frequency, and change failure rate.