Forestry added header images get wrong path on frontend about ipfs-blog HOT 4 CLOSED

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

from ipfs-blog.

@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.

from ipfs-blog.

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?

from ipfs-blog.

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

from ipfs-blog.