Revamp minikube website footer

[sandipanpanda]

Fixes: #18055

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[minikube-bot]

Can one of the admins verify this patch?

[spowelljr]

@sandipanpanda I know it's in draft so if you're aware and still working on this ignore this, but I'm not seeing your change in the footer

https://deploy-preview-18062--kubernetes-sigs-minikube.netlify.app/

[sandipanpanda]

Here's link to the Hugo config

https://www.zerostatic.io/docs/hugo-shard/global-config/footer/

@spowelljr I was following the documentation for the footer you shared in the issue. I think it is for a custom hugo theme, not the one minikube uses.

[sandipanpanda]

Changes seem to work now: https://deploy-preview-18062--kubernetes-sigs-minikube.netlify.app/docs/

[spowelljr]

Great work! Could you also style it to white so it matches the rest of the footer?

[sandipanpanda]

Done!

[spowelljr]

Awesome @sandipanpanda, this looks great! One last request if you're willing, to match the rest of the links on our site it would be nice if it changed color on hover to help the users know it's a link. I was thinking something around #b5b1b1 maybe?

[sandipanpanda]

@spowelljr what do you think about keeping them the default blue to indicate they are clickable links?

[sandipanpanda]

/cc @medyagh

[spowelljr]

@spowelljr what do you think about keeping them the default blue to indicate they are clickable links?

I don't think the contrast of the blue on a gray background visually goes together. I think having them change shade on hover would be enough.

[k8s-triage-robot]

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

[medyagh]

@sandipanpanda do you mind addressing steven's review so we could merge this pr

[sandipanpanda]

/cc @medyagh @spowelljr
PTAL

[spowelljr]

Looks good, thanks for the PR!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sandipanpanda, spowelljr

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [spowelljr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment