From 8c014679b1064dbf6e5e535e48d5e45316e60005 Mon Sep 17 00:00:00 2001
From: Thomas Heartman <thomas@getunleash.ai>
Date: Tue, 11 Oct 2022 11:32:48 +0200
Subject: [PATCH] docs: Convert all images to using the figure component

---
 website/docs/topics/anatomy-of-unleash.mdx | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/docs/topics/anatomy-of-unleash.mdx b/website/docs/topics/anatomy-of-unleash.mdx
index 7d1095a49e..ca05ecb1a7 100644
--- a/website/docs/topics/anatomy-of-unleash.mdx
+++ b/website/docs/topics/anatomy-of-unleash.mdx
@@ -28,7 +28,7 @@ All Unleash instances must have at least one project at any given time. New inst
 
 Pro and Enterprise customers can create, rename, and delete projects as they wish (as long as there is always **at least one project**). Open-source users, on the other hand, only get access to the default project.
 
-<Figure caption="Unleash projects (the outer box) contain one or more environments (the inner box)." img={'/img/anatomy-of-unleash-environment.png'}/>
+<Figure caption="Unleash projects (the outer box) contain one or more environments (the inner box)." img="/img/anatomy-of-unleash-environment.png"/>
 
 ## Environments and project environments
 
@@ -49,9 +49,9 @@ Environments are adjacent to [feature toggles](../reference/feature-toggles.mdx)
 
 When creating a feature toggle, you must assign a unique (across your Unleash instance) name, a [feature toggle type](../advanced/feature-toggle-types.md), a [project](../user_guide/projects.md) it belongs to, and an optional description. Everything except for the name can be changed later.
 
-![alt_text](/img/anatomy-of-unleash-features.png)
+<Figure img="/img/anatomy-of-unleash-features.png" caption="TODO"/>
 
-![alt_text](/img/anatomy-of-unleash-strategy.png)
+<Figure img="/img/anatomy-of-unleash-strategy.png" caption="TODO"/>
 
 
 
@@ -65,7 +65,7 @@ Activation strategies tie feature toggles and [environments](../user_guide/envir
 
 Unleash comes with a number of strategies built in (refer the [activation strategies documentation](../user_guide/activation-strategies.md) for more information on those). You can also create your own [custom activation strategies](../advanced/custom-activation-strategy.md) if you need them. All strategies can be further augmented by [**strategy constraints**](../advanced/strategy-constraints.md).
 
-![alt_text](/img/anatomy-of-unleash-constraint.png)
+<Figure img="/img/anatomy-of-unleash-constraint.png" caption="TODO"/>
 
 ## Strategy constraints
 
@@ -92,7 +92,7 @@ You can apply multiple segments to a strategy. Much like with constraints, **eve
 
 Segments are only available to Pro and Enterprise users.
 
-![alt_text](/img/anatomy-of-unleash-segments.png)
+<Figure img="/img/anatomy-of-unleash-segments.png" caption="TODO"/>
 
 ## Variants and feature toggle payloads
 
@@ -106,18 +106,18 @@ You can use the variant payload to attach arbitrary data to a variant. Variants
 
 A feature toggle can have as many variants as you want. Importantly, variants are independent of [environments](../user_guide/environments.md). In other words: you’ll always have the exact same variants with the exact same weightings and the exact same payloads in all environments.
 
-![alt_text](/img/anatomy-of-unleash-environments-strategies.png)
+<Figure img="/img/anatomy-of-unleash-environments-strategies.png" caption="TODO"/>
 
-![alt_text](/img/anatomy-of-unleash-environments-strategies2.png)
+<Figure img="/img/anatomy-of-unleash-environments-strategies2.png" caption="TODO"/>
 
-![alt_text](/img/anatomy-of-unleash-variants.png)
+<Figure img="/img/anatomy-of-unleash-variants.png" caption="TODO"/>
 
-![alt_text](/img/anatomy-of-unleash-customer-tiers.png)
+<Figure img="/img/anatomy-of-unleash-customer-tiers.png" caption="TODO"/>
 
 
 **Example 1: **Customers above a certain tier get additional features
 
-![alt_text](/img/anatomy-of-unleash-new-feature-rollout.png)
+<Figure img="/img/anatomy-of-unleash-new-feature-rollout.png" caption="TODO"/>
 
 **Example 2: **New feature rollout for improved checkout process