Mobile menu theme and language configuration

[magicDGS]

What version of starlight are you using?

0.11.1

What is your idea?

Currently on mobile the menu shows the theme and language on the footer (and maybe the social icons, if they are shown there after #978). The idea would be to configure if those components are in a header or a footer (or any other solution to fix the issue described below).

Why is this feature necessary?

For small size documentation, the current behavior might be fine, but for large documentation the user might need to scroll to the end just to see those options.

In addition, this combined with the problems described in #977 and #978 are making the experience with mobile a bit clunky.

Last but not least, if an extension like starlight-blog (see also #948) is used and the component still behaves in the same way (footer), accessing the blog from mobile (more common than accessing the full documentation) might be difficult.

Do you have examples of this feature in other projects?

No response

Participation

• I am willing to submit a pull request for this feature.

[newtoallofthis123]

Interesting idea! I had a similar problem as well 😅

[HiDeoo]

Not to say the idea is not interesting, on the contrary, but I wanted to mention that component overrides already allow for users to potentially override this behavior if this is something blocking/annoying for them to wait for a potential built-in solution to address this.

For example, in starlight-blog as it was mentioned, we use that to always render the blog link above the sidebar content on mobile:

[magicDGS]

Thanks for the hint. I will use that in the meantime!

[delucis]

Thanks for the suggestion! I wonder if making that footer section sticky could be a good solution instead of a configuration option? That way, the language/theme options would always be visible and just the navigation links scroll.

As @HiDeoo says, this should be possible today with component overrides, but definitely something to think about whether we can also improve the default behaviour.

[magicDGS]

Thanks for the response. Making it sticky sounds like a better solution, I was just suggesting a configuration not to be intrusive in the current behavior. I am kind of new on terms of UI/UX and accessibility, so I don't feel that I have the knowledge to do strong suggestions such that.