<h1 id="markdown">Markdown<a aria-hidden="true" class="anchor-heading icon-link" href="#markdown"></a></h1>
<ul>
<li><a href="/wiki/notes/gXsL1BFwltPwNkfGnB3wN">hasCreator</a> <a href="/wiki/notes/eKUZ0SqHbRVs5sRCiZyG5">John Gruber</a></li>
</ul>
<h2 id="hassense-a-markup-language"><a href="/wiki/notes/mYXKcNxVG7fcemnYxx0EZ">hasSense</a> a markup language<a aria-hidden="true" class="anchor-heading icon-link" href="#hassense-a-markup-language"></a></h2>
<ul>
<li><a href="/wiki/notes/s2AA4w4SyPFu44ylTFLQH">instanceOf</a> <a href="/wiki/notes/z4kl5ie3d8inzmp00eq20aj">Programming Language</a> </li>
</ul>
<h2 id="hassense-the-class-of-markup-languages-based-on-markdown"><a href="/wiki/notes/mYXKcNxVG7fcemnYxx0EZ">hasSense</a> the class of markup languages based on Markdown<a aria-hidden="true" class="anchor-heading icon-link" href="#hassense-the-class-of-markup-languages-based-on-markdown"></a></h2>
<ul>
<li><a href="/wiki/notes/QKEepTlPqcDgJw0fhRvPB">subClassOf</a> <a href="/wiki/notes/z4kl5ie3d8inzmp00eq20aj">Programming Language</a></li>
</ul>
<h2 id="to-do">to-do<a aria-hidden="true" class="anchor-heading icon-link" href="#to-do"></a></h2>
<ul>
<li>[c] summarize footnoting. using ^ seems scary give dendron references.</li>
</ul>
<h2 id="resources">Resources<a aria-hidden="true" class="anchor-heading icon-link" href="#resources"></a></h2>
<ul>
<li><a href="https://cirosantilli.com/markdown-style-guide/#top-level-header">https://cirosantilli.com/markdown-style-guide/#top-level-header</a>
<ul>
<li>a bunch of suggested best practices</li>
<li>first mention I've found of using horizontal rule <code>---</code> to end a header's content</li>
<li>good examples of definition lists</li>
</ul>
</li>
<li><a href="https://stackoverflow.com/questions/4823468/comments-in-markdown">https://stackoverflow.com/questions/4823468/comments-in-markdown</a>
<ul>
<li>no great solution for comments. </li>
<li>tempting to just use <code>//</code> and/or <code>/* ... */</code></li>
<li>t.2024.01.11 according to <a href="https://www.w3schools.io/file/markdown-comments/">https://www.w3schools.io/file/markdown-comments/</a> it should be <code>&#x3C;!---</code> and <code>---></code></li>
</ul>
</li>
<li><a href="https://www.smashingmagazine.com/2022/02/thoughts-on-markdown/">https://www.smashingmagazine.com/2022/02/thoughts-on-markdown/</a>
<ul>
<li>experience for editors is not ideal
<ul>
<li>supported-by: "Do you really want your editors to bump against merge conflicts or how to rebase branches?"</li>
</ul>
</li>
<li><a href="/wiki/notes/NlCXE63wYf9A0vToHfVzv">references</a> <a href="/wiki/notes/l7si3k21egbqfsxvt5gb6on">MDX</a></li>
</ul>
</li>
</ul>
<hr>
<strong>Children</strong>
<ol>
<li><a href="/wiki/notes/BtlFN9O6DIPp0gDYgRK5i">Commonmark</a></li>
<li><a href="/wiki/notes/O698yb57stRhT9DxOgZ2c">CriticMarkup</a></li>
<li><a href="/wiki/notes/v6crodfdul20xzo855azcjm">Dendron Flavored Markdown</a></li>
<li><a href="/wiki/notes/49isri60mlpfqqfffo6ahnc">Dragons Inn Flavored Markdown</a></li>
<li><a href="/wiki/notes/BBg2KcQ1aANaVEPWAJw34">GFM</a></li>
<li><a href="/wiki/notes/PRMkhi6Ek2kX4CQJLDidp">MultiMarkdown</a></li>
<li><a href="/wiki/notes/659fUF9wKybhz2RU7d3lj">Php Markdown Extra</a></li>
<li><a href="/wiki/notes/kq4R0U0QtV8gP2UeGIB9c">R Markdown</a></li>
<li><a href="/wiki/notes/dtxqxxlj51rdmv6e40xddpg">R Markdown</a></li>
</ol>
<hr>
<strong>Backlinks</strong>
<ul>
<li><a href="/wiki/notes/tX0Ki4R9sD1H9uXEnlamr">Semiotic Blob</a></li>
<li><a href="/wiki/notes/mgdBdETJA9rtIgLxmnIRm">Milkdown</a></li>
<li><a href="/wiki/notes/xhobgjvpyurhxkybqpyv2da">Commonplace</a></li>
<li><a href="/wiki/notes/pxobo46hylnqvnmupsk6ihu">reStructuredText</a></li>
<li><a href="/wiki/notes/cp7ybekm5ikxrikg4glged6">Subtext</a></li>
<li><a href="/wiki/notes/eKUZ0SqHbRVs5sRCiZyG5">John Gruber</a></li>
<li><a href="/wiki/notes/BBg2KcQ1aANaVEPWAJw34">GFM</a></li>
<li><a href="/wiki/notes/PRMkhi6Ek2kX4CQJLDidp">MultiMarkdown</a></li>
</ul>

the class of markup languages based on Markdown

Markdown

public-notes


Welcome! And beware!  

## Purpose

This vault is the "[[learning-in-public|ar.swyx.learn-in-public]]" part of my Second Brain. If you share some of my interests, please [reach out](https://djradon.github.io)! 

## Contents

- [[t]] my personal wikipedia
- [[idea]] (not necessarily mine)
- Resource Notes, including highlights, thoughts and metadata, for various things:
  - [[ar]] mostly articles, papers and web pages
  - [[book]]
  - [[community]]
  - [[course]]
  - [[event]]
  - [[game]]
  - [[loc]]
  - [[org]]
  - [[user]] 
  - [[prdct]] mostly software products, but also ontologies
  - [[recipe]]
  - [[video]] movies, tv episodes, youtube, etc
- [[vs]]
- [[wanted]]
- Some "Metadata Notes":
  - [[tags]] which may refer to any and multiple (or none) of the above
  - [[c]]: ways to categorize resources
  - [[p]]: ways to assert things about resources (mostly abandoned)

In terms of the [[t.km.zettelkasten]] method, this wiki is a commingling of literature notes with something @Sönke-Ahrens warned about: a "personal Wikipedia or a database" [^1]. 

In terms of [[t.tm.getting-things-done]], it's references, someday-maybe, next actions, and public projects.

## Beware!

This is a cluttered cupboard of jumbled jottings riddled with inaccuracies, confusion, and mistakes.

## What This Is Not

- evergreen-notes/digital-garden: for "synthesized" / original-ish publishable big-idea notes that should evolve over time, props to @andy-matuschak and @maggie-appleton
- blog: for "point-in-time" items to be shared: personal news, articles, etc.
  - e.g., [[ar.substack.carpe-noctem]]


[^1]: [[book.how-to-take-smart-notes]]  

Markdown

hasSense a markup language

hasSense the class of markup languages based on Markdown

to-do

Resources