- fix stage-numbering conflict (README vs 05-Progress) and unify stage-1 reading scope - resolve AWS workshop prerequisite contradiction in 04-Reference/01 - convert medium-path wikilinks to vault-root paths (~30 links), fix .pyy typos, annotate ragas fork, unify archive status, add 01-/02- README hubs - compress old-version guidebook notes (01, 05) into pointers; add 2026 reading guidance to 00-Overview - dedupe project templates and remove embedded template copy in 03-Practice/README
Projects
Purpose: Time-bound initiatives with clear completion criteria.
What is a Project?
A project has:
- A specific goal or deliverable
- A clear end date or completion criteria
- Multiple tasks or actions
Examples: Writing a paper, launching a product, planning an event, learning a new skill
Recommended Structure
For each project folder, create:
Research/- Source materials and referencesDrafts/- Work in progressOutput/- Final deliverablesREADME.md- Project objectives, timeline, and status
Project Lifecycle
- Start: Create folder with subfolders and README
- During: Keep all related materials in the project folder
- Complete: Create summary note, then move to
04_Archive/
Active Project Folders
Tips
- Link to relevant Areas and Resources
- Commit regularly to track progress with git
- Review weekly to check status and next actions