feat: move author field to languages.xx.toml under params

[Jh123x]

First time contributing so please do let me know if I am doing something wrong.

• feat: move author field to params.toml
• feat: add warning when author field is in languages.xx.toml instead of params.toml
• docs: update docs to reflect change

Closes #690

[netlify]

✅ Deploy Preview for hugo-congo ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	a15820c
🔍 Latest deploy log	https://app.netlify.com/sites/hugo-congo/deploys/65635e1d02b5f800083a3b1c
😎 Deploy Preview	https://deploy-preview-704--hugo-congo.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Jh123x]

Not sure how to change the docs correctly.
Do I need to change them for every translation?

For snippets like this in getting-started

# config/_default/languages.en.toml

title = "My awesome website"

[author]
name = "My name"
image = "img/author.jpg"
headline = "A generally awesome human"
bio = "A little bit about me"
links = [
  { twitter = "https://twitter.com/username" }
]

So I just make another snippet that points is something like

# config/_default/languages.en.toml

title = "My awesome website"

# config/_default/params.toml

[author]
name = "My name"
image = "img/author.jpg"
headline = "A generally awesome human"
bio = "A little bit about me"
links = [
  { twitter = "https://twitter.com/username" }
]

[jpanther]

I think this is on the right track, but I don't think moving the author params to params.toml is the correct solution as it will be difficult to localise. I have a feeling these need to move under the [params] block in the respective languages.[lang].toml file.

ie. we end up with:

[params.author]
name = "Name"

I haven't tackled this one yet as it's a bit of breaking change for users to migrate these values and so it needs a minor version bump. It might be valuable to test some fallback scenarios to determine if it can handle using both the values in the correct location and the old location. I also think this change could be bundled into a wider feature that implements multi-author functionality.

[Jh123x]

I think this is on the right track, but I don't think moving the author params to params.toml is the correct solution as it will be difficult to localise. I have a feeling these need to move under the [params] block in the respective languages.[lang].toml file.

ie. we end up with:

[params.author]
name = "Name"

I haven't tackled this one yet as it's a bit of breaking change for users to migrate these values and so it needs a minor version bump. It might be valuable to test some fallback scenarios to determine if it can handle using both the values in the correct location and the old location. I also think this change could be bundled into a wider feature that implements multi-author functionality.

Updated! Is the current implementation ok?

[jpanther]

That's much better, I think the only thing left to tweak is the warning message. It's directing people to the params.toml file when really it should just say that the author block needs to be changed to params.author in languages.xx.toml.

[jpanther]

Thanks, looks good. I'll merge it in later today.

[kelset]

hey @jpanther - thanks for maintaining this great theme! QQ: am I wrong or this fix hasn't made it yet in a released version? Sorry, I'm not sure familar with the whole Go ecosystem

[Jh123x]

hey @jpanther - thanks for maintaining this great theme! QQ: am I wrong or this fix hasn't made it yet in a released version? Sorry, I'm not sure familar with the whole Go ecosystem

I think it is just in dev and not in a release yet