Obsidian Syntax Showcase

Quartz 5 aims at full Obsidian compatibility. This note uses each construct once, with real content, so the rendering can be checked page by page.

Callouts

Plain callout

The default type. Useful for asides that should not interrupt the flow of the argument.

Collapsed by default (click the title)

A dash after the type collapses the callout. Good for long reference material: the reader opts in.

Nested callouts

Callouts can contain callouts.

Inner example

A quorum of 2 out of 3 nodes tolerates exactly one failure. A quorum of 3 out of 5 tolerates two.

Open question

Does a stacked-pages layout make long notes harder to read on a laptop screen? Decide after a week of use.

Highlights and hidden comments

The claim to remember from the CAP discussion is that partition tolerance is not optional; the real decision is what to sacrifice while the network is broken.

Task lists with custom markers

• Migrate the site to Quartz 5
• Review the stacked-pages experience on desktop
• Decide whether the Tokyo Night theme should stay
• Install the Giscus app on the repository so comments can be posted
• Hard line breaks plugin: rejected, the notes are hard-wrapped
• Revisit this list in a month

Block reference

The definition below is not copied; it is embedded from the partition tolerance article through its block id, so it stays in sync:

Partition Tolerance (P) in the CAP theorem means that a distributed system continues to operate even if there are arbitrary message losses or failures within the network that separate the system into multiple isolated partitions. Imagine your distributed database servers are connected by a network. A “network partition” means that communication between some of these servers is lost, effectively splitting them into two or more independent groups that cannot talk to each other. (Gilbert & Lynch, 2002)

Link to original

Footnotes

Mermaid renders at build time with an expand button¹, and the video below is embedded with plain image syntax².

Mermaid

flowchart LR
    A[Markdown note] --> B[Transformers]
    B --> C[Filters]
    C --> D[Emitters]
    D --> E[(public/)]
    B -. plugins .-> B

Video embed

Martin Kleppmann’s first distributed systems lecture, which the System Design notes on this site follow:

Wikilinks with aliases and headings

• Alias: the CP systems note
• Heading link: System Design/cp_systems_design > What a quorum write looks like
• Tag link: system-design

Footnotes

1. The diagram source lives in the markdown; no image files are involved. ↩

2. ![](https://www.youtube.com/watch?v=...) becomes an iframe. Tweets work the same way. ↩