Merge branch 'mkdocs_material' into 'master'

update relative path in md files

See merge request refonte-data/documentation!3

docs/architecture/cms.md

@@ -4,7 +4,7 @@ For all the editorial content on the portal one CMS is used to offer the possibi
 
 ## Ghost: headless CMS
 
-![ghost-logo](/docs/assets/ghost-logo.png)
+![ghost-logo](../assets/ghost-logo.png)
 
 The choice went for the open source CMS [Ghost](https://ghost.org/), replacing Wordpress as our first choice at the beginning of the project.  
 Whereas it's not perfect and there is still room for improvement, this is a great tool to use to create content in a beautiful user interface. The API allows us to get all the information needed for the web application by a REST API.

docs/architecture/services/authentication.md

@@ -13,7 +13,7 @@ This service also provides endpoints to retrieve and update a user profile.
 
 ## How it works
 
-![authentication-service](/docs/assets/authentication-service.png)
+![authentication-service](../../assets/authentication-service.png)
 
 The entrypoint of the service is a REST API provided by a [NestJS](https://github.com/nestjs/nest) application. It depends on two other services:
 

docs/architecture/services/organizations.md

@@ -8,7 +8,7 @@ In our application, one organization is usually a provider of data, used in the
 
 ## How it works
 
-![organizations-service](/docs/assets/organizations-service.png)
+![organizations-service](../../assets/organizations-service.png)
 
 The entrypoint of the service is a REST API provided by a [NestJS](https://github.com/nestjs/nest) application. This backend application interacts with a PostgresSQL database through an ORM called [TypeORM](https://github.com/typeorm/typeorm).