F
Folders and collections
Use Inbox, active Projects, stable Reference areas, Read later, Shared, and Archive. Limit nesting to the depth people can predict.
See the full structure →Link organizer framework
Give every important link a clear home and enough context to return.
Use a shallow collection structure, a controlled tag vocabulary, useful titles, intent notes, status, and review dates as a portable metadata layer.
Folders as locationsTags as attributesNotes as contextStatus as workflow
Minimum useful metadata
A compact record is easier to maintain
Each field should answer a different retrieval question instead of repeating the same words.
| Field | Question it answers | Example |
|---|---|---|
| Title | What is this resource? | CSS container queries — syntax and examples |
| Collection | Where does it primarily live? | Reference / Front-end |
| Reason | Why did I save it? | Use the support table during component migration |
| Tags | What attributes cross collections? | guide, approved, accessibility |
| Status | What happens next? | unreviewed, read, approved, archived |
| Review date | When could it become stale? | Quarterly for pricing; annual for stable standards |
Structure
Keep locations shallow and relationships flexible
Deep trees increase decision cost. Use collections for a primary home and tags for cross-cutting views.
T
Tags and attributes
Use action, content type, status, and recurring topics. Add a tag only when it groups multiple links and supports a real search.
Design the vocabulary →Naming formula
Concept first, source second, useful detail last.
Replace “Home,” “Docs,” or “Ultimate Guide” with a title you would search later. Put distinctive words early because interfaces truncate.
topicsourcepurposeversion when relevant
Before
“Guide”
After
Customer interview questions — discovery script for B2B onboarding
Reason
Use sections two and four before the next research call.
Maintenance
Use small reports to keep the organizer clean
A monthly audit can focus on a few high-signal views instead of inspecting everything.
Inbox age
Old unprocessed links reveal a broken capture-to-review habit.
One-use tags
Merge typos and overly specific labels or move the detail into notes.
Overused tags
Remove labels such as “resource” that retrieve most of the collection.
Stale links
Review high-risk pages, completed projects, and canonical team references.