You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 17, 2020. It is now read-only.
Not sure if this is a real issue, or how to solve it's bugging me in a post I'm working on, so I'm flagging it here for future consideration.
Working with the rst .. image:: file.png role in a post is brittle.
Putting file.png in the _posts directory doesn't work because file.png doesn't get copied to the _site subdirectory where the post's index.html ends up.
Putting file.png in a top level directory like images that gets copied to _site means that the image markup ends up something like .. image:: ../../../../../images/file.png. I haven't dug deeply enough to know if the number of ../ in that relative file spec is constant.
There has to be a better way...
The text was updated successfully, but these errors were encountered:
Not sure if this is a real issue, or how to solve it's bugging me in a post I'm working on, so I'm flagging it here for future consideration.
Working with the rst
.. image:: file.png
role in a post is brittle.file.png
in the_posts
directory doesn't work becausefile.png
doesn't get copied to the_site
subdirectory where the post'sindex.html
ends up.file.png
in a top level directory likeimages
that gets copied to_site
means that the image markup ends up something like.. image:: ../../../../../images/file.png
. I haven't dug deeply enough to know if the number of../
in that relative file spec is constant.There has to be a better way...
The text was updated successfully, but these errors were encountered: