Relative image path resolution is borked

[jmduke]

Discussed in #5

^{Originally posted by jdhitsolutions June 5, 2025}
I'm unclear on how images work with the CLI. The documentation suggests that I put the image in the media folder and adjust the markdown image reference accordingly. The implication based on reading of the docs is that on push files in the media file will be uploaded. I just pushed a new email. The email showed up, albeit with formatting issues I'll cover in a separate discussion.

The email still had the markdown reference link which obviously doesn't work. I suppose the wishful part of me thought the push would replace the markdown link with an <img> tag. If the image in media was uploaded, I can't find a way to insert the uploaded file into the document. The alternative is to drag and drop media, which seems to defeat the purpose of the media folder.

Now, I could very well have a misunderstanding on how this is supposed to work, and I recognize that some features may not be fully baked, which is why I am bringing this up here. The CLI could be part of my new publishing workflow, once I work out a few pesky details.

[linear]

CLI-5 Relative image path resolution is borked

[markjaquith]

This is working just fine for me (in fact, I was pleasantly surprised by how well it worked).

What I did was this:

1. Put an image in buttondown/media/some-image.png
2. In buttondown/emails/some-email.md, embeded that image using a relative path (my editor auto-completed this for me!): ![My alt text](../media/some-image.png)
3. buttondown push

This uploaded the image to Buttondown. When I view the draft email on buttondown, it has a Buttondown CDN UUID URL (like https://assets.buttondown.email/images/451f13f7-5e28-4884-874d-98e62f24dea2.png, e.g.

But locally, it still uses the filename I chose. Multiple pushes/pulls keep this mapping. What seems to happen is that a mapping gets created in .buttondown.json, so that when syncing operations happen, the CLI translates between localPath and url