Merge pull request #325 from mxenabled/wes/folderStructureADR/CT-2205

docs: added an ADR for folder structure

Author: wesrisenmay-mx

architectureDecisionRecords/0004FolderStructure.md

@@ -0,0 +1,60 @@
+# Title
+
+Folder structure
+
+## Date proposed
+
+05-14-2026
+
+## Context
+
+With our current repository structure we have the following cons:
+
+1. You must understand the language and framework to be able to find things
+1. You must dig through multiple folders to be able to get a grasp of what a single domain does
+1. It isn't obvious what works together without looking through code
+
+## Decision
+
+We will follow screaming architecture. Our folder structure will look something like the following:
+
+```
+src/
+├── Institutions/
+│   ├── Institution/
+│   │   ├── api.test.ts
+│   │   ├── api.ts
+│   │   ├── api.test.ts
+│   │   └── Institution.tsx
+│   ├── api.test.ts
+│   ├── api.ts
+│   ├── Institutions.test.ts
+│   └── Institutions.tsx
+├── Member/
+│   ├── api.test.ts
+│   ├── api.ts
+│   ├── Member.test.ts
+│   └── Member.tsx
+└── shared/
+│   ├── Member/
+│   │   ├── api.test.ts
+│   │   ├── api.ts
+│   │   ├── consts.ts
+│   │   ├── utils.test.ts
+│   │   └── utils.ts
+│   └── Validation/
+│       ├── date.test.ts
+│       ├── date.ts
+│       ├── required.ts
+│       └── required.ts
+├── vite.config.ts
+└── App.tsx
+```
+
+All folders underneath src and shared are domains. Things stay in their domain underneath src until they are actually shared, then they can move to the shared folder. Files that are used together stay in close proximity.
+
+## Consequences
+
+1. It will be easier to find things
+1. It will be easier to understand how related things work together
+1. Our folders will have a clear structure to be followed