From 217ba852ee00a250d46608ad0416c3c96f4c8882 Mon Sep 17 00:00:00 2001 From: laurentheirendt <laurent.heirendt@uni.lu> Date: Tue, 24 Mar 2020 17:20:42 +0100 Subject: [PATCH] add links --- external/integrity/naming/file_naming.md | 2 ++ external/integrity/organization/organization.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/external/integrity/naming/file_naming.md b/external/integrity/naming/file_naming.md index 878ea253..a1cda6cb 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 05a1df10..52df6ff4 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 -- GitLab