Create a .css file with the following code (I use Textedit for mac, don’t leave the .txt extension)
Put it in the snippet folder : your vault/.vault/snippet
Open the .vault folder using CMD OPT . command.
Notice that I added text-align: center; to center the caption because I use another snippet to center my image. If you don’t want to center your image, juste erase this part of the code (for reading mode and source view).
Don’t forget to activate this new snippet in the obsidian setting
Normal text
> [!figure] ![[two_noises.png]]
> Two signal measurement one has a SNR of 10 the other of 100. The signal average is however the same.
Some normal text continue here
Markdown already has a place for the image description (spec here):
![Image description](path/to/image.jpg)
or
![[path/to/image.jpg|Image description]]
This is where the text is taken from in the captions plugin(s) above.
Relying on Obsidian-style callouts is quite far from any sort of standard Markdown. It might be supported on another Markdown renderer, but it probably won’t be.
Using the in-spec Image Description has a higher likelihood of being supported on another platform into the future, and even without that, it is easier for other software to parse and renders perfectly into HTML.
edit: I’ll add that there’s nothing wrong with doing it the callout way - it’s just food for thought as you consider the longevity of your vault, and the cross-compatibility of it on other platforms if Obsidian is no longer around.
Of course . This was just an additional solution on the topics.
This solution is pretty suitable for long descriptions which can include bold text LaTeX , cross references etc …
Works well within Obsidian and any Markdown render with Obsidian callout flavour .
In fact the information is still there for Markdown render that does not handle callouts (like pandoc) . Only a weird [!figure] is added somewhere, but figure and caption are there.