Skip to content

MOC (Map of Content) Pattern

The MOC (Map of Content) Pattern is a method for organizing and structuring content, particularly within personal knowledge bases or note-taking systems. It functions as a curated hub that aggregates links to related materials, serving as a navigational entry point for a specific subject or domain.^[600-developer__tools__windows__000-MOC-windows.md]

Structure and Syntax

In markdown-based implementations, a Map of Content typically serves as the primary index for a directory or topic. It generally consists of a list of links, often formatted as bullet points, that point to specific child notes or sub-resources^[600-developer__tools__windows__000-MOC-windows.md].

A common naming convention for these files is to prefix the filename with 000-MOC- followed by the topic name (e.g., 000-MOC-windows.md)^[600-developer__tools__windows__000-MOC-windows.md]. This lexical naming scheme ensures that the index appears at the top of file listings, making it the default starting point for exploration.

Purpose and Function

The primary purpose of an MOC is to provide a "Table of Contents" or a dashboard for a specific context. It allows users to:

  • Centralize Access: Aggregate disparate notes into a single, manageable view^[600-developer__tools__windows__000-MOC-windows.md].
  • Facilitate Navigation: Serve as a jumping-off point for exploring detailed sub-pages, such as installation guides, command records, or specific tool configurations^[600-developer__tools__windows__000-MOC-windows.md].
  • Maintain Order: Organize technical documentation or knowledge clusters (e.g., a collection of Windows or WSL related notes) without enforcing a rigid physical hierarchy on the individual files themselves^[600-developer__tools__windows__000-MOC-windows.md].

Sources

^[600-developer__tools__windows__000-MOC-windows.md]