SUMO community discussions

[Attn: Admin/Abby] Pocket help center migration to SUMO

  • 8 Replies
  • Last reply by Michele Rodaro
  1. Abby
    Abby 36 posts Mozilla Staff
    more options

    Hi everyone! We are kicking off the process of migrating the current Pocket Help Center (managed through an external content management system called HelpScout) over to SUMO! This will help make our content updates for Pocket more efficient, and also enable our amazing localization contributors to help us translate Pocket KB content for our users across the world.

    We will begin the process of adding EN-US articles to SUMO next week and are aiming to complete the migration by mid-September. Please do not make any changes or localize any of the content until we provide a further update that all of the content has been completely and correctly moved over. We will also be QAing all of the articles once we've finished the migration, ensuring links work, images load, etc.

    We will be in touch soon with more details, best practices & processes for helping to maintain and localize Pocket support content in the future, but we wanted to be sure to give you a heads up in case you notice Pocket content appearing in search results/dashboards/etc.

    Please let me know if you have any questions! Thank you! Abby

    Hi everyone! We are kicking off the process of migrating the [https://help.getpocket.com/ current Pocket Help Center] (managed through an external content management system called HelpScout) over to SUMO! This will help make our content updates for Pocket more efficient, and also enable our amazing localization contributors to help us translate Pocket KB content for our users across the world. We will begin the process of adding EN-US articles to SUMO next week and are aiming to complete the migration by mid-September. '''Please do not make any changes or localize any of the content until we provide a further update that all of the content has been completely and correctly moved over. ''' We will also be QAing all of the articles once we've finished the migration, ensuring links work, images load, etc. We will be in touch soon with more details, best practices & processes for helping to maintain and localize Pocket support content in the future, but we wanted to be sure to give you a heads up in case you notice Pocket content appearing in search results/dashboards/etc. Please let me know if you have any questions! Thank you! Abby
  2. AliceWyman
    AliceWyman 6313 posts
    more options

    See Bug 1843171 - Update FxA account migration article - Kobo question (comment 5) regarding these duplicate articles:

    The FAQ article was apparently copied from https://help.getpocket.com/article/1187-pocket-migration-to-firefox-accounts Pocket Transition to Firefox Accounts - FAQ Related github issue: https://github.com/mozilla/sumo/issues/1414 Create a webhook to redirect Pocket to KB articles Related discussion: https://support.mozilla.org/en-US/kb/pocket-transition-firefox-accounts-faq/discuss/11631 New link: https://support.mozilla.org/en-US/kb/pocket-migration-to-firefox-accounts/discuss/11631 ^ new link is due to a change in the FAQ article's URL ("slug")

    See [https://bugzilla.mozilla.org/show_bug.cgi?id=1843171#c5 Bug 1843171] - Update FxA account migration article - Kobo question (comment 5) regarding these duplicate articles: *[[Pocket Transition to Firefox Accounts]] *[[Pocket Transition to Firefox Accounts - FAQ]] The FAQ article was apparently copied from https://help.getpocket.com/article/1187-pocket-migration-to-firefox-accounts Pocket Transition to Firefox Accounts - FAQ Related github issue: https://github.com/mozilla/sumo/issues/1414 Create a webhook to redirect Pocket to KB articles Related discussion: <s>https://support.mozilla.org/en-US/kb/pocket-transition-firefox-accounts-faq/discuss/11631</s> New link: https://support.mozilla.org/en-US/kb/pocket-migration-to-firefox-accounts/discuss/11631 <sub>^ new link is due to a change in the FAQ article's URL ("slug") </sub>

    Modified by AliceWyman on

  3. TyDraniu
    TyDraniu 163 posts
    more options

    Shouldn't be Pocket a new separate product on a localization dashboard?

    Shouldn't be Pocket a new separate product on a localization dashboard?
  4. AliceWyman
    AliceWyman 6313 posts
    more options

    I see that Pocket is now a separate product, for example: https://support.mozilla.org/pl/contributors?product=pocket https://support.mozilla.org/en-US/contributors/kb-overview?product=pocket https://support.mozilla.org/products/pocket https://support.mozilla.org/questions/new/pocket

    I see that Pocket is now a separate product, for example: https://support.mozilla.org/pl/contributors?product=pocket https://support.mozilla.org/en-US/contributors/kb-overview?product=pocket https://support.mozilla.org/products/pocket https://support.mozilla.org/questions/new/pocket
  5. AliceWyman
    AliceWyman 6313 posts
    more options

    P.S. Related post on adding Pocket to Article review and approval guidelines: https://support.mozilla.org/en-US/forums/knowledge-base-articles/716332#post-86217

    P.S. Related post on adding Pocket to [[Article review and approval guidelines]]: https://support.mozilla.org/en-US/forums/knowledge-base-articles/716332#post-86217
  6. Michele Rodaro
    Michele Rodaro 443 posts
    more options

    Hi, I have a question about Pocket articles. I have localized some of these articles into Italian. In the Italian dashboard, most of the untranslated articles concern Pocket ones. All articles of other Mozilla products have been translated into Italian and updated.

    The problem with Pocket articles is that many of the articles published on SUMO after the migration from the Pocket site often contain broken links, instructions not updated with the latest versions of the Pocket apps for Android or iOS but often not even for Pocket for desktop (screenshots, elements of the user interface, etc.). I wanted to ask if there is any Content Manager or Reviewer who can review the Pocket articles and update them so that we localizers can translate them without going crazy ;-)

    Another big problem is that often, at least as far as I'm concerned, some UI elements are not translated and often they are still in English so we don't know if we have to translate them based on our translation or if they will sooner or later be translated.
    Usually all Mozilla products are localized on Pontoon but it seems to me that external translators were used for the Pocket interface translations, and if there is some element of the interface that should be updated, it is not possible for us localizers to update those translations.
    Some examples in the Pocket for Firefox desktop UI: "Highlights" is still in English and in Italian it should be "Evidenziati"; "Tags" is "Tag" and should be "Etichette"; "All Tags" is "Tutti i tag" and should be "Tutte le etichette"... and so on. So, when we translate the Pocket articles on SUMO, if we write the name of the elements we don't know whether to use what we see in the interface or what the exact translation should be in our language.

    Another problem is that there are often articles that say exactly the same things, duplications that should be unified in a single article.

    I apologize for this long message and I hope I have made clear some of the problems with the Pocket articles that I would like to localize but which, as they are now, I don't want to localize because they are not completely correct.

    Thanks in advance,
    Michele

    Hi, I have a question about Pocket articles. I have localized some of these articles into Italian. In the Italian dashboard, most of the untranslated articles concern Pocket ones. All articles of other Mozilla products have been translated into Italian and updated. The problem with Pocket articles is that many of the articles published on SUMO after the migration from the Pocket site often contain broken links, instructions not updated with the latest versions of the Pocket apps for Android or iOS but often not even for Pocket for desktop (screenshots, elements of the user interface, etc.). I wanted to ask if there is any Content Manager or Reviewer who can review the Pocket articles and update them so that we localizers can translate them without going crazy ;-) Another big problem is that often, at least as far as I'm concerned, some UI elements are not translated and often they are still in English so we don't know if we have to translate them based on our translation or if they will sooner or later be translated. <br>Usually all Mozilla products are localized on Pontoon but it seems to me that external translators were used for the Pocket interface translations, and if there is some element of the interface that should be updated, it is not possible for us localizers to update those translations. <br>Some examples in the Pocket for Firefox desktop UI: "Highlights" is still in English and in Italian it should be "Evidenziati"; "Tags" is "Tag" and should be "Etichette"; "All Tags" is "Tutti i tag" and should be "Tutte le etichette"... and so on. So, when we translate the Pocket articles on SUMO, if we write the name of the elements we don't know whether to use what we see in the interface or what the exact translation should be in our language. Another problem is that there are often articles that say exactly the same things, duplications that should be unified in a single article. I apologize for this long message and I hope I have made clear some of the problems with the Pocket articles that I would like to localize but which, as they are now, I don't want to localize because they are not completely correct. Thanks in advance,<br>Michele
  7. AliceWyman
    AliceWyman 6313 posts
    more options

    Abby wrote in her August post (see above): We will also be QAing all of the articles once we've finished the migration, ensuring links work, images load, etc.

    Hopefully Abby or another staff member will reply here, to let us know the QA status. I added "[Attn: Admin/Abby] to the thread title. In case it helps, here is a list of en-US Pocket articles: https://support.mozilla.org/en-US/contributors/kb-overview?product=pocket

    Abby wrote in her August post ([https://support.mozilla.org/en-US/forums/contributors/716486#post-85974 see above]): ''We will also be QAing all of the articles once we've finished the migration, ensuring links work, images load, etc. '' Hopefully Abby or another staff member will reply here, to let us know the QA status. I added "[Attn: Admin/Abby] to the thread title. In case it helps, here is a list of en-US Pocket articles: https://support.mozilla.org/en-US/contributors/kb-overview?product=pocket
  8. Kiki
    Kiki 1693 posts Mozilla Staff
    more options

    Michele Rodaro said

    I wanted to ask if there is any Content Manager or Reviewer who can review the Pocket articles and update them so that we localizers can translate them without going crazy ;-)

    Hi Michele,

    Thanks for sharing your feedback about Pocket articles. We've talked about it during our community call yesterday and here's the summary of what we talked about:

    • Outdated content: while the team is aware of some of the outdated content, we reluctant to fix it now because Pocket product team is still working on planning the strategy for 2024 and beyond. Once we know more from them, we should be able to prioritize the work and take actions. If you're interested in helping us to update the content, please go ahead and tag Dayani (Technical Writer) or Olivia (Support Manager for Pocket) if you have any questions along the way (see Meet the Team page for their contact detail].
    • Pocket UI strings: Justin were able to export the strings (EN and the localized version too). We could find a way to transfer those strings to you if necessary.
    • Duplicate content: this might be intentional unless it's about 2 articles that contain exactly the same thing. My suggestion is, if you found something that can be simplied using template, feel free to propose changes to those articles. Otherwise, it's ok to leave them for now.

    That being said, if you don't want to localize the Pocket content for one reason or another, we could totally understand. More importantly, Pocket should be deprioritize in general compared to the other products.

    ''Michele Rodaro [[#post-86293|said]]'' <blockquote> I wanted to ask if there is any Content Manager or Reviewer who can review the Pocket articles and update them so that we localizers can translate them without going crazy ;-) </blockquote> Hi Michele, Thanks for sharing your feedback about Pocket articles. We've talked about it during our [https://support.mozilla.org/en-US/forums/contributors/716580?last=86305 community call] yesterday and here's the summary of what we talked about: * Outdated content: while the team is aware of some of the outdated content, we reluctant to fix it now because Pocket product team is still working on planning the strategy for 2024 and beyond. Once we know more from them, we should be able to prioritize the work and take actions. If you're interested in helping us to update the content, please go ahead and tag Dayani (Technical Writer) or Olivia (Support Manager for Pocket) if you have any questions along the way (see [[Meet the Team]] page for their contact detail]. * Pocket UI strings: Justin were able to export the strings (EN and the localized version too). We could find a way to transfer those strings to you if necessary. * Duplicate content: this might be intentional unless it's about 2 articles that contain exactly the same thing. My suggestion is, if you found something that can be simplied using template, feel free to propose changes to those articles. Otherwise, it's ok to leave them for now. That being said, if you don't want to localize the Pocket content for one reason or another, we could totally understand. More importantly, Pocket should be deprioritize in general compared to the other products.
  9. Michele Rodaro
    Michele Rodaro 443 posts
    more options

    Hi Kiki,
    First of all welcome back on board. I'm really happy that you are with us again. I missed you and I hope that your maternity was happily "rewarded". I would have liked to write you a few private messages to find out how you were and how maternity was going, but then I thought you needed more privacy during this period (:

    I apologize for the delay in responding to your message.

    Regarding Pocket articles, thanks for the info. From what you wrote I understand the situation.

    Kiki ha detto

    * Pocket UI strings: Justin were able to export the strings (EN and the localized version too). We could find a way to transfer those strings to you if necessary.
    This seems like very interesting information to me. If you could find a way to transfer those strings to me, I think that might be helpful, then I'll figure out how to move when I get the strings.

    I want to localize Pocket articles, I have never held back with localizations (…and you know it) and, apart from Pocket, so far I have always localized and updated all articles of all Mozilla products. The only thing holding me back at the moment are the contents which are often obsolete, some difficulties with the UI and some other difficulties with the localization of some UI strings for the various operating systems. For Pocket on desktop or for the Android app I can often find the references more easily on my Mac and smartphone, but for the iOS app, not having an iOS smartphone, it becomes more complicated to verify steps and UI.

    I send you a big virtual hug and await, if possible, the Pocket UI strings ;)
    Michele =)

    Hi Kiki, <br>First of all welcome back on board. I'm really happy that you are with us again. I missed you and I hope that your maternity was happily "rewarded". I would have liked to write you a few private messages to find out how you were and how maternity was going, but then I thought you needed more privacy during this period (: I apologize for the delay in responding to your message. Regarding Pocket articles, thanks for the info. From what you wrote I understand the situation. ''Kiki [[#post-86313|ha detto]]'' <blockquote>* Pocket UI strings: Justin were able to export the strings (EN and the localized version too). We could find a way to transfer those strings to you if necessary. </blockquote>This seems like very interesting information to me. If you could find a way to transfer those strings to me, I think that might be helpful, then I'll figure out how to move when I get the strings.<br><br> I '''want''' to localize Pocket articles, I have never held back with localizations (…and you know it) and, apart from Pocket, so far I have always localized and updated all articles of all Mozilla products. The only thing holding me back at the moment are the contents which are often obsolete, some difficulties with the UI and some other difficulties with the localization of some UI strings for the various operating systems. For Pocket on desktop or for the Android app I can often find the references more easily on my Mac and smartphone, but for the iOS app, not having an iOS smartphone, it becomes more complicated to verify steps and UI. I send you a big virtual hug and await, if possible, the Pocket UI strings ;)<br> Michele =)