admin/goodgo-platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(docs): consolidate 22 audit files from root into docs/audits/

Browse Source 
Root directory had accumulated audit/exploration markdown files cluttering
the project root. Moved all audit-related files to docs/audits/ with a
README.md index, and updated cross-references in K6_LOAD_TESTING_GUIDE.md
and README_FRONTEND_DOCS.md.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
Ho Ngoc Hai
2026-04-10 23:16:00 +07:00
parent 68b65cb848
commit 59272e9321
26 changed files with 8500 additions and 189 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README_FRONTEND_DOCS.md
View File

@@ -21,7 +21,7 @@ High-level summary of findings:
---
#### 2. **FRONTEND_EXPLORATION.md** 📋 DETAILED REFERENCE
#### 2. **docs/audits/FRONTEND_EXPLORATION.md** 📋 DETAILED REFERENCE
**45-minute read | Comprehensive analysis**
Extremely thorough breakdown:
@@ -102,7 +102,7 @@ Organized by file complexity:
### Scenario 3: I'm a Developer Implementing i18n
1. Quickly scan **EXPLORATION_SUMMARY.txt** (5 min)
2. Deep dive **FRONTEND_EXPLORATION.md** sections relevant to your task
2. Deep dive **docs/audits/FRONTEND_EXPLORATION.md** sections relevant to your task
3. Use **FILE_MAPPING_GUIDE.md** as step-by-step instructions
4. Reference code examples and pseudo-code provided
@@ -242,7 +242,7 @@ The docs reference:
If you're new to this codebase:
1. Start with **EXPLORATION_SUMMARY.txt** for overview
2. Read **FRONTEND_EXPLORATION.md** section "Directory Structure Overview"
2. Read **docs/audits/FRONTEND_EXPLORATION.md** section "Directory Structure Overview"
3. Understand the App Router structure
4. Review current component patterns
5. Then start implementation with **FILE_MAPPING_GUIDE.md**