Implementation: How should the docs-angular scanning system handle Archive d...
Documentation for Sessions
⚙️ Implementation: How should the docs-angular scanning system handle Archive d...
📋 Decision Context
Question:
How should the docs-angular scanning system handle Archive directories?
Task: Configure docs-angular to ignore Archive/archive/Archived/archived directories in documentation system
🎯 Decision Made
Chosen:
Ignore archive directories similar to hidden and node_modules
Options Considered:
- Include archive directories in scans
- Ignore archive directories similar to hidden and node_modules
- Make archive handling configurable
- Process archives but mark as archived
💭 Reasoning
Archive directories contain historical documentation that should not appear in active navigation or search results. By ignoring them at the scan level (similar to .hidden directories and node_modules), we: (1) Reduce manifest size from 2278 to 1694 files (584 archived files excluded), (2) Improve scan performance, (3) Keep navigation clean and focused on active documentation, (4) Maintain consistency with existing patterns for ignored directories. The implementation uses case-insensitive matching (archive, Archive, archived, Archived) to catch all common naming conventions. This was implemented in all three scan scripts: scan-docs-structure.js, scan-folders-config.js, and scan-docs-visibility.js.
📁 Files Involved
apps/docs-angular/scripts/scan-docs-structure.jsapps/docs-angular/scripts/scan-folders-config.jsapps/docs-angular/scripts/scan-docs-visibility.js
🔗 Related
- Decision ID:
dev_1767879511624_ki7u9zy - Session: 29
- Workspace: editor2
Auto-generated by MCP Smart Consolidation