Table of Contents
Markdown
Return to Markua, GitHub Markdown, DokuWiki Markdown
- Snippet from Wikipedia: Markdown
Markdown is a lightweight markup language for creating formatted text using a plain-text editor. John Gruber created Markdown in 2004 as an easy-to-read markup language. Markdown is widely used for blogging and instant messaging, and also used elsewhere in online forums, collaborative software, documentation pages, and readme files.
The initial description of Markdown contained ambiguities and raised unanswered questions, causing implementations to both intentionally and accidentally diverge from the original version. This was addressed in 2014 when long-standing Markdown contributors released CommonMark, an unambiguous specification and test suite for Markdown.
See:
- So many different incompatible implementation of Markdown (it is worse than the different incompatible versions of BASIC Programming Language in the 1980s) - https://github.com/markdown/markdown.github.com/wiki/Implementations
- https://www.adamhyde.net/whats-wrong-with-markdown - “Non-standardized formats suck! Markdown is good for limited use cases. Use it for README files on GitHub.”
- https://news.ycombinator.com/item?id=19744711 - Aardwolf said on April 25, 2019: “For me Markdown sucks because it ignores single newlines. Almost any place where I have to type markdown feels like it's plain text (typing a readme in an actual plain text editor, a git comment in vim, a plain text box like this one here in hacker news and reddit that also ignores newlines, …), and plain text is supposed to listen to your newlines. But markdown will happily turn your two things you put on separate lines into a single line, ruin source code or ascii art without adding special formatting, etc… It should wrap long lines, but should listen to explicit newlines. The simplest text editor can, and does, do that.”
-
- He says, “Now that I’ve written here (https://golifelog.com/posts/markdown-still-sucks-1636034939101) for over 300 days, I can confidently say that Markdown is not for me. In fact, I’ll go so far as to say if I had to use Markdown to write my newsletter, there would be no newsletter. Aside from learning the syntax, my biggest issue with Markdown is the lack of real-time formatting. I don’t like the idea that I have to wait to publish my article to see all the formatting. Oh, that’s how big H2 header is?? Nope, need to change it. Oh and I forgot the space after the “#” which you don’t need for other commands. I am a true target of the famed WYSWYG functionality.”
Study
- Search ALL of Udemy: https://udemy.com/courses/search/?src=ukw&q=markdown
YouTube Videos
https://youtube.com/results?search_query=markdown
Cloud Monk recommends the following YouTube video:
GitHub Tags
External Sites
Main
Interesting Articles
Search
Search for this topic on:
Support Resources, FAQs, Q&A, Docs, Blogs
Books
Encyclopedias
Search Engines
Apple
Education - Courses - Podcasts
Repos - Package Managers
Programming Language Docs
Networking
BTW, Just another reminder: Markdown SUCKS!
Markdown: Markdown Cheatsheet, Markdown on DokuWiki, Markdown Dialects, Leanpub Markdown (Markua), GitHub Markdown, Markdown GitHub, Awesome Markdown. (navbar_markdown)
Writing: Cloud Monk's Books (Cloud Monk's Package Manager Book, DevOps for 20 Languages by Cloud Monk and Functional Programming Compare and Contrast 10 Languages by Cloud Monk), Cloud Monk Library, Cloud Monk, Technical Writing, Technical Writing Bibliography, Technical Writing Courses, Writing Tools (AWESOME DokuWiki, Leanpub, DokuWiki, Spell Checker, Grammar Checker - Grammarly, Mind Maps, Outlining), Technical Writing Glossary, Writing Topics, Awesome Writing, GitHub Writing. (navbar_writing)
© 1994 - 2024 Cloud Monk Losang Jinpa or Fair Use. Disclaimers
SYI LU SENG E MU CHYWE YE. NAN. WEI LA YE. WEI LA YE. SA WA HE.