diff --git a/EVS-Client/release-note.md b/EVS-Client/release-note.md
index fa65b231f69450b18760ba88156b0d92d17adde2..accbdf55013a01cc3d66eb19b1eadc61095a4dc0 100755
--- a/EVS-Client/release-note.md
+++ b/EVS-Client/release-note.md
@@ -10,6 +10,7 @@ reference: KER1-RNO-IHE-EVS_CLIENT
 ---
 
 ## Message-Content-Analyzer 3.1.0
+
 _Release date: 2023-07-11_
 
 Step 1 of Gazelle User Management renovation.
@@ -17,6 +18,7 @@ Step 1 of Gazelle User Management renovation.
 Integration of new version (2.0.0) of sso-client-v7.
 
 # 6.3.0
+
 _Release date: 2023-07-11_
 
 Step 1 of Gazelle User Management renovation.
diff --git a/Gazelle-SSO/installation.md b/Gazelle-SSO/installation.md
index 0ef006ba8e52ee455e7e4badc010591ce6435708..d3a28590c76c5176b6638818861e27585abf78e4 100755
--- a/Gazelle-SSO/installation.md
+++ b/Gazelle-SSO/installation.md
@@ -11,93 +11,15 @@ reference: KER1-MAN-IHE-SSO_INSTALLATION-1_03
 customer: IHE-EUROPE
 ---
 
-# Gazelle Keycloak CAS 21.0.1 Installation Manual
-
-## Prerequisites
-
-Installation needs to be performed on a Debian linux __Stretch__ or newer. This SSO is used by Gazelle tools to authenticate users.
-A PostgreSQL instance is required to store the data of the SSO. 
-Two databases are used by the SSO. One is for keycloak and the other one is the Gazelle TM database used to get the list of users and their group and roles.
-
-# Installation
-
-## 1. Retrieve a keycloak docker image
-
-Browse the following URL to get the correct docker image of Keycloak : https://quay.io/repository/keycloak/keycloak.
-
-Gazelle integration works with version 21.0.X.
-
-Example of commands to download the image :
-
-```bash
-docker pull quay.io/keycloak/keycloak:21.0.1
-```
-
-## 2. Get jar file to provide it to keycloak
-
-Download the file named `gazelle-user-management.jar`from the following URL : https://gazelle.ihe.net/nexus/service/local/repositories/releases/content/net/ihe/gazelle/keycloak-provider
-
-The jar must be placed in the folder `/opt/keycloak/providers/`.
-
-
-## 3. Configure a realm for Gazelle
-
-A JSON configuration file is required to correctly configure the Gazelle realm. This file must declare all the configurationS of the realm.
-
-The list of configuration to set in the file : 
-
-- Global configuration (realm name, user auth flow)
-- The list of clients allowed to use the SSO
-- The list of roles
-- The list of protocol mappers
-- The SMTP configuration
-- Brute force protection configuration
-- Event listeners configuration
-- Theme for the login page and emails
-
-An example of this file available in the source code repository of Gazelle User Management [here](https://gitlab.inria.fr/gazelle/applications/gazelle-user-management/-/blob/master/keycloak-provider/realm-gazelle.json).
-
-## 4. Set environment variables
-
-There are variables that must be given to the docker container in order to deploy the application correctly.
-
-| Name                      | Description                                      | Value Example                 |
-|---------------------------|--------------------------------------------------|-------------------------------|
-| DB_KC_USER                | Postgres database user for Keycloak              | gazelle                       |
-| DB_KC_PASSWORD            | Postgres database password for Keycloak          |                               |
-| DB_KC_HOST                | Postgres database hostname for Keycloak          | localhost                     |
-| DB_KC_PORT                | Postgres database port for Keycloak              | 5432                          |
-| DB_KC_NAME                | Postgres database name for Keycloak              | keycloak                      |
-| DB_TM_USER                | Postgres database user for TM                    | gazelle                       |
-| DB_TM_PASSWORD            | Postgres database password for TM                |                               |
-| DB_TM_HOST                | Postgres database hostname for TM                | localhost                     |
-| DB_TM_PORT                | Postgres database port for TM                    | 5432                          |
-| DB_TM_NAME                | Postgres database name for TM                    | gazelle                       |
-| DEBUG                     | Enable keycloak remote debug mode                | false                         |
-| DEBUG_PORT                | Set keycloak debug port                          | *:18787                       |
-| GAZELLE_TM_URL            | Gazelle TM instance url                                   | http://localhost:8080/gazelle |
-| KC_ADMIN_CLIENT_SECRET    | The secret for the admin-cli client              | secret                        |
-| KC_CLIENTS_ADMIN_EMAIL    | The email of the user with manage-client role    | Default: indus@kereval.com    |
-| KC_CLIENTS_ADMIN_USERNAME | The username of the user with manage-client role | gazelle-clients-admin         |
-| KC_CLIENTS_ADMIN_PASSWORD | The password of the user with manage-client role | password                      |
-| ROOT_TEST_BED_URL         | Test bed root url                                | http://localhost              |
-
-There are aditional variables that can be set to configure the keycloak server.
-
-Refer to the [keycloak server configuration documentation](https://www.keycloak.org/server/all-config) for more information.
-## 5. Start keycloak
-
-When all the configurations are ready, you can start keycloak with the image of keycloak you retrieved previously.
-
-Don't forget to mount a volume for /opt/keycloak to provide the different configurations files to keycloak
-
-At the first start, keycloak will create the database and the admin user. It will automatically import the realm configuration file.
+# [DEPRECATED] Apereo CAS 5.1.X Installation Manual
 
-Check the logs to follow the progress of the deployment.
-When it's deployed, you can access to the admin console with the admin user and the password you set in the environment variables. You must check the good configuration of the Gazelle realm.
+{% capture sso_alert %}
+Gazelle SSO, formerly Gazelle CAS, is deprecated since 2023-07-17. The replacement is a new 
+authorization server that is part of Gazelle User Management. 
+<a href="https://doc-ihe.kereval.cloud/gazelle-applications/v/gazelle-user-management/">See its documentation</a>.
+{% endcapture %}
 
----
-# [DEPRECATED] Apereo CAS 5.1.X Installation Manual
+{% include warning.html content=sso_alert %}
 
 The purpose of this document is to guide you through the installation process of the Apereo CAS 5.1.X. This SSO is used by Gazelle tools to authenticate users.
 
diff --git a/Proxy/installation.md b/Proxy/installation.md
index 8efeead17cd77959cddb762fa6ed49a1d2dfa68c..c425358ec33e05fdaa4cf5c5603cc2139a608fa7 100755
--- a/Proxy/installation.md
+++ b/Proxy/installation.md
@@ -88,6 +88,7 @@ sudo /etc/init.d/jboss7 start
 ```bash
 psql -U gazelle gazelle-proxy < schema-X.X.X.sql
 ```
+
 ## 8.  Execute the sql script available in your workspace at gazelle-proxy-ear/src/main/sql/init-5.0.0.sql
 
 ```bash
@@ -96,7 +97,7 @@ psql -U gazelle gazelle-proxy < init-X.X.X.sql
 
 ## 9. Browse the application
 
-Open your favorite browser (we recommend Chrome or Firefox) and go to [*http://yourServer:8080/proxy*](http://yourServer:8080/proxy)
+Open a browser and go to [*http://yourServer:8080/proxy*](http://yourServer:8080/proxy)
 
 ## 10. The proxy is now up and running, see the next section for information on the configuration.
 
diff --git a/Test-Management/release-note.md b/Test-Management/release-note.md
index a49bdd9c3fb364c4902d8d0dc9a7f27f085fc619..7f26f28f23284f775b05b24a58dc9baffbbbfdf4 100755
--- a/Test-Management/release-note.md
+++ b/Test-Management/release-note.md
@@ -10,6 +10,7 @@ reference: KER1-RNO-IHE-TEST_MANAGEMENT
 ---
 
 # 7.0.0
+
 _Release date: 2023-07-12_
 
 Step 1 of Gazelle User Management renovation. 
@@ -40,7 +41,9 @@ __Bug__
 * \[[GZL-5217](https://gazelle.ihe.net/jira/browse/GZL-5217)\] DIGIT_Unable to edit Monitor test assignment
 
 # 6.10.3
+
 _Release date: 2023-06-01_
+
 __Sub-task__
 * \[[GZL-5126](https://gazelle.ihe.net/jira/browse/GZL-5126)\] Show statistics about SUT network interfaces for testing session managers and administrators
 
diff --git a/_templates/jekyll-gazelle-documentation/_includes/warning.html b/_templates/jekyll-gazelle-documentation/_includes/warning.html
new file mode 100644
index 0000000000000000000000000000000000000000..ed1e9508a5b9d32eb29b4761d4691c5d69bb3d2d
--- /dev/null
+++ b/_templates/jekyll-gazelle-documentation/_includes/warning.html
@@ -0,0 +1,3 @@
+<div class="alert alert-warning" role="alert">
+    <i class="fa fa-warning"></i>{{ include.content }}
+</div>
diff --git a/_templates/jekyll-gazelle-documentation/static/fonts/fontawesome-webfont.ttf b/_templates/jekyll-gazelle-documentation/static/fonts/fontawesome-webfont.ttf
new file mode 100644
index 0000000000000000000000000000000000000000..d7994e13086b1ac1a216bd754c93e1bccd65f237
Binary files /dev/null and b/_templates/jekyll-gazelle-documentation/static/fonts/fontawesome-webfont.ttf differ
diff --git a/_templates/jekyll-gazelle-documentation/static/fonts/fontawesome-webfont.woff b/_templates/jekyll-gazelle-documentation/static/fonts/fontawesome-webfont.woff
new file mode 100644
index 0000000000000000000000000000000000000000..6fd4ede0f30f170eecb4156beb7235bf01fff00b
Binary files /dev/null and b/_templates/jekyll-gazelle-documentation/static/fonts/fontawesome-webfont.woff differ
diff --git a/_templates/jekyll-gazelle-documentation/static/fonts/fontawesome-webfont.woff2 b/_templates/jekyll-gazelle-documentation/static/fonts/fontawesome-webfont.woff2
new file mode 100644
index 0000000000000000000000000000000000000000..5560193ccc5d768df40766ba54491f1822ed683c
Binary files /dev/null and b/_templates/jekyll-gazelle-documentation/static/fonts/fontawesome-webfont.woff2 differ