Markdown readers fight awkward preview and file navigation
People reading Markdown in editors often have to take extra steps to see rendered content, and switching among files can close or replace documents they meant to keep open. Some also want a safe, read-only way to follow links and read files without accidental edits. Existing workflows vary by editor and platform, leaving users to work around missing preview, tab, and packaging behavior.
For markdown readers and developers browsing project documentation. Mentioned from Feb 2016 to Apr 2026 on GitHub, Hacker News and Stack Exchange.
10 different people described this problem in 6 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 4.8/10
- Frequency
- 8.6/10
- Willingness to pay
- 0.0/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.
I love this for markdown, but I'm afraid it's not going to be used for much longer if I can't have more than one file open in the same window
I just got annoyed by this behaviour of closing files - I evidently wanted to have opened - for the 451th time in the last two weeks
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
- 8 more quotes from people who have this problem
- Current workarounds, existing solutions and risks