Note Organization System

This vault is organized into three separated study areas:

• Design
• Coding
• Music

Home is the only global entry point. It should stay simple and should not become a full inventory of every note.

Core Structure

Area	Folder	Main map	Purpose
Design	Design	Design	UI/UX, design courses, design process, research, systems, motion
Coding	Coding	Coding	front-end development, JavaScript, browser APIs, Unity, game programming
Music	Music	Music	guitar theory and music study

Main Rule

Design, Coding, and Music should not link to each other.

Inside each area, links are encouraged when they connect real study topics. Across areas, use plain text instead of an Obsidian link.

Examples:

• In Design, write React as plain text, not [[React]].
• In Coding, write Design System as plain text, not [[Design System]].
• In Music, keep links only to music notes.

Note Types

Type	type: value	Purpose	Example
Home	home	global entry point	Home
Area map	map	top-level area navigation	Design, Coding, Music
Topic map	map	organizes a course or learning path	UID 07 - Course Map, JavaScript
Course note	course-note	notes from one class or lecture	UID 07 - Introduzione al corso
Concept note	concept	reusable idea worth revisiting	Design System, Style Tile
Atomic note	atomic	one focused coding or design topic	Async and Await, Class in JS
Project note	project	project, exercise, or game idea	JS - Practice Projects, Game Design Document
Process note	process	a phase or method within a design/dev workflow	Deep Dive, Handover
Resource note	resource	curated list of tools, links, or references	Design Resources
Meta note	meta	rules about the vault itself	Note Organization System

Both “Area map” and “Topic map” use type: map — the distinction is structural (top-level vs. within an area), not a frontmatter difference. Do not use map-of-content or atomic-note — use map and atomic.

Required Frontmatter

Every note must have frontmatter with at least:

---
type: <one of the values above>
status: active
---

status is normally active. Use other values (e.g. draft, archive) only when deliberately marking a note’s lifecycle state.

What Gets a Note

Create or keep a note when it is useful as a reusable study node.

Good candidates:

• course maps and lecture notes
• reusable design concepts
• coding topics that need examples
• project notes and checklists
• music theory topics that will grow over time

Avoid separate notes for:

• basic tool names, such as Figma, FigJam, Notion, Webflow, Spline, or Midjourney
• concepts that only have a one-line definition
• random vocabulary
• cross-area references that only create graph noise

Folder Rules

Put a note where its main use belongs:

• Design process, UX, UI, research, and visual direction go in Design.
• Implementation syntax, frameworks, APIs, and programming exercises go in Coding.
• Guitar and music theory go in Music.

If a note mixes areas, choose the area where the note will be most useful later. For example:

• Layouts and Flexbox Structuring UI belongs in Coding because it is mainly Tailwind/Flexbox implementation.
• Deep Dive belongs in Design because it describes a discovery/research phase.

Map Rules

Maps are navigation pages, not inventories.

Each area map should:

• list the important sub-maps
• group the strongest concepts
• avoid listing every tiny atomic note
• avoid links to other areas

Use Home only for the three area maps and this organization note.

Empty Links

Empty links are allowed only when they are intentional future notes.

Keep empty links for planned learning paths, such as the future topics inside 吉他乐理.

Remove empty links when they are:

• basic tools
• accidental vocabulary
• one-time examples
• cross-area links

Tags

Tags are not links, so the “Design, Coding, and Music should not link to each other” rule does not apply to them. Use tags for cross-cutting concerns that don’t belong in an Area map, e.g. #review for notes that need revisiting, or #exam for exam-relevant material.

Tags must not replace Area Map navigation — a note should still be reachable by following links from its Area map, regardless of which tags it has.

Area-Specific Rules

If an area needs a rule that doesn’t fit the general structure (e.g. how 吉他乐理 uses intentional empty links, see “Empty Links” below), add it as a short note in that area’s main map (Design, Coding, or Music) instead of expanding this document with area-specific exceptions.

Maintenance Checklist

When adding or cleaning notes:

1. Decide whether the note belongs to Design, Coding, or Music.
2. Put it in the matching folder.
3. Add frontmatter with type and status (see Required Frontmatter).
4. Link only to notes inside the same area.
5. Add it to an area map only if it helps navigation.
6. Do not create a full-vault inventory page.