Skip to content

www: add markdown language switcher#658

Closed
missytake wants to merge 1 commit intomainfrom
markdown-language-switcher
Closed

www: add markdown language switcher#658
missytake wants to merge 1 commit intomainfrom
markdown-language-switcher

Conversation

@missytake
Copy link
Contributor

From #614 - but it really is its own feature, so it should be in a separate PR.

@missytake missytake force-pushed the markdown-language-switcher branch from 51d557e to 62f028b Compare October 7, 2025 20:16
Copy link
Contributor

@hpk42 hpk42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for moving this out of the big docker PR!
i am however very skeptical to complicate the current web page with translations.
I'd rather suggest to reduce/streamline it, also because with multi-transport people will look at the web page even less than today, and rather have a documented way have arbitrary custom web pages managed outside the relay repo.

@missytake
Copy link
Contributor Author

Closing this for now, we have too many open PRs and it's not clear we want this. In general, it is much easier to design a completely custom web page by now: https://chatmail.at/doc/relay/getting_started.html#custom-web-pages

@missytake missytake closed this Mar 5, 2026
@r10s
Copy link
Contributor

r10s commented Mar 5, 2026

+1 for closing. this seems are premature optimisation.

in practise, the relays we got aware over the last months, are pretty locally targeted - and are already translated then, to the locals they want to support.

and if a relay operator really wants to support different languages, they can do that by the tools available - if in doubt, add a "see english below", some js or whatnot. this seems nothing we need to think about currently.

@missytake missytake mentioned this pull request Mar 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants