Skip to content

Target-system presets

Some platforms have specific requirements for Markdown formatting, file structure, or metadata. Adjust the export configuration to optimize output for your target system. Below are some common presets.

Obsidian

Run the following command to configure the exporter for Obsidian:

cme config set \
  export.include_document_title=false \
  export.page_breadcrumbs=false \
  export.page_href=wiki \
  export.attachment_href=wiki \
  export.page_properties_format=meta-bind-view-fields \
  export.page_properties_report_format=dataview

Obsidian natively renders the document title and page breadcrumbs, so both are disabled to avoid redundant output. Wiki-style links ([[Page Title]] and ![[attachment.png]]) are used so Obsidian can resolve links by title across the vault without depending on the file system path.

meta-bind-view-fields writes all page properties to YAML front matter and replaces the property table with inline `VIEW[{key}][text]` fields. dataview replaces frozen Page Properties Report snapshots with live Dataview DQL queries that re-evaluate across your vault.

Plugin Purpose
Dataview Query and display page metadata across the vault; powers the Page Properties Report DQL queries
Meta Bind Renders the exported VIEW[{key}][text] fields as live, readable values inline in the page body; works alongside Dataview
Highlightr Renders the colour highlights exported from Confluence text highlights
Folder Notes Opens the page note when clicking a folder, mirroring Confluence's page-as-folder structure

:::note Wiki links resolve by page title. If multiple pages share the same title across spaces, Obsidian may link to the wrong file. In that case, omit export.page_href=wiki and use relative or absolute links instead. :::

:::note Dataview report queries only work correctly if all referenced child pages are also exported and their page properties are available as front matter. :::

Azure DevOps (ADO) Wikis

Run the following command to configure the exporter for ADO Wikis:

cme config set \
  export.attachment_href=absolute \
  'export.attachment_path=.attachments/{attachment_file_id}{attachment_extension}' \
  'export.filename_encoding={" ":"-","\"":"%22","*":"%2A","-":"%2D",":":"%3A","<":"%3C",">":"%3E","?":"%3F","|":"%7C","\\":"_","#":"_","/":"_","":"_"}' \
  export.filename_length=200

ADO Wikis require absolute attachment links and expect attachments in a specific .attachments/ folder. Filenames are sanitized to match ADO's restrictions: spaces become dashes, dashes are percent-encoded, and other forbidden characters are replaced with underscores. The filename length is capped to stay within ADO's limits.