Questo sito contiene un utile guida con esercizi interattivi per imparare il #Markdown:

https://commonmark.org/

Rettifico come da commenti: in realtà è il sito ufficiale del #CommonMark, una sua possibile standardizzazione. Infatti ne esistono molte varianti.

Getting close to being happy with how I organise the content for a module I have been entrusted with.

It is a #Git organised set of notes for a #flippedClassroom module.

All notes are written in #CommonMark (#OrgMode if it was just me ;-))

#Pandoc is at the heart of preparing the written notes.

+ Custom templates help satisfy local branding requirements
+ Pandoc features enable #moodle compatible HTML to be generated with #MathJax maths and embedded resources. (Moodle is just a carrier!)
+ Use #CSL to generate references

#Make enables targets to generate ALL THE TARGETS, ensuring correct pandoc options are used:

+ Standalone HTML for local use, with #SimpleCSS for styling
+ HTML optimised for Moodle;
+ LaTeX;
+ PDF (via LaTeX)
+ DOCX

Slides and assessment specs are still LaTeX.

If you're thinking of using any other form of #markup than #Commonmark then please don't.
https://commonmark.org/

In small morning projects land, I've written a simple #VSCode extension for the #djot markup language!

Since no one probably knows what Djot is, Djot was made by John MacFarlane, the mastermind behind #commonmark , the common standard for #markdown documents! It's his pet project for a better markup language inspired by a blog post he made about the topic: https://johnmacfarlane.net/beyond-markdown.html

Djot: https://github.com/jgm/djot

The extension:
https://github.com/ryanabx/djot-vscode
https://marketplace.visualstudio.com/items?itemName=ryanabx.djot-vscode

#Markdown syntax tip for code block attributes, yielding the best rendering results with both pandoc and on platforms such as #GitLab #GitHub, #Codeberg, etc:

``` lua {#my-id .another-class}
io.stdout:write('hi!')
```

The curly-braces syntax for attributes is ignored when read as #CommonMark, the Markdown variant used by most platforms. The above ensures that syntax highlighting still works with CommonMark, and that the other attributes get respected when converting with #pandoc.

As a side project of #Fedify, I published @fedify/markdown-it-mention, a markdown-it plugin that parses and renders Mastodon-style @mentions!

https://github.com/dahlia/markdown-it-mention

Support for #CommonMark alert-boxes was added in pandoc 3.1.10.

> [!INFO]
> This is an informational message.

Note, however, that writer (i.e., rendering) support for this is limited, and that the `alert` extension works with CommonMark, but not with pandoc-flavored Markdown.

The syntax has been made popular by GitHub: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts

Since I'm on a roll, how come infosec.exchange allows posts of up to 10k characters but #rubysocial only gives me 500? Not all things programming can be expressed in a ½ kilo of chars.

And OMG do I wish this instance supported #CommonMark and an easier way to escape octothorpes when discussing #RubyLang methods! Writing methods as :foo instead of \#foo or `#foo` just seems cumbersome, and the latter two show up as hash tags anyway!

I'm still not out of the rabbit hole of searching for an #OpenSource #PersonalKnowledgeManagement software.

I'm gonna give a second try to @zettlr tomorrow! Their docs are *surprisingly* user-friendly and they claim to stick to the pure #CommonMark where probable. It's all the while being nice to researchers with citing, inline usage of #TeXLaTeX, #MermaidJS, and pop-over #footnotes. Provision of the simple #PDF export and #Pandoc customization are welcome, too!

But, to be fair, I may be overexaggerating how good #Zettlr is because of my recent disgust with #VendorLocking. In fact, almost anything that closely follows the common spec and is #FreeSoftware might suffice already. Having something as advanced and closer to the roots is certainly refreshing!

Bummer. @github doesn't support rendering markdown "definition lists", because they use cmark-gfm, which is a fork of cmark, which implements Common Mark, which still hasn't added support for markdown definition lists to their specification.
https://talk.commonmark.org/t/description-list/289
#github #cmark #commonmark #markdown

Pretty stupid question but can someone explain why #commonmark doesn't support colors when most modern terminals support it? (Even linux virtual terminal/console). I am not asking for color accurate sRGB spectrum. Just enough to highlight some parts.

@edwiebe @EpiphanicSynchronicity @obsidianmd

FYI #Djot is 90% like #Markdown but as much complete as the alternatives and it is by the author of #Pandoc and #Commonmark spec:

https://djot.net/