diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 2be988da91566e52496e3c70761c9e9e30667bb7..6ab7b04962b74066b6b3923407654347f517819b 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -5,9 +5,10 @@ pages:
   stage: deploy
   image: lbmc/pandoc:2.11
   script:
-    - mkdir -p public/img
+    - mkdir -p public/img public/doc/
     - make
     - cp img/* public/img/
+    - cp doc/* public/doc/
   artifacts:
     paths:
       - public
diff --git a/data_management.tex b/data_management.tex
index a0fca214439d1d307f0d7035119ac146239a366e..387f34a683800041d6e2256c7cf2fc6658aee450 100644
--- a/data_management.tex
+++ b/data_management.tex
@@ -59,6 +59,8 @@ Data Management Plans (or {\bf DMP}s) are a key element of good data management.
   \item how data will be curated & preserved (including after the end of the project).
 \end{itemize}
 
+\href{The ANR wrote a document of recommendations concerning the DMP}{https://lbmc.gitbiopages.ens-lyon.fr/hub/good_practices/doc/ANR-modele-PGD.pdf}.
+
 The {\bf DMP} may need to be updated over the course of the project whenever significant changes arise, such as (but not limited to): new data, changes in consortium policies or changes in consortium composition and external factors.
 
 We will now go over the solutions that you have access to, to store, {\bf backup}, and {\bf archive} your {\bf documents}, {\bf codes} and {\bf experimental data}.
diff --git a/doc/ANR-modele-PGD.pdf b/doc/ANR-modele-PGD.pdf
new file mode 100644
index 0000000000000000000000000000000000000000..bb87ec7643998f192560c7bc7e317a604a4922a4
Binary files /dev/null and b/doc/ANR-modele-PGD.pdf differ