Link Search Menu Expand Document

Markdown Pod

  • id: dendron.markdown
  • coverage
    • export
    • βœ… import
    • βœ… publish

Import

Import markdown files stored locally.

The pod finds all files from the root, and copies over the files into your vault, cleaning the file names to fit dendron’s naming hierarchy. You can see an example below.

  • Original
.
└── projects
    β”œβ”€β”€ p1
    β”‚   β”œβ”€β”€ one.md
    β”‚   β”œβ”€β”€ two.md
    β”‚   └── one.pdf
    └── p2
        β”œβ”€β”€ three.md
        β”œβ”€β”€ four.md
        └── three.gif
  • After Import
.
└── vault
    β”œβ”€β”€ assets
    β”‚   β”œβ”€β”€ one-{uuid}.pdf
    β”‚   └── three-{uuid}.gif
    β”œβ”€β”€ projects.p1.md
    β”œβ”€β”€ projects.p1.one.md
    β”œβ”€β”€ projects.p1.two.md
    β”œβ”€β”€ projects.p2.md
    β”œβ”€β”€ projects.p2.three.md
    └── projects.p2.four.md

Non-markdown files within a directory will be moved into the assets folder of your vault. A uuid will be added to non-markdown file names to ensure it does not overwrite any existing files. A link of the original filenames will be made in the note that corresponds to the imported directory

...
# Imported Assets
- [one.pdf](assets/one-c91d4cb3-1db8-4703-884f-c4f5f9a00734.pdf)

Note that all files starting with a . will be ignored during the import.

If you are importing from tools like Obsidian that support wiki-links, Dendron will convert those wiki-links to Dendron’s dot based format (eg. [[project/p1]] -> [[project.p1]])

Publish

Publish Dendron Markdown to regular markdown. Convert note references and dendron specific syntax to regular markdown.