[BUG] Language Switcher Missing on Navigation Pages

[tejasvising]

Describe the bug.

When on the homepage, the language selector shows both "English" and "Deutsch" options. After clicking any top-level navigation link in the header (e.g., Docs, Tools, Community etc) that opens a new page, the language selector only shows "English" and the "Deutsch" option disappears. This happens across desktop, tablet, and mobile viewports.

Expected behavior

The language selector should consistently show both "English" and "Deutsch" on every page, including Docs, Tools, and other navigation targets.

Screenshots

Initial Scenario:

After navigating to any other page(Example Community page):

Notice that there was an option to switch language to Deutsch at homepage which disappears on moving to another page.

How to Reproduce

1. Open the homepage.
2. Open the language selector; observe both "English" and "Deutsch" options.
3. Click any navigation link (e.g., Docs, Tools, etc.).
4. Open the language selector again; only "English" is available.

🖥️ Device Information [optional]

• Operating System (OS):
• Browser:
• Browser Version:

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

Yes I am willing to submit a PR!

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[princerajpoot20]

This is happening because, at the moment, we only have the Deutsch translation present for the home page and the tools/cli page. If we want to have this option on the remaining pages, we need to add the translations.

I’m not sure about you going ahead with adding the Deutsch translation since you don’t know this language. I would prefer it to come from someone who knows the language, so that we have an additional eye on the text from that person’s point of view.

@derberg what are your views on this?

[NobleCoder69]

Thanks for the clarification @princerajpoot20 🙏

I understand that Deutsch translations are currently available only for the homepage and tools/cli pages.

Instead of adding translations myself, would it be acceptable if I:
• Keep Deutsch visible in the language switcher
• Disable it on pages where translations are missing
• Add a tooltip or helper text explaining that German is only available on selected pages

This would improve UX without introducing incorrect translations.

Please let me know if this approach works. Happy to submit a PR.

[theAnuragMishra]

@NobleCoder69 don't you think it would be better to add the switcher when the translations are available? there's no use of having translation on two pages.

[NobleCoder69]

I agree
Showing the language switcher when translations exist for only a few pages can confuse users and create false expectations.

It’s better to display the switcher only on pages where translations are available, or enable it site-wide once more Deutsch translations are added.

[SanidhyaMadheshia]

@tejasvising the solution @theAnuragMishra gave is what should be done for quick soln , but for a long run I think we should do care about other users as the users who is comfortable in landing should also be comfortable with other pages in the same language . This can improve the ux .
I would really love to draw feature out of a bug .
can you please assign me this issue
let me know