diff --git a/content/implementations/_index.md b/content/implementations/_index.md
index bdd761b..78c3a26 100644
--- a/content/implementations/_index.md
+++ b/content/implementations/_index.md
@@ -17,7 +17,7 @@ color : blue-1
#### Element
{{< /implementation >}}
-{{< implementation type="client" devs="IndieHosters" link="https://scim2-cli.readthedocs.io/en/latest/#">}}
+{{< implementation type="client" devs="Yaal" link="https://scim2-cli.readthedocs.io/en/latest/#">}}
#### Cli
{{< /implementation >}}
{{< /grid >}}
\ No newline at end of file
diff --git a/content/overview/comparison.md b/content/overview/comparison.md
index ee433d0..a441afa 100644
--- a/content/overview/comparison.md
+++ b/content/overview/comparison.md
@@ -8,7 +8,10 @@ weight : 4
{{< switch-box title="Ldap" >}}
With this LDAP approach **everything is centralized** (except authorization).
-![LDAP diagram](media/ldap-diagram.svg)
+
**Everything speaks the LDAP protocol langage.** Identities are stored in an LDAP directory, which is provisioned via LDAP protocol. Authentication is done by the application that asks the user’s credentials and validates them against the directory via LDAP protocol.
{{< /switch-box >}}
@@ -16,20 +19,29 @@ With this LDAP approach **everything is centralized** (except authorization).
{{< switch-box title="Ldap+SSO" >}}
This architecture **tackles the two main drawbacks of the only LDAP approach** : the missing single sign-on and the security vulnerability. **Authentication is delegated to other web protocols** (like OAuth, OIDC or SAML). This way, the user logs in only once to the identity provider.
-![LDAP with SSO diagram](media/ldap-sso-diagram.svg)
+
{{< /switch-box >}}
{{< switch-box title="SSO" >}}
On modern web infrastructure, LDAP started to be abandoned because **loose provisioning can also be done via SSO protocols.**
-![SSO only diagram](media/sso-diagram.svg)
+
{{< /switch-box >}}
{{< switch-box title="SSO+SCIM" >}}
**SCIM solve the remaining problems** via a simple standard web api. This infrastructure is **event driven, a provisioning action on the IdP is quickly passed on all applications.**
-![SSO with SCIM diagram](media/sso-scim-diagram.svg)
+
{{< /switch-box >}}
| | LDAP | LDAP & SSO | SSO | SSO & SCIM |
diff --git a/content/overview/identity-management.md b/content/overview/identity-management.md
index 9d1b42c..27f5921 100644
--- a/content/overview/identity-management.md
+++ b/content/overview/identity-management.md
@@ -4,7 +4,13 @@ description : "What we speak about and in **which environment**. We must agree o
color : yellow
weight : 1
---
-![basics of identity management](media/illus-basics.svg)
+
+
+
+
{{< grid >}}
{{< card icon="user" >}}
#### Authentication
@@ -26,7 +32,7 @@ Where are user’s identity & credentials stored?
How to manage & transfer user’s identity ?
{{< /card >}}
{{< /grid >}}
-
+
### Our environment
Our digital work environment is composed of **many applications** and web services. We want a **seamless user experience** for our free software based collaboration platform. With a **Single Sign-on (SSO)** system users get a unified login and logout experience but there is a catch.
diff --git a/static/media/illus-home.svg b/static/media/illus-home.svg
new file mode 100644
index 0000000..cce19ca
--- /dev/null
+++ b/static/media/illus-home.svg
@@ -0,0 +1,153 @@
+
diff --git a/static/media/small/illus-basics.svg b/static/media/small/illus-basics.svg
new file mode 100644
index 0000000..5402a5e
--- /dev/null
+++ b/static/media/small/illus-basics.svg
@@ -0,0 +1,288 @@
+