Maps of Content

by mkshp-dev
5
4
3
2
1
Score: 35/100
New Plugin

Description

This plugin has not been manually reviewed by Obsidian staff. Dynamically generate Maps of Content (MOC) by extracting matching list items from notes in your vault.

Reviews

No reviews yet.

Stats

stars
14
downloads
0
forks
0
days
NaN
days
NaN
days
0
total PRs
0
open PRs
0
closed PRs
0
merged PRs
0
total issues
0
open issues
0
closed issues
0
commits

Latest Version

Invalid date

Changelog

README file from

Github

Maps of Content

This plugin provides a dynamic way to extract elements (like lists, tasks, headings, paragraphs, or blockquotes) from your Markdown files that match a specific word filter, automatically generating Map of Content (MOC) indexes in your vault.

It accomplishes this by adding a new moc markdown code block processor.

How to use

In any of your notes, add a code block with the language set to moc and provide a YAML-based configuration.

Here is an example:

Configuration Options

  • folder (required): The folder path within your vault to search for files. E.g., Diary or Notes/Meetings.
  • element (required): The type of element to extract. Can be set to List, Task, Heading, Paragraph, or Blockquote.
  • filter (required): The filter condition to apply to each element. Supported formats include:
    • has_word("word") or contains("text") or has_text("text"): Matches elements containing the exact text.
    • matches("regex"): Matches elements using a regular expression.
    • has_tag("#tag"): Matches elements containing the specified tag.
    • is_completed(): Matches only completed tasks (when element is Task).
    • is_incomplete(): Matches only incomplete tasks (when element is Task).
  • recursive (optional): A boolean (true or false) that determines whether the search should include subfolders within the specified folder. If omitted, it defaults to false.

Result

The plugin will scan all markdown files in the specified folder. For any files containing elements that match your filter, it will dynamically render a section.

The rendered output includes:

  1. A header with a link back to the source file where the elements were found.
  2. The matching elements themselves.

Note: The original moc code block is replaced in reading/preview mode with the dynamically generated content.