Changes on the pages for contributors are not trackable for changes which need update

RESOLVED WONTFIX

Status

support.mozilla.org
Localization
RESOLVED WONTFIX
6 years ago
3 years ago

People

(Reporter: JasnaPaka, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

6 years ago
On the dashboard localizer can see which articles need updates (or urgent updates). That's fine but it looks like it doesn't work for pages for contributors. I'm in the situation when on the dashboard I see that all translations are actual.

https://support.mozilla.org/cs/localization
- no articles for update

But on the page with all articles I can see that some pages need update (or urgent update).

https://support.mozilla.org/cs/localization/most-visited-translations

I talk about pages for contributors like:
* https://support.mozilla.org/en-US/kb/superheroes-wanted
* https://support.mozilla.org/en-US/kb/meet-team
* https://support.mozilla.org/en-US/kb/localize-firefox-help

I would like to see information about situations when these articles need updates on the dashboard.

(I'm going to update translations for these articles. So it is possible that you will see translations marked as up-to-date in the future.)
This sounds like we need a section on the localization dashboard for articles in the "How to contribute" category.
Pavel, they don't show up, because they are "how to contribute" articles, we removed them from the dashboard because some are updated quite often and they are not user-visible, so they would get more attention that necessary on the localization dashboard. Maybe we should revisit that decision, and as Ricky said, we could create a special category for them.

Updated

6 years ago
Severity: normal → minor

Updated

6 years ago
Severity: minor → normal
Uhm. How do we still feel about this at this moment?

Comment 4

3 years ago
I think we can leave those pages the way they are (since they're 'internal' to the community, in a way), and if we need them to be localized, we can always start a separate effort for that, not to get in the  way of the much more important and impactful support KB l10n.

If you strongly disagree, please reopen this bug.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.