configs

Updating obsidian/MOC.md

4 min read

The MOC (Map of Content) is the per-note index of the whole vault. Every note has a link line and a one-paragraph summary. Keep it current whenever a note is added, renamed, moved, or deleted.

Always read the current obsidian/MOC.md before editing — match the surrounding block exactly.

Top-level structure

Three # (H1) sections, separated by ---:

# Configs
…
---
# Certifications
…
---
# Studying
…

Each area groups its notes into topic wrappers (outer callouts):

AreaWrapper calloutExample
Configsone shared > [!abstract]+ Configs wrapping all topics—
Certificationsone > [!example]+ <Cert name> per certification> [!example]+ Terraform-004
Studyingone > [!tip]+ <Topic> per topic> [!tip]+ Cisco

Inside a topic wrapper

Nested one level (> >):

  1. Optional > > [!success]- Certificate with an embedded PDF (![[…pdf]]) — for certs/courses.
  2. One or more > > [!info]- <Subsection> callouts holding the link lists.
  3. A single > > [!summary]- Summaries callout holding the summary paragraphs.
> > - `CODE`<padding>— [[target|alias]]
  • CODE — a short uppercase mnemonic (3–6 chars), unique within its [!info]- block (IAC, STATE, NETS, DHCP, C/S).
  • Padding — spaces so every — in the block lines up. Pad to (longest code in block + 1 space) before —: 
    > > - `IAC`     — [[Core/1. What is Infrastructure as Code?|1. What is Infrastructure as Code?]]
> > - `INTRO`   — [[Core/2. What is Terraform?|2. What is Terraform?]]
> > - `PLUGINS` — [[Core/3. How Terraform works with plugins|3. How Terraform works with plugins]]
  • Link target — use the shortest form that is unambiguous in the vault:
    • Unique filename → bare: [[Resource Naming Convention]].
    • Name collides across folders (e.g. numbered notes) → path-qualified: [[studying/cisco/Основи роботи в мережі/1. Типи мереж|1. Типи мереж]].
    • Add |alias to control the displayed text (keep the leading number in the alias: 1. Типи мереж).

Summary paragraph format

Inside > > [!summary]- Summaries, one entry per note, separated by a blank > > line:

> > **Note Title** — One paragraph: what it covers and the key takeaways.
> >
> > **Next Note Title** — …
  • Bold title strips the leading number: file 4. Клієнти та сервери → **Клієнти та сервери**. File 1. What is Infrastructure as Code? → **What is Infrastructure as Code?**.
  • Write the summary in the note’s language — Ukrainian notes get Ukrainian summaries, English notes English. Match the tone/length of neighboring summaries (2–4 sentences, dense).
  • Order summaries to match the link-list order.

Procedure — adding a new note

  1. Locate its area (# Configs / # Certifications / # Studying) and topic wrapper. Create the wrapper if the topic is new (copy the shape of a sibling: [!tip]+/[!example]+/nested [!info]- + [!summary]-).
  2. Add the link line to the right [!info]- block, in the block’s existing order (numeric for numbered courses, otherwise logical). Pick a unique CODE. Re-pad every line in that block so the — still align after the new (possibly longer) code.
  3. Add the summary to that topic’s [!summary]- block in the same position, language-matched, number stripped from the bold title.
  4. If a whole new top-level area is needed, add a new --- + # Area section following the existing pattern.

Procedure — rename / move / delete

  • Rename/move: update the link target (and alias) and the bold summary title to match the new filename/path. Don’t touch surrounding prose.
  • Delete: remove the link line (re-pad the block) and the summary entry. Remove an emptied wrapper/section.

Worked example — add 5. Компоненти мережі under Cisco

Link line (added after the C/S line, codes re-padded — COMP fits the existing 4-wide padding):

> > - `C/S`     — [[studying/cisco/Основи роботи в мережі/4. Клієнти та сервери|4. Клієнти та сервери]]
> > - `COMP`    — [[studying/cisco/Основи роботи в мережі/5. Компоненти мережі|5. Компоненти мережі]]

Summary entry (Ukrainian, number stripped, placed after the Клієнти та сервери entry):

> > **Компоненти мережі** — Три категорії апаратних компонентів: кінцеві пристрої (хости), проміжні пристрої та мережне середовище передавання. Хости — джерело або одержувач повідомлень; ідентифікуються унікальними адресами.
> >

Verify: only the two new lines and re-padding changed; all other summaries and prose are untouched.

Graph View

Backlinks