[misterspaceman]

I've landed on a workflow that I like a lot, and have shown to several people on my team. I use Google Drive for Desktop, which maps the G:\ drive to Google Drive. From there, I use VS Code for Markdown editing.

Google Docs now supports Markdown files, so if I need to convert the Markdown file to Word or PDF, I just open it in Docs and download it in the format I need. (Pandoc also works for this, as the author mentions). Converting HTML to Markdown can also be done in Docs: copy and paste the web page text into Google Docs, and download the file as Markdown.

For mobile, I use the DriveSync app to download my notes (Markdown) folder to my phone. Then I use Obsidian to open and edit the files.

[DidYaWipe]

But why should you need to convert it? Why does no one call out the giant problem with Markdown: the lack of READERS?

[misterspaceman]

I rarely need to convert markdown documents, but sometimes I need to produce a report for a client or a non-technical internal reader.

[DidYaWipe]

Exactly. The problem isn't converting; it's viewing.

[immibis]

People read documents, not formats.

[DidYaWipe]

Exactly. So why are we supposed to read Markdown full of embedded codes?