Yup, that's the problem with building paths/folders.

In your Pull Request, there's a change with image path: https://github.com/segmentio/segment-docs/pull/174/files#diff-e3144a881ed92eaaa367978fb31ce39e

I used it and it works as you can see on this page: http://segment-docs-stage.s3-website-us-west-2.amazonaws.com/docsv2/connections/spec/identify/

Yes, paths changed a little. The image folder stays in same spot, but index.html file of a page sits in a folder. Structure after Jekyll compilation looks like this:

images/
anomaly_detection/
    |-- index.html

It's a matter of fixing the content of markdown files and add to images path a ../ so they have a proper path.

PS. or we can consider using absolute paths, however, at this point, I cannot tell if this is an easier way 😅Would need to test it out

@jedrzejchalubek I'm just confused because even with prettylinks on, I've never seen this behavior in Jekyll so that it requires this path traversal. If you look at, for example https://github.com/docker/docker.github.io/blob/master/docker-hub/repos.md which builds https://docs.docker.com/docker-hub/repos/, you can see that it doesn't require this folder traversal.

okay, I see what's going on here.
That was confusing for us too 😄

I've just tested specifically this page http://segment-docs-stage.s3-website-us-west-2.amazonaws.com/docsv2/protocols/anomaly_detection/#forward-violations-to-a-slack-channel you mentioned before.

It turns out that Jekyll is smart enough and both paths:
![](images/protocols_meta_source_setup.png)
![](../images/protocols_meta_source_setup.png)
work well.

However, something doesn't work very well on the staging.
Now, we have the same code locally and on your staging and there are differences between images visibility. Locally I can see all of the images no matter which path I use, but the staging can't handle that. Maybe it's something with your building scripts 🤔

I guess there's nothing we can do about it.

@noeemi thanks for testing that! I thought I was going crazy!

@danielstjules @XavierAgostini Which of you knows the most about our S3 setup to troubleshoot? I'm seeing it correctly locally as well. 🤔

@sanscontext the issue is with the URL:
![](./../images/protocols_meta_source_setup.png)
This will work, so you just need to manually update the images paths for the broken images

@XavierAgostini As I pointed out upthread, this is not usual behavior for Jekyll and is a really poor experience.