microsoft / microsoft/markitdown

Feature Request: Add support for converting Atlassian Confluence documents to Markdown

Open
#1,715 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
186k
Forks
13.7k
Avg merge
1d 4h
Merged PRs (30d)
49

Description

Description

When passing Atlassian Confluence pages or exported Confluence content to MarkItDown, there is currently no support for converting them to Markdown. Confluence uses its own storage format (XHTML-based) with custom macros, which standard HTML converters don't handle well.

Proposal

Add native support for converting Confluence documents to Markdown, leveraging the existing open-source tool confluence-markdown-exporter as a reference or integration point.

The confluence-markdown-exporter already supports:

  • Converting Confluence pages to Markdown format using the Atlassian API
  • Handling various Confluence elements: headings, paragraphs, lists, tables, code blocks, tasks, and alerts
  • Retaining formatting such as bold, italic, and underline
  • Converting Confluence macros to equivalent Markdown syntax where possible
  • Handling images and attachments by linking them appropriately in the Markdown output
  • Supporting extended Markdown features like front matter and Mermaid diagrams
  • Supporting Confluence add-ons such as draw.io, PlantUML, and Markdown Extensions
Use Case

Many teams store documentation, design specs, and knowledge bases in Confluence. Being able to convert these documents to clean Markdown would enable:

  • Migrating documentation from Confluence to Markdown-based platforms (e.g., Obsidian, Azure DevOps Wikis, GitHub)
  • Feeding Confluence content into LLM pipelines that expect Markdown input
  • Archiving Confluence pages in a portable, version-control-friendly format
Suggested Approach
  • Integrate or reference the confluence-markdown-exporter (pip install confluence-markdown-exporter) as a converter backend
  • Support both Confluence Cloud and Confluence Server formats
  • Handle Confluence-specific macros (info panels, code blocks, status labels, etc.) gracefully
Environment
  • markitdown version: latest (pip install)
  • Python 3.13
  • macOS

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the linked confluence-markdown-exporter and compare its Confluence Cloud and Server coverage with MarkItDown's existing converter architecture. Define the supported input forms, macro handling, and integration boundary; the work is done when representative Confluence content converts to usable Markdown with coverage verified by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.