You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: wikilinks, a scaffolding command and touch targets
Three gaps found by comparing the plugin against the five recipe plugins
already in the community list.
Cells now render through Obsidian's markdown renderer, so an ingredient can
be [[Mascarpone]] and carry a hover preview and a backlink. This is the one
thing those plugins cannot copy cheaply: they all treat ingredients as
text, so none of them feed the vault graph. The renderer is injected as a
CellRenderer rather than imported, which keeps render.ts free of the
plugin API and unit-testable. Clicking a link inside a step now follows the
link instead of ticking the step off.
A new command scaffolds a recipe block from pasted prose. Transcription is
the adoption barrier here — every rival reads recipes you already have,
this one asks you to restructure them. The scaffold converts fences,
markers, numbering and headings, and refuses to guess which step consumes
which ingredient: 'pour in 3-4 oz of your milk' carries a quantity and is
still a step, so a heuristic sure enough to build the tree would sometimes
build it wrong in silence. The output always parses, so a table appears
immediately and gets refined from there.
Tickable cells measured 34px against the 44px touch target every platform
asks for; under a coarse pointer they now use height as a floor, measured
at 44px in Obsidian's mobile emulation.