mirror of
https://github.com/Unleash/unleash.git
synced 2025-07-31 13:47:02 +02:00
Update UI text in Unleash welcome key concepts page (#8238)
This commit is contained in:
parent
6188079122
commit
1ea63a8a1f
Binary file not shown.
Before Width: | Height: | Size: 137 KiB After Width: | Height: | Size: 192 KiB |
@ -60,50 +60,47 @@ export const WelcomeDialog: FC<IWelcomeDialogProps> = ({ open, onClose }) => {
|
|||||||
/>
|
/>
|
||||||
</WelcomeLine>
|
</WelcomeLine>
|
||||||
<Box>
|
<Box>
|
||||||
Here are the concepts you{' '}
|
Here are the{' '}
|
||||||
<Typography
|
<Typography
|
||||||
component='span'
|
component='span'
|
||||||
color='primary'
|
color='primary'
|
||||||
fontWeight='bold'
|
fontWeight='bold'
|
||||||
>
|
>
|
||||||
must understand
|
key concepts
|
||||||
</Typography>{' '}
|
</Typography>{' '}
|
||||||
in order to work effectively with Unleash
|
you'll need when working with Unleash
|
||||||
</Box>
|
</Box>
|
||||||
<StyledImg src={formatAssetPath(onboardingConcepts)} />
|
<StyledImg src={formatAssetPath(onboardingConcepts)} />
|
||||||
<ScreenReaderOnly>
|
<ScreenReaderOnly>
|
||||||
<h2>Environments</h2>
|
<h2>Environments</h2>
|
||||||
<p>
|
<p>
|
||||||
Unleash comes with two global environments. Once you
|
Environments represent different stages in your
|
||||||
create a feature flag it will exist in all environments,
|
development lifecycle. The default environments are
|
||||||
but it will hold different configuration per
|
development and production.
|
||||||
environment.
|
|
||||||
</p>
|
</p>
|
||||||
<h2>Projects</h2>
|
<h2>Projects</h2>
|
||||||
<p>
|
<p>
|
||||||
Feature flags live in projects. When SDKs connect to
|
Projects help you organize feature flags and define
|
||||||
Unleash they use an environment /project combination in
|
access for users and applications. SDKs use a
|
||||||
order to retrieve the correct configuration. You can
|
combination of environment and project to retrieve
|
||||||
also use projects to control access level for feature
|
feature flag configurations.
|
||||||
flags.
|
|
||||||
</p>
|
</p>
|
||||||
<h2>Feature flags</h2>
|
<h2>Feature flags</h2>
|
||||||
<p>
|
<p>
|
||||||
Flags live in projects and across all configured
|
Feature flags exist within a project and have distinct
|
||||||
environments. Each flag will have separate configuration
|
configurations for each of the project's active
|
||||||
in each environment enabled for the project that they
|
environments.
|
||||||
live in.
|
|
||||||
</p>
|
</p>
|
||||||
<h2>Activation strategy</h2>
|
<h2>Activation strategy</h2>
|
||||||
<p>
|
<p>
|
||||||
Activation strategies are rulesets that decide whether
|
Activation strategies are rulesets that determine if a
|
||||||
or not a feature flag should be enabled in a specific
|
feature flag is enabled in a specific environment. You
|
||||||
environment. You can configure as many rulesets as you
|
can configure multiple activation strategies per
|
||||||
want per environment.
|
environment.
|
||||||
</p>
|
</p>
|
||||||
</ScreenReaderOnly>
|
</ScreenReaderOnly>
|
||||||
<Button variant='contained' onClick={onClose}>
|
<Button variant='contained' onClick={onClose}>
|
||||||
Got it, let's get started
|
Got it, let's get started!
|
||||||
</Button>
|
</Button>
|
||||||
</ContentWrapper>
|
</ContentWrapper>
|
||||||
</StyledDialog>
|
</StyledDialog>
|
||||||
|
Loading…
Reference in New Issue
Block a user