Image prefixing not working

[isaacbrodsky]

Please see uber/h3#274

I couldn't find a way to use relative paths (such as ijkp.png, relative to the images directory, or /images/ijkp.png, relative to the site root) to refer to images. Instead I had to hardcode the path prefix, which results in breaking the development version of the site.

[jckr]

please put your images in /src. Gatsby will transform them and apply various optimizations when creating the production website. That's why logically, it makes sense to have images along other parts of the source code.

With your images in /src (for instance in /src/images) you can then reference them like so in your markdown: 
for instance

[ibgreen]

Should we add a chapter about images in our docs and mention this there?

[isaacbrodsky]

@jckr I assumed static/images (rather than src/images) was the correct path because npm run build fails if it doesn't exist.

I tried both:

![IJK+](/images/ijkp.png)
![IJK+](images/ijkp.png)

and the resulting img tag did not have the prefix applied in npm run build. The file was at website/src/images/ijkp.png in my repo.