Note Organization System
This vault works best as a small linked knowledge base, not as a folder-only archive.
Note Types
| Type | Purpose | Example |
|---|---|---|
| Home | main entry point | Home |
| Map | organizes a topic or course | UID 07 - Course Map, JavaScript |
| Course note | notes from one class or lecture | UID 07 - Introduzione al corso |
| Concept note | reusable idea | Design System, Style Tile |
| Tool note | software or tool | Figma, Webflow |
| Atomic note | one small topic | Async&Await, Class in JS |
Linking Rules
Use a link when the topic is important enough to become reusable later.
Good links:
- core concepts: Design System, User Interface Design
- tools: Figma, Webflow
- course maps: UID 07 - Course Map
Avoid linking every small word. Too many empty links make the graph noisy.
Empty Links
Empty links are okay when they mean “I plan to write this note later.”
Keep empty links for:
- important concepts
- project outputs
- future study topics
Do not keep empty links for:
- random vocabulary
- one-time examples
- topics you do not plan to revisit
Recommended Workflow
- Put new course notes into a course map.
- Extract reusable ideas into concept notes.
- Link project work to the concepts that support it.
- Review unresolved links weekly and create only the useful ones.
- Keep one main entry point: Home.
Naming Pattern
| Category | Pattern |
|---|---|
| Course notes | UID 07 - Lesson Name |
| Concept notes | simple noun phrase, e.g. Design System |
| Tool notes | tool name, e.g. Figma |
Current Cleanup Rule
For now, do not move files into many folders. The vault is small enough that links and map notes are more useful than heavy folder structure.