From 41370be591c9bd4c5c103e87ee26c57768fe42dd Mon Sep 17 00:00:00 2001 From: Jaanus Sellin Date: Wed, 14 Jun 2023 08:46:15 +0300 Subject: [PATCH] feat: update predefined strategies tooltip (#3964) --- .../src/component/strategies/StrategiesList/StrategiesList.tsx | 2 +- website/docs/reference/activation-strategies.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/frontend/src/component/strategies/StrategiesList/StrategiesList.tsx b/frontend/src/component/strategies/StrategiesList/StrategiesList.tsx index c7736a440f..5f379070a4 100644 --- a/frontend/src/component/strategies/StrategiesList/StrategiesList.tsx +++ b/frontend/src/component/strategies/StrategiesList/StrategiesList.tsx @@ -76,7 +76,7 @@ const PredefinedStrategyTitle = () => ( ({ marginBottom: theme.spacing(1.5) })}> diff --git a/website/docs/reference/activation-strategies.md b/website/docs/reference/activation-strategies.md index 884ff633aa..1bcf9e853d 100644 --- a/website/docs/reference/activation-strategies.md +++ b/website/docs/reference/activation-strategies.md @@ -2,7 +2,7 @@ title: Activation Strategies --- -It is powerful to be able to turn a feature on and off instantaneously, without redeploying the application. The next level of control comes when you are able to enable a feature for specific users or enable it for a small subset of users. We achieve this level of control with the help of activation strategies. The most straightforward strategy is the standard strategy, which basically means that the feature should be enabled to everyone. +It is powerful to be able to turn a feature on and off instantaneously, without redeploying the application. Activation strategies let you enable a feature only for a specified audience. Different strategies use different parameters. Predefined strategies are bundled with Unleash. The recommended strategy is the gradual rollout strategy with 100% rollout, which basically means that the feature should be enabled to everyone. Unleash comes with a number of built-in strategies (described below) and also lets you add your own [custom activation strategies](../reference/custom-activation-strategies.md) if you need more control. However, while activation strategies are _defined_ on the server, the server does not _implement_ the strategies. Instead, activation strategy implementation is done client-side. This means that it is _the client_ that decides whether a feature should be enabled or not.