Images in markdown relative to content

[garvincasimir]

Hi,
I like the idea of having my images close to my content so I create my articles like this:

post/my-post.md
post/images/my-post-img.png

This displays the images on the single template when ugly urls are turned on but does not display it on the list pages or on any page when ugly urls are turned off. The relative path for the image never gets transformed even with canonifyurls turned on. Maybe there is a setting I am messing?

![my img](images/my-post-img.png)

I see issue #147 had a discussion that might be related to this. The images are being copied but I am not getting the correct urls in the generated pages.

Any thoughts on this?

[bep]

This is currently not possible, but it is (or should be) in front of @spf13's brain ...

Currently you have to have to path relative to the context root (/post/images/...).

[garvincasimir]

I would send a pull request but the go code makes me feel dumb. But seriously great to see @spf13 take up this issue. I know it complicates rendering because the link to the image would vary based on the final path of the page it is rendered on.

[tcurdt]

I would love to have support for

posts/2015/some-post-slug/index.md
posts/2015/some-post-slug/image.png
posts/2015/some-post-slug/archive.zip
posts/2015/other-post-slug/index.md

and I want would like that to appear in the output as

/2015/some-post-slug/index.html
/2015/some-post-slug/image.png
/2015/some-post-slug/archive.zip
/2015/other-post-slug/index.html

[tcurdt]

This actually seems to be working out of the box now.
Getting rid of "posts" folder is a problem though. A work around is to use:

permalinks:
  post: /:year/:slug/

which isn't quite the same thing though.

[SvenDowideit]

@spf13 have you got some ideas on how to implement this? we need it for the Docker docs, but pointers will get me up to speed faster :) (its on my list of things for the next 4 days :)

[SvenDowideit]

initial version added in #1398

[AlexZeitler]

Is there any progress on using images in markdown relative to content?

[jygastaud]

@AlexZeitler : As suggest in #147 I'm using the following workaround.

Contents are in content/project/my-content/index.md folder
Images are stored in static/project/my-content/my-image.png folder

And in my markdown I can do ![my-image](my-image.png)

Hugo just will copy the structure without the first "static" folder so generation the html file will have acces to the image.

Hope it helps!

[AlexZeitler]

@jygastaud Thanks for your reply.

I created this structure now:

content/blog/test-with-path/index.md
static/blog/test-with-path/mypng.png

In the md I referenced it this way ![some png](mypng.png)

I also tried

content/blog/test-with-path/index.md
static/blog/test-with-path/mypng.png/mypng.png

None did work.

[jygastaud]

That's weird.
That works for me. See jygastaud/jygastaud.github.io@a415264 which result to http://gastaud.io/article/entityconnect-d8/conversion-form-instance/

You can see structure here : https://github.com/jygastaud/jygastaud.github.io/tree/source

[garvincasimir]

@jygastaud please take a look at the original issue again. If you only ever display images on the actual post page then you can work around it. However, if your list pages display posts with images where the image is located relative to the content then the image will not display. Hugo would probably need to take the mark down and write different urls to the same asset based on the context of the page render.

For example, your list page is www.yoursite.com/blog/ and it has your last 3 posts. A post at www.yoursite.com/blog/mypost.html with a relative image in /blog/images/img1.jpg can use a relative url in mypost.html to reference that image but that url will be incorrect for displaying your last 3 posts. It also gets tricky when you think about ugly vs no ugly urls. My hope was that Hugo could compensate for these different nuances and always write the correct url to the asset. I hope that clarifies it.

[jygastaud]

@garvincasimir oh sorry I missed the part that explains that it works on single page but not on list :/
Sorry for the noise.