Differences

This shows you the differences between two versions of the page.

--- fxdemo:05-part:07-naming-and-file-conventions:07-2-directory-naming:start [2026/08/09 17:19] – created owen
+++ fxdemo:05-part:07-naming-and-file-conventions:07-2-directory-naming:start [2026/08/09 17:21] (current) – owen
@@ Line 11: / Line 11: @@
 Representative directory names include:
-  - ''docs/''
+  docs/
-  - ''idl/''
+  idl/
-  - ''src/''
+  src/
-  - ''generated/''
+  generated/
-  - ''config/''
+  config/
-  - ''scripts/''
+  scripts/
-  - ''containers/''
+  containers/
-  - ''tests/''
+  tests/
-  - ''logs/''
+  logs/
-  - ''evidence/''
+  evidence/
-  - ''tools/''
+  tools/
 Subdirectories should refine the parent directory's purpose. For example:
-  - ''src/control-plane/''
+  * ''src/control-plane/''
-  - ''src/data-plane/''
+  * ''src/data-plane/''
-  - ''config/nodes/''
+  * ''config/nodes/''
-  - ''config/qos/''
+  * ''config/qos/''
-  - ''scripts/setup/''
+  * ''scripts/setup/''
-  - ''scripts/generation/''
+  * ''scripts/generation/''
-  - ''tests/acceptance/''
+  * ''tests/acceptance/''
 Developers should not create new top-level directories without a clear [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] purpose. When the team adds a new top-level directory, it should update the Repository layout documentation and, where needed, this handbook.