kubernetes / kubernetes/website
Improve outdated content warning on localized pages
- Dominant language
- HTML
- Stars
- 5.4k
- Forks
- 15.7k
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 204
Description
**This is a Feature Request**
This issue is to continue to improve the "outdated content" warning on localization pages introduced in https://github.com/kubernetes/website/pull/41768. This automation adds a warning message to localization pages when the English version of the page has been updated more recently than the localized page. This is determined by comparing the `Lastmod` of a page in English and a given Localization.
Example of the warning on https://kubernetes.io/fr/docs/home/
**Why is this needed**
I'm opening this issue to get more feedback from the localization teams of how this change has impacted their content and readers. The original intention of this change (see https://github.com/kubernetes/website/issues/41519) was to help readers of localized content know if content might be outdated and help them find the most current information. As noted in the [PR](https://github.com/kubernetes/website/pull/41768), there were some concerns about the message wording causing confusion or the automation logic being to simplified.
For example, @seokho-son mentioned in our latest Localization meeting that the Korean team has been experiencing many false instances of the warning message appearing on Korean pages. For example, if a minor change like fixing spaces is made to an English page, the Korean content does not need to be updated because the word spacing is different, but the outdated content warning will show up on the Korean page.
For localization teams:
* Have you noticed any cases where the warning message is showing up on pages where it shouldn't?
* Please share any feedback from readers or localization teams about the message.
Contributor guide
Research direction
Review the existing warning introduced in pull request 41768, the background in issue 41519, and the example on the French localization page. Gather the requested feedback from localization teams, especially the reported Korean false positives, and define an agreed message or automation change before implementation can be considered complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation, localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100