diff --git a/external/integrity/naming/file_naming.md b/external/integrity/naming/file_naming.md
index 878ea253f6a3bd429b3528aff2a47eb98b9f02dc..a1cda6cbccea51248dd8cdd26a917975f47ab8d4 100644
--- a/external/integrity/naming/file_naming.md
+++ b/external/integrity/naming/file_naming.md
@@ -16,6 +16,8 @@ Good file name follows three basic principles:
 * human readable
 * plays well with default ordering
 
+If you are looking for information on how to organize and structure your folders, you may find this [dedicated card](https://howto.lcsb.uni.lu/?integrity:organization) helpful.
+
 ## Machine readable
 
 Special characters can have different meaning for different operation system or software. The most commonly found are
diff --git a/external/integrity/organization/organization.md b/external/integrity/organization/organization.md
index 05a1df10b32ff72612fef80ffe99f9284c129c4a..52df6ff462fd28ae6244597234cfbc60ed91fe54 100644
--- a/external/integrity/organization/organization.md
+++ b/external/integrity/organization/organization.md
@@ -16,6 +16,8 @@ A key rule is to name the folders with straightforward but explicit names, and t
 of where to put a given file inside the folder structure. In fact, the directory tree should in some sense
 reflect the decision tree.
 
+More details on naming files and folders are provided in the dedicated [file naming card](https://howto.lcsb.uni.lu/?integrity:naming).
+
 There are a few suggestions to organize a folder structure:
 
 ## Suggestion 1