Best practices on image file locations

support
1

When creating article and blog post content with embedded images, what’s considered best practice for image file location? I see a lot of people just build out an image directory in the static folder, but it also seems like a page bundle might be better, since that would allow for Hugo’s image processing.
Per the example on https://gohugo.io/content-management/page-bundles/#branch-bundles, I created this directory structure under my content folder:

├── about
│   └── index.md
├── articles
│   ├── beginner-digital-photography-setup.md
│   ├── beginners-google-tag-manager
│   │   ├── images
│   │   │   └── gtm-home.png
│   │   └── index.md
│   ├── branch-bundle
│   │   ├── _index.md
│   │   ├── branch-content1.md
│   │   ├── branch-content2.md
│   │   ├── image1.jpg
│   │   ├── image2.jpg
│   │   └── images
│   │       └── image1.jpg
│   └── my-dev-setup.md

from either branch-content1.md or branch-content2.md, I’m struggling to embed an image. none of the 4 options below in either markdown file work:

### option 1

![alt text](image2.jpg "Logo Title Text 1")

### option 2

![alt text](../image2.jpg "Logo Title Text 1")

### option 3

![alt text](../images/image2.jpg "Logo Title Text 1")

### option 4

![alt text](../branch-bundle/images/image1.jpg "Logo Title Text 1")

I was, however, able to get a shortcode to work, using “…/image1.jpg” as the path. Maybe that’s just the best way forward for me?

I’m sure I’m just missing some key content for setting this up. Ideally, I’d like to make page bundles work, and come up with a nice, repeatable process for that. I’m curious how others approach managing images for articles and blog posts.

thanks!

1 Like
2

my 2cents:

![alt text](images/image2.jpg "Logo Title Text 1")

{{< figure src=images/image2.jpg  >}}
1 Like
3

thanks - this works well. I also discovered how to set up an archetype for my page bundle process. Still lots for me to learn, but things are really shaping up.