Obsidian
sublimated supports most Obsidian markdown extensions. push your vault via git and it renders correctly on the web.
see markdown syntax for the full syntax reference, or demo to see everything rendered.
what works
- wikilinks —
[[page]]and[[page|display text]]resolve to files in your space - embeds —
![[file]]embeds images, documents, and other content inline - block IDs —
^blockidat the end of a paragraph or heading creates a stable anchor - block references —
[[page#^blockid]]links to a specific block - heading references —
[[page#heading]]links to a specific section - frontmatter — YAML between
---delimiters, stored and queryable - task lists —
- [ ]and- [x] - tables, strikethrough, highlights
- dataview queries — DQL code blocks and inline expressions
embeds
![[photo.png]] embed an image
![[photo.png|300]] with width
![[photo.png|300x200]] with width and height
![[document.md]] embed another document
![[document.md#section]] embed a specific section
![[document.md^blockid]] embed a specific block
sublimated also supports iA Writer content blocks (/path/to/file) as an alternative embed syntax.
wikilinks
[[meeting-notes]] links to meeting-notes.md
[[projects/roadmap]] links to projects/roadmap.md
[[roadmap|Our Roadmap]] custom display text
links resolve from your space root.
block IDs
This is an important paragraph. ^important
## Section heading ^intro
reference from other files with [[page#^important]] or embed with ![[page#^important]].
pushing your vault
cd my-vault
git init
git add . && git commit -m "initial"
git remote add origin https://sublimated.com/{your-space}/vault.git
git push -u origin main
your vault is now browsable at sublimated.com/{your-space}/vault with all wikilinks and embeds working. see git for more on cloning and pushing.
what's different
- sublimated resolves wikilinks from the space root, not relative to the current file
- Obsidian plugins and custom CSS don't carry over — only the markdown content
.obsidian/config folder is ignored for rendering