A practical library for files that have to outlive the project.
River Folder publishes field-tested guides, reusable templates, and a worked workspace for organizing, delivering, and archiving real-world project files.
Start here
Choose the problem you need to solve today.
- 01
Intake
Capture what arrives. Make it findable before making it perfect.
- 02
Active
Keep current work visible, named, and owned.
- 03
Deliver
Package final outputs with enough context to use them.
- 04
Archive
Preserve what matters and remove everything else.
Latest guides
View all guidesAllNamingOrganizingHandoffArchive
DOCA naming pattern that scales with a projectNaming6 min read→
DOCA field guide to cleaning a messy project folderOrganizing8 min read→
DOCBuilding a handoff package people can trustHandoff7 min read→
DOCArchiving for the long termArchive9 min read→
DOCWrite a project README that remains usefulDocumentation5 min read→
Worked_Example/
|-- 00_about_this_workspace.md
|-- 01_intake/
| |-- inbox/
| `-- notes/
|-- 02_active/
| |-- planning/
| |-- research/
| `-- work/
|-- 03_deliver/
| |-- outputs/
| `-- handoff/
`-- 04_archive/
|-- final/
`-- reference/
This example follows one project from raw source material to final deliverables. Every folder has a role, every durable file has context, and the archive has an inventory.
- Real filenames and folder rules
- A complete handoff index
- Clear review statuses
- An archive that explains itself
Templates
Plain files you can use as-is or adapt.
