Upgrade Hugo and Docsy

[chalin]

The versions of Hugo and Docsy are quite old.

contributor-site/netlify.toml

Lines 5 to 6 in 1a8d9c6

	[build.environment]
	HUGO_VERSION = "0.69.2"

For example, Hugo 0.69.2 was released in April 2020.

/cc @nate-double-u

[chalin]

Why upgrade? E.g., Docsy's current page-feedback feature is incompatible with GA4 (google/docsy#1302). Since UA is being deprecated and this site is being migrated to GA4 (#354), the a new version of Docsy will eventually be needed. (There is a work-around for the page-feedback issue, so the upgrade isn't urgent.)

[jberkus]

Is this something you can help with?

[sftim]

I agree that it's useful to upgrade.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[jberkus]

/remove-lifecycle stale

We were able to upgrade to 0.89, but remain stalled on the upgrade to 110.

[sftim]

See the revised PR, #374

[chris-short]

We did spend some time on this during the Contributor Summit at KubeCon Chicago. @jeefy's fork has some errors we need to work through but, we've made a step forward here.

[sftim]

What still needs to happen before we can call this Done?

[jeefy]

I'm back and working through said errors (actually I started from scratch and scrapped my post-lunch hastily-done branch)

Most errors that we encountered at the summit are fixed, and the last thing I'm updating is the Dockerfile. PR inc soon.

[jeefy]

Oh duh.

/assign

[chris-short]

Were you going to tackle the move from submodules to Hugo Modules? I can do that separately if you'd like.

I also want to update the K8s.dev picture now that we have a big crowd pic for a replacement.

[jeefy]

Kinda did it all, see here: #456

Need help with a CSS issue post-migration but otherwise it's all done and clean.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[jberkus]

/remove-lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[stmcginnis]

/remove-lifecycle stale

[stmcginnis]

Looks like we're up to Hugo 0.124 now. There is a slightly newer release out, but I think it's just regular dependency management at this point. Follow-on work being done in #456. I think it's safe to close this issue now.

/close

[k8s-ci-robot]

@stmcginnis: Closing this issue.

In response to this:

Looks like we're up to Hugo 0.124 now. There is a slightly newer release out, but I think it's just regular dependency management at this point. Follow-on work being done in #456. I think it's safe to close this issue now.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.