Improve use of space for docs

[chbrandt]

Documentation pages provide two tables of content: one -- on the left -- for the whole site, and the other -- on the right -- for the current document. For instance, I'm at Updating Configuration via a ConfigMap. The one on the right is using too much space and should be moved somewhere else (see screenshots); My suggestion is to move it also to the left, below/above the site's ToC.

Notice the amount of empty space on the (right side) pages that could be used for a better (reading) experience:

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[network-charles]

This is a hugo theme called docsy.

[sftim]

/area web-development

[chbrandt]

Thanks for the info @network-charles . Using docsy example image, here is what I'm proposing:

I never played with Hugo, but I understand those themes can be customised.
On the side: I took the chance to visit the themes gallery, Relearn seems to provide the layout I am proposing.

[network-charles]

Oh, nice.

It’ll be great for you to discuss your proposal at the SIG Docs meeting tomorrow. Changing a theme is a major change from a UI/UX perspective. But if you are customizing the existing one then that's a minor change.

[AmarNathChary]

Thanks for the info @network-charles . Using docsy example image, here is what I'm proposing:

I never played with Hugo, but I understand those themes can be customised. On the side: I took the chance to visit the themes gallery, Relearn seems to provide the layout I am proposing.

It's a good idea. IMO the content length on the right side changes according to the pages we are in. We can have an extra slide bar for this WDYT?

[chbrandt]

@network-charles

It’ll be great for you to discuss your proposal at the SIG Docs meeting tomorrow. Changing a theme is a major change from a UI/UX perspective. But if you are customizing the existing one then that's a minor change.

I miss that message in due time. Where do I find information for the next meeting?

[chbrandt]

@AmarNathChary

We can have an extra slide bar for this WDYT?

Yes, that would work too. Even better, I'd say.

[network-charles]

I miss that message in due time. Where do I find information for the next meeting?

https://kubernetes.slack.com/

After joining the workspace, join the #sig-docs channel. All the information you need are on the channel info section.

[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