On the “Known limitations” page, it says that Gatsby and Forestry have issues with absolute file paths. I’m not sure if that’s accurate:
This line: "Gatsby interprets absolute files paths relative to the system root and not the project root” seems to be incorrect. I’m using a Gatsby site with absolute file paths and it works as expected. (Maybe it’s changed on a recent Gatsby version?)
I’m running a Gatsby site on Forestry without the recommended gatsby-remark-relative-images plugin and it “just works” with no issues.
It recommends storing images in static/ and links to a recommended blog starter. The linked blog starter, however, does not store images there.
I’m filing an issue instead of a PR because I’m not 100% confident that I completely understand the technicalities. Maybe there’s something else I’m missing?
https://github.com/forestryio/forestry.io/blob/master/hugo/content/docs/guides/developing-with-gatsby.md#known-limitations
On the “Known limitations” page, it says that Gatsby and Forestry have issues with absolute file paths. I’m not sure if that’s accurate:
gatsby-remark-relative-images
plugin and it “just works” with no issues.static/
and links to a recommended blog starter. The linked blog starter, however, does not store images there.I’m filing an issue instead of a PR because I’m not 100% confident that I completely understand the technicalities. Maybe there’s something else I’m missing?