Markdown tool directory

The Markdown tool directory is a list of Markdown applications. Each page provides a brief overview of the application and a list of the Markdown syntax elements that are supported.

Ethics statement

Creating and curating this list has been a labor of love. I don't accept compensation or gifts in exchange for adding applications to this directory. I'm not affiliated with any of the developers of these applications. When necessary, I purchase licenses and subscriptions for these applications. Of course, The Markdown Guide is an open source project and I welcome pull requests from readers. Developers are welcome to submit information about their applications.

List of tools that (may) need to be documented

The Markdown tool directory is a work in progress. I've compiled a list of some applications that I think might need to be documented. This is not a comprehensive list! Feel free to add other tools.

• MarkdownPad 2
• pandoc
• Evernote
• TeXMe
• nvALT: https://brettterpstra.com/projects/nvalt/
• nvUltra (replacement to nvALT): https://nvultra.com/
• Amazon Chime - https://docs.aws.amazon.com/chime/index.html
• Taskade - https://www.taskade.com/
• Docs to Markdown - G Suite Marketplace
• GitHub - rust-lang/mdBook: Create book from markdown files. Like Gitbook but implemented in Rust
• Recheck Hugo since it started using a new Markdown processor
• Readthedocs
• Mindmapping tool markmap-lib
• dev.to
• GitHub - docsifyjs/docsify: A magical documentation site generator.
• sourcehut - https://sourcehut.org
• https://document360.io
• Tools listed on GitHub - BubuAnabelas/awesome-markdown: Delightful Markdown stuff.
• Turtl: The secure, collaborative notebook | Turtl
• GitHub - retext-project/retext: ReText: Simple but powerful editor for Markdown and reStructuredText
• Pleroma
• Discourse
• Drafts ‎Drafts on the App Store
• “Jupyter Markdown” Markdown Cells — Jupyter Notebook 6.0.1 documentation
• WriteFreely
• Wordpress Markdown quick reference cheat sheet — Support — WordPress.com
• Jetpack Why Bloggers Should Use the Markdown Online Editor
• Jupyter
• StackEdit chrome extension StackEdit Markdown Extension - Chrome Web Store
• Sublime Text
• Textmate
• GitHub - bast/cicero: Serving presentation slides written in Markdown.
• Drupal?
• 1Password
• ReadMe.io ?
• Gitter (chat / collaboration)
• Jira
• Confluence
• Basecamp?
• Atom
• VS Code Markdown editing with Visual Studio Code
• Stackoverflow (6/4/20 - they're switching to CommonMark https://meta.stackexchange.com/questions/348746/were-switching-to-commonmark)
• GitHub
  • GitHub Protips: Tips, tricks, hacks, and secrets from Lee Reilly - The GitHub Blog
• GitLab
• Jetbrains apps
• Microsoft Word?
  • http://www.writage.com
• Sharepoint
• Saleforce?
• Commento Commento: A fast, privacy-focused commenting platform
• PivotalTracker Formatting your text with Markdown
• R Markdown
• Nextcloud?
• Gatsby
• Dropbox paper? I think there is an export to Markdown option.
• Code snippet organizer for pros | Cacher
• Mochi — Forget forgetting.
• Foam
• novelWriter
• Microsoft Teams

How to test an application

This is currently pretty terrible, but I copy and paste the source of the README from my markdown-test repository into the application and see what the rendered output looks like. Something I've noticed is that different file formats (HTML/PDF/etc.) can render different output, so be sure to test and verify each of the application's export options.

Creating a page for an application

I really need to make this easier. Sorry. It's currently a very manual process. What I do is duplicate an existing tool page and work from that. You'll need to add an icon (required) and screenshot (optional) for the application.

Things to note:

• Check that the application's description in the YAML fits in the box on the application directory home page — you'll need to preview the site locally or check the Netlify staging link when you open the pull request.
• The table is HTML, so you can't use Markdown in the source there. Use HTML.
• You have to manually change the cell color to match the cell status (Yes/No/Partial). See existing pages.
• Keep the marketing text to a minimum and make sure it doesn't sound like an advertisement. People want to know briefly what the application does and whether or not it fits their needs. They can always visit the application's website if they want more information.

Open a pull request and I'll proofread it. If you need help, contact me! Thanks!