Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update UI text in Unleash welcome key concepts page #8238

Merged
merged 6 commits into from
Sep 30, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 18 additions & 21 deletions frontend/src/component/personalDashboard/WelcomeDialog.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -60,50 +60,47 @@ export const WelcomeDialog: FC<IWelcomeDialogProps> = ({ open, onClose }) => {
/>
</WelcomeLine>
<Box>
Here are the concepts you{' '}
Here are the{' '}
<Typography
component='span'
color='primary'
fontWeight='bold'
>
must understand
key concepts
</Typography>{' '}
in order to work effectively with Unleash
you'll need when working with Unleash
</Box>
<StyledImg src={formatAssetPath(onboardingConcepts)} />
<ScreenReaderOnly>
<h2>Environments</h2>
<p>
Unleash comes with two global environments. Once you
create a feature flag it will exist in all environments,
but it will hold different configuration per
environment.
Unleash comes with two default environments. Feature
melindafekete marked this conversation as resolved.
Show resolved Hide resolved
flags exist across all environments but can have
different configurations in each.
</p>
<h2>Projects</h2>
<p>
Feature flags live in projects. When SDKs connect to
Unleash they use an environment /project combination in
order to retrieve the correct configuration. You can
also use projects to control access level for feature
flags.
Feature flags live inside projects. When SDKs connect to
Unleash they use the combination of environment and
project to retrieve the correct configuration. Projects
also control who can access a feature flag.
</p>
<h2>Feature flags</h2>
<p>
Flags live in projects and across all configured
environments. Each flag will have separate configuration
in each environment enabled for the project that they
live in.
Flags live inside a project and exist across all its
environments. Flags can have a unique configuration in
each environment enabled for their project.
</p>
<h2>Activation strategy</h2>
<p>
Activation strategies are rulesets that decide whether
or not a feature flag should be enabled in a specific
environment. You can configure as many rulesets as you
want per environment.
Activation strategies are rulesets that determine if a
feature flag should be enabled in a specific
environment. You can configure multiple activation
strategies per environment.
</p>
</ScreenReaderOnly>
<Button variant='contained' onClick={onClose}>
Got it, let's get started
Got it, let's get started!
</Button>
</ContentWrapper>
</StyledDialog>
Expand Down
Loading