<h1 id="note-naming-tips">Note Naming Tips<a aria-hidden="true" class="anchor-heading icon-link" href="#note-naming-tips"></a></h1>
Tips for naming notes (see <a href="/notes/0j9jbeegeekkgh3facwp5tq">Note Name</a>):
<ul>
<li>
Keep top-level hierarchy items short and expand naming as you go deeper.
<ul>
<li>This is currently necessary due to VSCode quick pick limitations, which require truncating search results. See <a href="/notes/n44yr1mk4wfgkbqeprbeef9">thorg.visualPreferences.vsc.quickPick.maxLabelLength: Max Length of VSCode Quick Pick Labels (Before Truncation)</a> to adjust the truncation length.</li>
</ul>
</li>
<li>
Use singular naming for all notes, including parent notes that contain groups or lists. While plural naming works technically (similar to namespace design in code), singular naming creates a more visually cohesive and readable structure throughout your system.
<ul>
<li>Examples:
<ul>
<li>Use "Project" instead of "Projects" for a parent note containing multiple projects</li>
<li>Use "Task" instead of "Tasks" for a note grouping several tasks</li>
</ul>
</li>
<li>Concrete example:
<ul>
<li>✅ <code>tech.bash.lang.shell-variable.RANDOM</code></li>
<li>❌ <code>tech.bash.lang.shell-variables.RANDOM</code></li>
</ul>
</li>
</ul>
</li>
<li>
Don't overthink it. You can refactor later when you have more context.
</li>
</ul>