Mkdocs¶
Mkdocs Gotchas¶
yamlhighlighting is broken withmdx-breakless-lists- when using heading
#, if there are no line breaks between headings, any lists that is after content of the second heading will not be rendered properly, even withmdx-breakless-lists - furthermore, if using lists right after a
yamlcode block, the list will also not be rendered correctly 
- when referencing a subheading in another file, mkdocs uses
[](file.md#heading-with-space)while obsidian uses[](file.md#heading%20with%20space) - Before switching from lists to normal content, a line break is needed, otherwise the text below will be rendered with a indent
- mkdocs subheadings
[](#subheadings)must be in lower case
Admonition/Callouts¶
???is also valid syntax for mkdocs???+makes the callout collapsible and opens by default, while???-makes it closed by default
Obsidian callouts requires the pluginmkdocs-callouts
- obsidian callout syntax also follows the same
+,-for collapsing, it is to be inserted after the brackets
Available callouts include notes, info, warning, danger, success, failure, example, abstract, tip, question, bug.

Keys, Caret, Mark, Tilde¶
Keys
++ctrl+alt+plus++
Ctrl+Alt++

mark highlighting
tilde strikethrough
Tabbed Content¶
Tab 1 content mkdocs
Second line here.
Tab 2 content
- not supported in obsidian
attr_list¶
Fancy Buttons
mkdocs
[button text](.\mkdocs.md){ .md-button }

Tooltip
I’m a tooltip that you can hover or click.
[tooltip](https://link "hover text")

Annotation
I’m an annotation, but you need to click the plus icon (1) to show. (2)
- annotation 1
- annotation 2

Footnote
Insert footnote like [^1] 1
- for inserting footnote
[^1] [^1]:at the end to explain the footnote; not supported in obsidian
Code Highlighting¶
# yaml highlighting has to be `yaml` not `yml` and it's broken
---
version: "2.1"
services:
clarkson:
image: lscr.io/linuxserver/clarkson
container_name: clarkson
environment:
- PUID=1000
- PGID=1000
ports:
- 3000:3000
restart: unless-stopped
-
explaining the footnote. ↩