Support relative paths in markdown images

[runofthemillgeek]

Adds code from Hugo's built-in render-image hook and modifies it slightly to support relative image paths in markdown files.

Previously, we'd have to spell the absolute path from root of the hugo site or make directories for each individual post which is what Hugo recommend. But this was very inefficient. This change allows us to use editors like Obsidian, VSCode and have them render the images correctly. It also supports Hugo's page bundles for rendering images as a result. Based on the order, I believe page bundles are given priority so that works out.

i.e, if you have the following tree:

content
└── posts
   ├── _index.md
   ├── hello.md
   ├── images
   │  └── test.png
   └── test.png

You can now include images in hello.md in the following ways:

![](test.png)
![](images/test.png)
![](./test.png)
![](./images/test.png)

[tomfran]

Cool, this is backward compatible right?

[runofthemillgeek]

@tomfran yeap, I tested the absolute path option (i.e /posts/test.png) as well as a page bundle like the posts you have on your personal blog. Both seem to work fine in my case.

[tomfran]

Thank you so much for testing

[runofthemillgeek]

Pulled the latest commit into my personal blog and ran a build. Looks all good even with existing paths. Converted paths to relative and published the built assets. This change is working as expected: https://blog.sangeeth.dev/posts/custom-domains-with-https-for-your-localhost-servers-on-macos/