Markdown and notebook authors struggle to publish across formats
Developers, researchers, and other writers create content in Markdown, notebooks, and app-specific formats, then need to export or reuse it elsewhere. The requested workflows range from command-line conversion to static publishing, and today may require switching tools, running external commands, or copying content manually. A single product could address many of these export and automation gaps, but would need to start with a narrow set of formats and outputs.
For markdown and notebook authors. Mentioned from Jan 2016 to May 2026 on Bluesky, GitHub and Hacker News.
16 different people described this problem in 14 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 4.9/10
- Frequency
- 10.0/10
- Willingness to pay
- 2.4/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
With no support or even a commitment of support, I can no longer even recommend Typora
Currently, users who want markdown have to re-open the .ipynb file in Jupyter notebook and use its export as markdown option, or use the command line converter
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 5 places to find your first customers
- 15 more quotes from people who have this problem
- Current workarounds, existing solutions and risks