Importing from Dendron

When to use

When a user asks to import a Dendron workspace (a folder with dendron.yml and flat Markdown files whose names are dot-hierarchies like project.tasks.md). You own it end to end. Read limestone-vault-conventions, working-with-collections, and importing-from-obsidian (the shared mapping) first.

Run the import (one tool call)

Call limestone_import_notebook(path, collection_name) with the workspace (or vault) folder. Returns the usual summary + unconverted list.

What the tool does (Dendron specifics)

Imported like Obsidian, with these differences:

Dendron	Limestone
dot-hierarchy filename (project.tasks.task1.md)	title = frontmatter title (else the last dot-segment)
auto frontmatter created/updated (epoch ms)	Created/Updated date properties (ms auto-detected)
frontmatter id, desc, nav_order	preserved back into the note's frontmatter (a warning lists them)

Finalizing (your job)

Same playbook as importing-from-obsidian. Dendron-specific:

• The dot-hierarchy is flattened away — every note lands in one collection. If the user wants the hierarchy back, use it to group rows or split collections (the leading dot-segments name the parent topics).
• desc (Dendron's summary) is preserved in frontmatter; promote it to a text property if useful.

Evolving this skill

If a recurring Dendron structure imports badly, propose an update here or flag importers/markdown_folder.py (DendronImporter). Keep the two in sync.