diff --git a/frontend/web/components/pages/WhatAreFeatureFlagsPage.js b/frontend/web/components/pages/WhatAreFeatureFlagsPage.js deleted file mode 100644 index 5a8b2d435b52..000000000000 --- a/frontend/web/components/pages/WhatAreFeatureFlagsPage.js +++ /dev/null @@ -1,129 +0,0 @@ -import React, { Component } from 'react'; - -const WhatAreFeatureFlagsPage = class extends Component { - static displayName = 'WhatAreFeatureFlagsPage' - - constructor(props, context) { - super(props, context); - this.state = {}; - } - - componentDidMount() { - API.trackPage(Constants.pages.WHAT_ARE_FEATURE_FLAGS); - } - - render() { - return ( -
- -
-

What are feature flags?

-
-
-

- A Feature Flag is a technique to turn some functionality of your application off, - via configuration, without deploying new code. If you’re employing CI/CD and - releasing - often they’re pretty important. -

-

- With Flagsmith, feature flags can be turned on and off per environment, also you - can enable flags for specific users. For example, this could be used to show - features to your internal team in production or for beta testers. -

-
-
-

- EXAMPLE: our interactive try it panels throughout the site are controlled by feature - flags. -

-
- -
-
-
-
-
- -
-

What is remote config?

-
-
-

- It's great being able to turn features on and off without doing a build, but with - some - features, - it's not as simple as that. This is where remote config comes in. - Often there's a need to configure feature properties, for example updating some text - to - promote an - in-app currency sale or even the copy on our homepage. -

-

- Similarly with feature flags, Flagsmith lets you configure these per environment - and for specific users. With our upcoming user segments feature, this could be used - to show different messaging or environment variables to power user groups, - mobile/browser specific users and - much more. -

-
-
-

- EXAMPLE: our homepage sections are controlled with remote config -

-
- -
-
-
-
-
- -
-

What benefits does this bring?

- -

- People who are not used to continuous integration might be wondering: why didn't I just - release the feature the way I normally would? Some of the reasons for feature flags being - such a good approach: -

-
    -
  • - It introduces the ability to test code in production with gradual/targeted rollouts to - specific - users. -
  • -
  • - It empowers non-technical team members to manage feature releases. -
  • -
  • - It enables testing of features early, against an up-to-date codebase. CI means we're - constantly - testing features on a very close representation to what is running in production. -
  • -
  • - It allows you to introduce beta programs to get early user feedback. -
  • -
  • - It reduces the need to rollback code with the ability to turn off features remotely in - the - event - of an emergency. -
  • -
-
-
-
- ); - } -}; - -WhatAreFeatureFlagsPage.propTypes = {}; - -module.exports = WhatAreFeatureFlagsPage; diff --git a/frontend/web/images/feature-flag.gif b/frontend/web/images/feature-flag.gif deleted file mode 100644 index 351d76ab6a48..000000000000 Binary files a/frontend/web/images/feature-flag.gif and /dev/null differ diff --git a/frontend/web/images/remote-config.gif b/frontend/web/images/remote-config.gif deleted file mode 100644 index 2e8d3839e787..000000000000 Binary files a/frontend/web/images/remote-config.gif and /dev/null differ