Title: Support Markdown (.md) document preview like PDFs
Summary
Please add native preview support for attached Markdown (.md) files in Workflowy, similar to the existing PDF preview. The goal is to be able to click an attached .md file and see a rendered view (headings, lists, code blocks, etc.) without leaving Workflowy.
Problem / Pain Point
-
Workflowy already renders Markdown nicely when pasted as text, but
.mdfiles are treated as generic attachments. -
Many of us keep documentation, notes, and specs as Markdown files in Git repos or local folders.
-
Today, if we attach those
.mdfiles to a Workflowy node, we can’t preview them in context—we have to download/open them in another app, breaking flow and losing the inline “document” feel that PDFs currently have.
Requested Behavior
For attached .md files:
-
Inline preview
-
Clicking a
.mdattachment opens a rendered Markdown view in an overlay (just like PDF preview). -
Basic formatting: headings, lists, bold/italic, links, images, code blocks, tables.
-
-
Toggle view
- Optional: a small toggle or button to switch between rendered view and raw
.mdtext for quick editing / copy-paste.
- Optional: a small toggle or button to switch between rendered view and raw
-
Consistent UX with PDFs
-
.mdattachments show a recognizable icon and filename. -
Clicking opens a scrollable preview overlay, with “open / download” options, mirroring the existing PDF experience.
-
Why this matters
-
Keeps Workflowy as the “hub” for projects while allowing Markdown to remain the canonical format in code / docs repos.
-
Great for technical users who write everything in Markdown but organize work in Workflowy.
-
Avoids constant context-switching between Workflowy and external editors just to read attached docs.
Nice-to-have (future) ideas
-
“Open in external editor” shortcut for
.mdattachments. -
Option to paste or drag a
.mdfile and choose: “attach as file” vs. “import as rendered Markdown text.”
Thanks for considering this—Markdown is already a big part of Workflowy’s editing experience; extending that to file preview would make it a much stronger home for technical and documentation-heavy workflows.