Markdown
Images and TextBundles
Local images
Reference an image relative to your document, as in , and it renders in place. Subfolders work too. The two photos below live inside PeepMD itself and are referenced exactly that way:
Photo by Daniel Roe on Unsplash.
Because images are embedded into the rendered page, they also survive into rich copy, PDF, and HTML exports. What you paste into Mail carries its pictures.
Remote images load live from the web as usual, and if a local image can't be read the moment a document opens (say, while macOS is still asking permission for the folder), the preview heals itself on the next app activation or ⌘R.
Images beside a document need one extra step.
PeepMD is given access to the document you opened and nothing else, not even the images folder sitting next to it. When it notices images it cannot read, a bar appears under the preview offering Allow Access…. Point it at the enclosing folder once and that permission is remembered from then on. TextBundles need none of this, because the images live inside the document.
TextBundles
A .textbundle is a folder that travels as one unit: Markdown plus an assets folder for its images. Bear, Ulysses, and friends use it to pass documents around without broken image links. PeepMD opens bundles directly: open one and its assets resolve, with edits to the text inside reloading live like any flat file. That makes them a good way to move an illustrated document between your Mac, your iPad, and Vision Pro.
Photo by ian dooley on Unsplash.
Note
PeepMD is a viewer: it writes into a bundle or a document only for a property you change or a task you check off.
Previous: CriticMarkup · Contents · Next: Exporting and Sharing