When I run hugo locally, I see my two projects and verified the projects/index.html is being created, but when it push it to GitHub, and Amplify builds it with Hugo 0.73, it doesn’t show up: https://tobilehman.com/projects/
Yup, me too. I see that public/projects/index.html lists both “crib-calc” and the “manipulate-mediastreams” projects. Isn’t that the expected result, at least before deployment?
I have a theory. public/projects/index.html is rendered first as a section, and then it’s overwritten as a taxonomy. To @pointyfar and me, the order was reversed for some reason, so we couldn’t reproduce the mistake.
You can test this by adding any content with a project, such as:
---
title: "Hello"
projects: "hello from the taxo"
---
Then that page will appear on the list.
If you want to define content for each taxonomy term (which is how the concept appears in the docs), you have to do it with a slightly different structure:
Hm, I get the feeling that there’s still some overwriting at play here. Maybe I should open an issue, because it fails too silently. I’ll investigate later.
TL;DR: There IS some overwriting, but that doesn’t cause a problem right now.
I’m back. Sorry to keep posting but I discovered a useful tool to figure out if the outputs are getting overwritten, which is the --path-warnings flag.
PS C:\Users\agust\code\github.com\tobilehman.com> hugo --path-warnings
The result of this command for the current version of your repo is:
Start building sites …
...etc etc...
WARN 2020/12/16 23:35:42 Duplicate target paths:
C:\Users\agust\code\github.com\tobilehman.com\public\projects\index.html (2),
C:\Users\agust\code\github.com\tobilehman.com\public\projects\index.xml (2)
Total in 6307 ms
I’m now ready to stop posting for the day (I don’t know what got into me to be honest) and give it a rest so I don’t get banned. Cheers to everyone.