Typewriter also has an iOS companion that's almost as feature rich as its desktop counterpart, so you can also edit your documents on the go. If you use those features, you may be better sticking with MacDown (or wait until I implement them 😀). Also Typewriter is a sandboxed app, so by design it cannot access images and other references on the file system apart from the file which is opened to do that you have to create a TextBundle file rather than pure Markdown. I have to say MacDown is still more customizable, with custom fonts and CSS styles for the preview which are not available in my app. There's an index to quickly navigate the document, paired with an Open Quickly panel which allows to select headers with the keyboard There are more shortcuts and helpers for tables and links, and easier formatting toggles (for example, you don't have to manually select a word to apply a style) The live preview has no flashes (there's an optional progress indicator for the updates, but you can disable it), and the scroll is synchronized more reliably The interface is more in line with macOS 11+ style, Despite the similarities and MacDown being open-source, there's no code in common with my app, which is written in Swift. This will cause Markdown in description tags (including implicit descriptions without tags), classdesc tags, param tags, property tags, and. I like to think of Typewriter as a more modern version of it. For most users, all you need to do is add the plugin to your JSDoc configuration (conf.json) as you would any other, by adding a reference to it in the plugins entry of the configuration JSON: Example. My app is very similar to MacDown, which actually was the editor I used the most before building my own. What would be the main benefits of switching? I’m a daily user of MacDown currently, which is rock solid for me.

More info can be found in the markdown.styles documentationįor example, add Font Awesome like this: 'markdown.Cool. You can use the built-in functionality to add custom CSS. Markdown-mermaid.languages - Configures language ids for Mermaid code blocks. Supported values are: 'base', 'forest', 'dark', 'default', 'neutral'. Markdown-mermaid.darkModeTheme - Configures the Mermaid theme used when VS Code is using a dark color theme. Markdown-mermaid.lightModeTheme - Configures the Mermaid theme used when VS Code is using a light color theme. UsageĬreate diagrams in markdown using mermaid fenced code blocks: ```mermaid Adds Mermaid diagram and flowchart support to VS Code's builtin Markdown preview and to Markdown cells in notebooks.Ĭurrently supports Mermaid version 9.3.0.

Macdown plugins