Jump to content

Talk:Markdown

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Notable implemantations

[edit]

@Nickelpro I agree with your edit that the long disorganized list is unnecessary, but I feel like there are still pretty notable software that uses markdown, like Discord, GitHub, ChatGPT, etc. Wouldn't it be better to heavily trim down the list instead of removing it altogether? UnnecessaryDecision (talk) 20:23, 21 March 2025 (UTC)[reply]

Similar articles do not feel the need to provide long lists of software that happen to use the underlying technology. We don't have lists of applications that happen to use XML or JSON or HTML, and I don't see why Markdown is any different in that regard. WP:ENC and WP:NOTDB, this is not a dumping ground of "thing uses markdown".
I think a discussion of notable dialects of Markdown might be useful. Ie, not just that Github uses Markdown, but that Github-flavored Markdown is a notable dialect that sees wide use and has inspired useful, common extensions to the original spec. This should not literally be a list with simple references to "this exists", but a prose-based discussion of notable dialects of markdown. Nickelpro (talk) 00:10, 26 March 2025 (UTC)[reply]

Use for LLMs

[edit]

I think that it would be worth mentioning that Markdown has recently been increasingly used with LLMs. Products like Google Docs and Apple Notes have added the ability to copy/export as Markdown, perhaps to make it easier to paste into an LLM, and there's a plethora of tools for converting PDF to Markdown. I wonder if there are any good sources for this though. SheepTester (talk) 22:47, 7 September 2025 (UTC)[reply]

No 1.0 spec

[edit]

In the text there is a line "No 1.0 spec has since been released, as major issues still remain unsolved." Personally, I found this confusing. Was it meant to be "No" (as in "nothing"), or "No" ans a abbreviated version of "Number"? 2001:1C00:650A:3200:9CA0:1211:B8BA:1C34 (talk) 06:24, 25 October 2025 (UTC)[reply]

The former (which is clear English), rather than the latter (which would be both nonsense as well as poor grammar) TEDickey (talk) 13:45, 25 October 2025 (UTC)[reply]

Comparison(capabilities/properties) of Markdown editors/viewers

[edit]

This list: https://github.com/mundimark/awesome-markdown-editors?tab=readme-ov-file can be taken as a start. Then their capabilities/limitations(like: page preview/WYSIWYG, able to show images(from local file system/from which protocols), ability to insert markup elements like tables via GUI, license, Operating System/Platform, costs etc.) should be shown in a table.

This can save a lot of time to Markdown users if they don't need to test a lot of Markdown software because some applications don't show images with HTTP URLs or like "Scratch" 0.7.1 insert new HTTP URLs with "http://asset.localhost/" prefix when adding an image from local file system). — Preceding unsigned comment added by Mr.Systematic (talkcontribs) 13:43, 3 March 2026 (UTC)[reply]

See discussion in Talk:Markdown#Notable implementations. The article about the Markdown format is not a dumping ground for everything which happens to use the Markdown format. Markdown is just text, literally anything that can edit text is a Markdown editor. There is no notable differentiating criteria. Other similar pages for markup formats do not maintain lists of applications which happen to use them, and neither should Markdown. Nickelpro (talk) 04:05, 7 March 2026 (UTC)[reply]

this table draft:

Program Platform(s) License Shows images View(s) Additional features
MarkText 32 bit & 64 bit x86 : Windows, Linux, macOS [1] open source [2] from HTTP table of contents[3](from headings), either(not concurrently) WYSIWYG realtime preview[4] or source code[5] supports CommonMark spec, GitHub Flavored Markdown spec [6]
Scratch macOS, Windows, Linux [7] open source can't load images originally from HTTP, adds local files with prefix "http://asset.localhost/" into source code WYSIWYG [8] Edit with AI, Git integration [9]