windyboy
8e3943f064
- Created CLAUDE.md configuration file - Created WEEKLY_REVIEW.md template - Set up PARA folder structure (Projects, Areas, Resources, Archive) - Created README files for each main folder - Configured .gitignore for vault files - Saved vault configuration to .claude/vault-config.json Generated with Claude Code Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
38 lines
1.0 KiB
Markdown
38 lines
1.0 KiB
Markdown
# Archive
|
|
|
|
**Purpose:** Completed or inactive items from Projects and Areas.
|
|
|
|
## What Gets Archived
|
|
|
|
- **Completed projects** - Move entire project folder here
|
|
- **Inactive areas** - Areas you're no longer maintaining
|
|
- **Old resources** - Outdated reference materials (use sparingly)
|
|
|
|
## Archive Structure
|
|
|
|
Maintain the same folder structure:
|
|
- `Projects/` - Completed project folders
|
|
- `Areas/` - Inactive areas
|
|
- `Resources/` - Outdated resources (if needed)
|
|
|
|
## Before Archiving a Project
|
|
|
|
1. Create a project summary note with:
|
|
- What was accomplished
|
|
- Key learnings
|
|
- Links to important outputs
|
|
2. Update related Area notes
|
|
3. Move the entire project folder here
|
|
|
|
## Maintenance
|
|
|
|
- Review quarterly to see what can be deleted
|
|
- Some archived items may be reactivated
|
|
- Keep the archive organized (mirror active structure)
|
|
|
|
## Tips
|
|
|
|
- Don't archive too aggressively - keep valuable reference material
|
|
- Use git history to track when things were archived
|
|
- Archived doesn't mean forgotten - you can still search and reference
|