wgroeneveld
/
brainbaking
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

note on Roys content hierarchies part 2

This commit is contained in:
Wouter Groeneveld 2022-08-17 08:59:09 +02:00
parent f77198dadd
commit 57ca32f5d3
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
content/notes/2022/08/17h08m53s44.md Normal file
View File

@ -0,0 +1,10 @@
---
date: 2022-08-17T08:53:44+02:00
context: "https://roytang.net/comments/8bebec65-9eb0-469e-9bb0-a475c0282532/"
---
Gotcha, I wasn't aware that resources were the problem. There's a long discussion [on the discourse page of Hugo](https://discourse.gohugo.io/t/keep-images-content-together/51/83) regarding this, but the gist is: that also works! 😅
I just tried that with my site. If I simply move every resource from `/static` to the corresponding folder, e.g. `/content/post/2022/07/image.jpg`, then it works without any change. Keep in mind that I include my images using the path `../image.jpg` if you want your content file to be in the `07` folder as well. That's not needed if you create a separate dir for reach post, _and_ can be circumvented by hacking `render-image.html`.
Anyway. I agree that the whole SSG system _can_ be needlessly complex (and confusing). To me, a Django or Wordpress setup doesn't alleviate that.