You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @Ezzio Moreira - the website docs are setup so that that each language shows the entire set of doc pages. When a page localization does not exist, Hugo uses the English version as a “fallback”.
This provides, in my opinion, for a smoother user experience where a reader can choose to never leaves their locale pages, and they get to seamlessly see those (sporadic) pages that have been translated.
The alternative is to have (large) page gaps and holes in the locale’s docs, and force the user to “leave” their locale docs and to enter the English locale. But then it is becomes more of a challenge for the reader to figure out which pages are available in the reader’s originally intended locale (they have to consult the language dropdown for each page). In the current scheme, if the page is translated, then it simply is shown as is.
I suspect that @EzzioMoreira's question will pop up again, and so it might be worth considering ways to make this clearer for site readers, though I'm not entirely convinced that it's worth the effort given that it is in a sense obvious when a page hasn't been translated. (Of course, the doubt that arises, as it did for @EzzioMoreira, is whether this is a bug or a feature.) In any case, I'm creating this issue as a place to discuss options, and track any implemented solution.
One rather radical solution would be to drop fallback pages. From a usability point of view, I don't think that that is the best solution, but I'm willing to entertain it.
Another might be to mark fallback page titles in a special way in all or some of the following places:
The locale/language drop-down menu
The page title
The linkTitle (hence the left-nav) page title
The text was updated successfully, but these errors were encountered:
In this particular case, I've noticed that the path was changed from /concepts/instrumentation/zero-code.md to /concepts/instrumentation/zero-code/index.md, which resulted on showing the fallback translations for pages that were already translated.
Here is the PR that fixes it for both Portuguese and Japanese languages: #5882
I don't know if there are any other pages that might have changed also, I can take a look on it to see if I can find anything else.
However, about the discussion, it would be nice if we could show a small warning explaining that the translation for the requested page is not available yet.
I'm leaning towards some indication that the page is a fallback too, though, as I mentioned, I'm still not entirely convinced that it is worth the implementation effort. Glad to discuss this at our next Comms meeting on Jan. 20.
As for the updates to the pt and ja pages, see #5882 (review). As I mention there,
for all the details about handling non-English page drift (which must be done with care), see Keeping track of localized-page drift.
Here is part of a discussion from
#otel-docs-localization
. @EzzioMoreira wrote:Here's my (@chalin) response:
I suspect that @EzzioMoreira's question will pop up again, and so it might be worth considering ways to make this clearer for site readers, though I'm not entirely convinced that it's worth the effort given that it is in a sense obvious when a page hasn't been translated. (Of course, the doubt that arises, as it did for @EzzioMoreira, is whether this is a bug or a feature.) In any case, I'm creating this issue as a place to discuss options, and track any implemented solution.
One rather radical solution would be to drop fallback pages. From a usability point of view, I don't think that that is the best solution, but I'm willing to entertain it.
Another might be to mark fallback page titles in a special way in all or some of the following places:
title
linkTitle
(hence the left-nav) page titleThe text was updated successfully, but these errors were encountered: