Forestry added header images get wrong path on frontend #2

New Issue

2026-10-05T05:08:49+02:00

adam commented

2026-10-05 05:08:49 +02:00

header images added like https://app.forestry.io/sites/o1m1vi-99lz4lw/#/pages/src-_blog-weekly-112-welcome-to-ipfs-weekly-112-md/

will get an extra /header_images/ on LazyImage src path

header images added like https://app.forestry.io/sites/o1m1vi-99lz4lw/#/pages/src-_blog-weekly-112-welcome-to-ipfs-weekly-112-md/ will get an extra `/header_images/` on `LazyImage` src path ![image](https://user-images.githubusercontent.com/13136975/104698810-cec0dc00-5709-11eb-9420-12fdcabdb4ea.png)

adam closed this issue

2026-10-05 05:08:49 +02:00

adam commented

2026-10-05 05:08:50 +02:00

@jessicaschilling following with what was discussed in #13, and after talking with @Ricardo-Silva91 today, we came to a conclusion that the header_images directory shouldn't exist as it only makes things more confusing.

The reasoning behind that is when we create a new blog post and add a new header_image, Forestry will upload the image to the public directory. There's no way to configure a specific field to upload to a different path.

With that being said, if we keep the header_images directory we would only be able to add images to it manually, which I think it's pointless since we want to use Forestry to manage the blog.

If we move the images to the public directory root we can follow the same naming convention you suggested in #13:

Header images that belong a specific blog post we can use weekly-001-header-image.png
Header images that are used in multiple posts we can use header-image-weekly-newsletter.png

Please let me know your thoughts on this.

@jessicaschilling following with what was discussed in #13, and after talking with @Ricardo-Silva91 today, we came to a conclusion that the `header_images` directory shouldn't exist as it only makes things more confusing. The reasoning behind that is when we create a new blog post and add a new `header_image`, Forestry will upload the image to the `public` directory. There's no way to configure a specific field to upload to a different path. With that being said, if we keep the `header_images` directory we would only be able to add images to it manually, which I think it's pointless since we want to use Forestry to manage the blog. If we move the images to the `public` directory root we can follow the same naming convention you suggested in `#13`: - Header images that belong a specific blog post we can use `weekly-001-header-image.png` - Header images that are used in multiple posts we can use `header-image-weekly-newsletter.png` Please let me know your thoughts on this.

adam commented

2026-10-05 05:08:51 +02:00

Agree, thanks for digging into that.

For future uploads in new blog posts we'll need to make a naming convention clear in our "how-to" guidance, though, since we will rely on the user to correctly name things they upload. Is there any sort of affordance within Forestry to add a note/caption on the image upload area of the post editor?

Agree, thanks for digging into that. For future uploads in new blog posts we'll need to make a naming convention clear in our "how-to" guidance, though, since we will rely on the user to correctly name things they upload. Is there any sort of affordance within Forestry to add a note/caption on the image upload area of the post editor?

adam commented

2026-10-05 05:08:51 +02:00

Yes, there is a description field we can use to add more information about the field, that should help.

Yes, there is a `description` field we can use to add more information about the field, that should help. <img width="1405" alt="Screenshot 2021-01-15 at 19 04 04" src="https://user-images.githubusercontent.com/34691925/104767710-8551aa80-5764-11eb-8d97-6c8e0c9c4283.png">

adam commented

2026-10-05 05:08:52 +02:00

Awesome - I'll open a new issue for adding those notes (and some other related content), and assign it to myself.

Awesome - I'll open a new issue for adding those notes (and some other related content), and assign it to myself.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/ipfs-blog#2