<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Simplest Workflow for Translated Pages in Community Central forum</title>
    <link>https://www.servicenow.com/community/community-central-forum/simplest-workflow-for-translated-pages/m-p/3519586#M6563</link>
    <description>&lt;P&gt;Hello! In our business, we frequently translate end-user facing content into 20+ languages. To spare the details, the basic process is: build the page (typically knowledge article) in English, extract the html, send that to our localization team, receive the translations back in html format, then &lt;EM&gt;create child pages for each translation and insert the provided html - &lt;/EM&gt;the last bit is extremely time consuming. The result is an English parent page with a drop down menu to select the other languages. When visiting the permalink for the page, the language selection defaults to the user's preferred language in SNOW.&lt;BR /&gt;&lt;BR /&gt;Does anyone have a more efficient process they are using for translations management? Ideally I'm looking for an import solution, or a way we could send the English page directly to localization and receive it back in platform, review for accuracy, and publish - eliminating the time consuming and error prone copy/paste. We're open to any ideas that would make this simpler, even if it means building the pages differently.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Fri, 03 Apr 2026 16:58:48 GMT</pubDate>
    <dc:creator>AnnaHeneghan</dc:creator>
    <dc:date>2026-04-03T16:58:48Z</dc:date>
    <item>
      <title>Simplest Workflow for Translated Pages</title>
      <link>https://www.servicenow.com/community/community-central-forum/simplest-workflow-for-translated-pages/m-p/3519586#M6563</link>
      <description>&lt;P&gt;Hello! In our business, we frequently translate end-user facing content into 20+ languages. To spare the details, the basic process is: build the page (typically knowledge article) in English, extract the html, send that to our localization team, receive the translations back in html format, then &lt;EM&gt;create child pages for each translation and insert the provided html - &lt;/EM&gt;the last bit is extremely time consuming. The result is an English parent page with a drop down menu to select the other languages. When visiting the permalink for the page, the language selection defaults to the user's preferred language in SNOW.&lt;BR /&gt;&lt;BR /&gt;Does anyone have a more efficient process they are using for translations management? Ideally I'm looking for an import solution, or a way we could send the English page directly to localization and receive it back in platform, review for accuracy, and publish - eliminating the time consuming and error prone copy/paste. We're open to any ideas that would make this simpler, even if it means building the pages differently.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 03 Apr 2026 16:58:48 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/simplest-workflow-for-translated-pages/m-p/3519586#M6563</guid>
      <dc:creator>AnnaHeneghan</dc:creator>
      <dc:date>2026-04-03T16:58:48Z</dc:date>
    </item>
  </channel>
</rss>

