Closed Bug 989115 Opened 11 years ago Closed 11 years ago

[tracker] Offer simple FAQ listing for non en-US locales

Categories

(support.mozilla.org :: Knowledge Base Software, task, P3)

Product:
support.mozilla.org
Component:
Knowledge Base Software
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
2014Q4

People

(Reporter: ibai, Assigned: rrosario)

References

Details

(Whiteboard: u=user c=wiki p=3 s=2014.18)

User Story

As a user, I'd like to access a list of all the localized articles on one page, instead of "hunting" through the entire taxonomy only to find English articles. Ideal: the list would have sections for each product (this can be a simple header) to make it easier to read.
As part of the simplification of our l10n efforts (i.e. less work to have a locale in a good shape in languages with small communities) we want to offer the option to present a list of all the localized articles instead of showing them within the category structured inherited from en-US. This means that when a user in that small locale access support.mozilla.org they will see a list of all the articles in that language (and if they land in a product landing page, they will be redirected to that home page). For now, we will curate that list manually within one article. So we just need to switch, in the locales that are part of this program, an "index" article instead of the list of products listed in boxes as we do today. We will keep iterating in this page as needed to make that list automatic, etc.
So, I'm assuming this is meant as a tracker bug. Couple of questions off the top of my head that we might want to discuss: * Would we have one list for all products? * How do we select the articles that are presented? Just the top 20? From in-product articles? * What happens to articles that the community decides to localize that are not part of our FAQ? * Do we need to modify the L10n dashboard for those locales? * Do we require all articles to be localized at all time for this FAQ? * What do we do, if some articles are not localized yet?
Summary: Offer simple FAQ listing for non en-US locales → [tracker] Offer simple FAQ listing for non en-US locales
Target Milestone: --- → 2014Q2
Kadir, this is a much simple solution. A very first iteration over what we will be doing later this year. If you want to keep this as a tracker, that works for me. For now, until a new L10n expert comes on board we want: - To "deface" SUMO in those locales that the coverage is very low (list will be provided) and turn product landing pages and /home into a simple article that those locales can mantain manually. - The article will serve as a manually curated list of articles that they have translated or they have created on their own. - It will cover all the products in one single place. Over time we will add functionality like the one you describe to make it more automated.
Ricky and Kadir, I looked at pages per session (2 on average) for some of the locales but realized that it's not going to be an accurate comparison. The fact that localized articles are harder to find in these countries might be the reason why users click on more than one page. I talked to Ibai more about this. Regarding whether or not we should remove the sidebar and other navigation elements from the article page, we should do whatever is easiest as long as we have the list of articles as the landing page. We can wait until we have more data and/or an L10N expert before changing all the other components. We can talk more about this in the coming week and at the meetup.
User Story: (updated)
Here are some specs for this page: *The article list page can be a simple wiki article (sample shown here: https://support.allizom.org/en-US/kb/sample-l10n-page). The L10N team (when available) and I can put the list together ourselves. *If a user clicks on a product or a topic, they'll be redirected to the article list page. We don't need to get rid of the sidebar or other navigational elements as long as we redirect the users to the article list page if they click on the sidebar. *This page won't have an English parent. It will be completely unique to its locale and won't be tied to other locales.
Looking at the calendar Q2 (targeted above) seems unlikely now. When can terminated locales expect a possibility to translate something again?
Hi Merike, we were going to test this with one locale before rolling out a plan with the remaining locales. Since the locale leader I'm working with has been busy, we can test it on your locale if you'd like. If you're interested, you and I can hand-pick articles that are important to your locale, localize them, then list them on the new L10N page. Any thoughts?
It depends on the time required. I don't have much that I can spend on SUMO (which is why I want to have SUMO open to potential new Estonian contributors and their contributions) If it was possible to recover the content (although outdated) that Estonian already had on Firefox (at least 3 articles) and Thunderbird (2 articles I think) then I could find the time to update these and perhaps translate two or three additional ones. So it wouldn't be more than 10 articles total. If that's enough then I don't see a reason not to test one more thing :)
Hi Joni, Merike - checking in on this as I get into my SUMO L10n shoes. Is there anything I can help with at this stage?
Hi, Michal. Merike and I haven't started on this, so please feel free to jump in. Merike, I'm sorry for not responding earlier. I missed the bugmail for your last comment. Now that Michal's here, we're in good hands. Joni
Great! @Merike - I'll see if I can dig up the existing Estonian content you mentioned. In the meantime, let's decide which additional articles you could tackle, if you have the time. Thank you for your help with this!
> @Merike - I'll see if I can dig up the existing Estonian content you > mentioned. In the meantime, let's decide which additional articles you could > tackle, if you have the time. If I was choosing myself I'd pick them from the following list: * https://support.mozilla.org/en-US/kb/reset-firefox-easily-fix-most-problems * https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode * https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding * https://support.mozilla.org/en-US/kb/firefox-crashes-troubleshoot-prevent-and-get-help Did you have any specific criteria(s) in mind for picking them?
@Merike - these look good. My criteria probably matches yours - the most popular / practical articles in SUMO. Basically, anything from the top 20 at https://support.mozilla.org/en-US/contributors?product=firefox that addresses the most widespread issues or user questions. I haven't found the old articles, so I'll assume they've been burned completely. Are you on IRC or Vidyo? We could also meet and talk about finding more contributors in Estonia, in general. @Kadir - any chance the retired articles are hovering somewhere in the archives?
Flags: needinfo?(a.topal)
(In reply to mdziewonski from comment #13) > Are you on IRC or Vidyo? We could also meet and talk about finding more > contributors in Estonia, in general. I'm usually on #l10n channel but detached most of the time. There's probably no silver bullet for finding new contributors though :)
Depends on: 1071055
Flags: needinfo?(a.topal)
Whiteboard: u=user c=wiki p=3 s=2014.18
Priority: -- → P3
Assignee: nobody → rrosario
Target Milestone: 2014Q2 → 2014Q4
To catch the situation here up with out of bug discussions: * Yes, retired locales can be reactivated, and their previous content will also be available again * We are going forward with this feature in this sprint. What that means is: ** We'll create an English article/page that participating locales can localize. ** For those locales that participate, we'll show that article/page anytime someone hits a /products url
What is the list of locales that should get this feature?
Flags: needinfo?(mdziewonski)
Flags: needinfo?(a.topal)
mdziewonski, one thing that needs to be setup for us to land this is the base wiki article in en-US. I'm assuming that the slug will be 'faq' but let me know if you want something else. Thanks.
The code is in a pull request: https://github.com/mozilla/kitsune/pull/2145 The settings are still TBD based on Comment 17 and Comment 16
Michael will provide the locales and write the article for it.
Flags: needinfo?(a.topal)
Here's the URL for the article: https://support.mozilla.org/en-US/kb/frequently-asked-questions The locales are listed in https://bugzilla.mozilla.org/show_bug.cgi?id=1071055, and are as follows: - et - fy-NL - gu-IN - ur
This is ready to land. Please let us know when everything is all set with the content.
Flags: needinfo?(a.topal)
I'm removing the needinfo on me. The okay will come directly from Michal as soon as he is done with the article.
Flags: needinfo?(a.topal)
Update: I have the article ready in English; waiting for the localizers to have a go at it.
Flags: needinfo?(mdziewonski)
Thanks for the update, Michal. Once you think this is ready to go, please let Ricky know, he'll flip the swithch.
What's the status here? The code changes to make this work are still sitting in a PR.
We're ready to go for Estonian, so you can put the redirect in place for /et/: If I remember correctly, the way it should work is a one-time entry-level redirect for all Estonian users going to SUMO to this page: https://support.mozilla.org/et/kb/korduma-kippuvad-kusimused From there, they should be able to go wherever they want, and we'll display non-localized content in EN, as usual. Other locales are coming a bit later (depending on contributors' availability).
Actually, the way this is implemented is that all the IA pages (product picker page, product landing page, topic landing page) are all redirected to the FAQ article.
Group: websites-security
oops. not sure how I did that.
Group: websites-security
Landed on master: https://github.com/mozilla/kitsune/commit/66a43ddd6a6fcf61d5b367c16e7fc06fb53716b7 Only 'et' is enabled for now. This will be deployed to prod next week.
That's great news, Ricky - thanks. Is there a way to preview this on allizom? https://support.allizom.org/et is not triggering anything there yet.
Flags: needinfo?(rrosario)
(In reply to mdziewonski from comment #30) > That's great news, Ricky - thanks. Is there a way to preview this on > allizom? https://support.allizom.org/et is not triggering anything there yet. Deployed to stage now. The problem is that stage doesn't have the FAQ article so it 404s: https://support.allizom.org/et/kb/frequently-asked-questions
Flags: needinfo?(rrosario)
Deployed to prod now. https://support.mozilla.org/et redirects to https://support.mozilla.org/et/kb/korduma-kippuvad-kusimused
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.