It filters nothing
A snippet is inserted as it stands — as HTML, unchecked. That is the point: anyone wanting to insert
an <svg> or a <style> should be able to.
The consequence: only use files you control yourself. A snippet from a foreign source is as trustworthy as foreign JavaScript. That does not apply to values from the page — placeholders are escaped (4.1).
It knows no conditions
No expressions, no comparisons, no rules per folder. A page can hide a box or swap its snippet, nothing more. Why, and what helps instead: 6.2.
It renders no Obsidian syntax
Wikilinks, callouts and embeds stay in a Markdown snippet as written. The plugin is a pure component and sits behind the content pipeline (1.3).
It remembers nothing in the browser
An opened box is back to whatever collapsed says after the next page change. Without JavaScript it
cannot be otherwise — and shipping no JavaScript is a decision, not a gap
(5.1).
The cache hangs on the modification time
Not on the content. Writing a file back with its old timestamp shows the old version. In practice this only affects restoring from an archive.
Snippets are public
They live under quartz/static/ and are shipped along. They can be fetched through the site’s
address. For markup that appears on every page anyway that is of no consequence — as a place for
anything non-public the folder is unsuitable.
What is deliberately absent
- No scheduling. No box that appears on Monday and disappears on Friday.
- No template language. Placeholders insert values; they cannot calculate, branch or repeat.
- No built-in styling. Apart from two rules for images the plugin brings no appearance with it (5.2).