Unfortunately the results from direct export don’t look as good as from pandoc.
Probably about 90% of the time for composing and viewing. Also it’s my preferred capture format for web clips, although sometimes that doesn’t work well and I switch to RTF or another format. I do convert to PDF occasionally, usually to share it with others. Once converted to PDF, I’ll delete the MD file and assets.
1 Like
Beauty is subjective 
Only composing and viewing, but I’m mostly viewing when I can’t see something in the editor, like transclusions, or it’s too bad to see in the editor like tables. If I could see everything in the editor, even not as beautiful as in the viewer, I think I would spend my time mostly using the editor.
Are you unaware you can export a Markdown document to Word via File > Export > as Word 2007 Document (DOCX)?
I am aware of this, but using pandoc gives you a lot of control of the template used and how the docx looks.
Currently, I’m mostly viewing. I’m only one step away from moving my full editing workflow to DEVONthink: resolving the RTL (Arabic) text direction challenge in the editor. I hope to see this addressed in the upcoming versions.
Almost all my Claude project work output is generated in markdown to be stored in DEVONthink and sometimes in the relevant Claude project folder.
When I need to have content formatted for printing to read or share, Claude has a set of format instructions for Word, which then can have the word formatted content printed directly and/or saved as pdf.
These alternate formats are usually also put back into DEVONthink for future reference and use.
Lots of composing and viewing, yes, but over the past few years I’ve also been exporting more and more PDFs directly from MD when I need to produce simple documents for others to read for my work, and I love the simplicity of the whole process. To be honest, though, when I need to export PDFs, I open the MD docs from DT into iA Writer and export from there—result just looks more attractive to my eye (yes, it’s subjective) 
.
1 Like
Mostly viewing with a little tweaking. I mostly edit in iA Writer.
1 Like
Same here!
Composing and viewing the rendered Markdown directly in DT, printing to pdf and exporting via Marked 2. A useful setup for my master thesis 
.
2 Likes
Markdown is so embedded in almost everything I do, that almost every export that is not an image started life in markdown. I don’t know percentages, but I do know that less than 1% of my document creation time monthly is spent in .docx, .pages, or any other old-school document app.
2 Likes
I’ve always used Ulysses for composing, DT for viewing and Ulysses for export. With the latest DT and DTTG I am moving more and more to composing and viewing. The templating for export in Ulysses keeps me there for export because I have made several custom style sheets over the years that I don’t want to redo (not sure how onerous that task is).
1 Like
I use a custom CSS and view rendered markdown in DT. Most of the time I edit in BBEdit, sometimes I edit in DEVONthink. I can’t think of a time I exported to a different format.
2 Likes
I create Markdown documents in DEVONthink and keep the view set to View → Preview → Standard. This lets me edit the Markdown directly while still seeing the formatted output.
I migrated from Evernote after dealing with a bloated database that was locked inside their proprietary format. Now I use MD whenever possible to keep my databases as small as possible.
1 Like
Welcome @trsands and thanks for participating!
When writing in DT, I often, say 70-80%, use Dual Pane. At one time or the other, say 90%, I render the finished document.
About 20% of the time I convert to PDF, almost exclusively. I use Marked for this
2 Likes
Almost always just composing and viewing, with the twin-pane option.
I often open documents in Typora, which is what I use for occasional PDF exports. For docx it’s Pandoc, but I can’t remember the last time I needed that.
1 Like
Composing and viewing the rendered Markdown. I’ll only convert it based on the client request.
1 Like
- I index my Obsidian vault(s) (and Claude Cowork projects) in DT and do most composing in VScode and/or Obsidian - very little of it in DT.
- When I want to export, I use Marked by Terpstra
FWIW: I’ve preferred Markdown (syntax and files¹) for many years now, and is proving to be a the most flexible and portable solution. Same folders, files and syntax used by DT, Obsidian, VScode, Claude, and soon to be “synced” to GitHub.
1 — I have not had pleasant experiences with apps that use Markdown syntax and rendering but store the content in some sort of custom datastore
1 Like