{"id":150293,"date":"2022-03-29T08:07:00","date_gmt":"2022-03-29T06:07:00","guid":{"rendered":"https:\/\/phrase.com\/blog\/posts\/localisation-continue-ce-que-cest-et-comment-elle-fonctionne\/"},"modified":"2026-08-04T21:12:48","modified_gmt":"2026-08-04T19:12:48","slug":"continuous-localization","status":"publish","type":"post","link":"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/","title":{"rendered":"Localisation continue : ce que c&rsquo;est et comment elle fonctionne"},"content":{"rendered":"\n<p>Continuous localization is the practice of translating and reviewing content in step with development, instead of as a separate phase after code ships. It plugs translation directly into agile and CI\/CD workflows, so new features reach every market and every language at the same time, without a separate hand-off to a translation team.<\/p>\n\n<p>Agile development is built around fast, continuous iteration. But most translation processes are still built around waterfall thinking: development finishes, then a batch of strings gets packaged up and sent out for translation. That mismatch is what continuous localization fixes.<\/p>\n\n<p>This guide covers what continuous localization actually means, why traditional translation workflows break under agile development, how continuous localization works in practice, and how to implement it.<\/p>\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Overview<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#why-doesnt-traditional-translation-work-with-agile-development\" >Why doesn&rsquo;t traditional translation work with agile development?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#how-did-agile-change-localization\" >How did agile change localization?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#how-continuous-localization-works\" >How continuous localization works<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#benefits-of-continuous-localization\" >Benefits of continuous localization<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#shorter-release-cycles\" >Shorter release cycles<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#better-quality\" >Better quality<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#simultaneous-global-launches\" >Simultaneous global launches<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#how-do-you-implement-continuous-localization\" >How do you implement continuous localization?<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#1-prepare-the-team-for-a-different-way-of-working\" >1. Prepare the team for a different way of working<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#2-map-your-current-workflow-before-changing-it\" >2. Map your current workflow before changing it.<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#3-automate-the-handoffs\" >3. Automate the handoffs<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#4-keep-a-stable-dedicated-translation-team\" >4. Keep a stable, dedicated translation team.<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#5-give-translators-context-not-just-strings\" >5. Give translators context, not just strings<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#6-treat-it-as-ongoing-not-a-one-time-migration\" >6. Treat it as ongoing, not a one-time migration<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#is-continuous-localization-worth-it-for-every-team\" >Is continuous localization worth it for every team?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#continuous-localization-faq\" >Continuous localization FAQ<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#what-is-continuous-localization\" >What is continuous localization?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#how-is-continuous-localization-different-from-traditional-localization\" >How is continuous localization different from traditional localization?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-19\" href=\"https:\/\/phrase.com\/fr\/blog\/posts\/continuous-localization\/#is-continuous-localization-the-same-as-continuous-integrationcontinuous-delivery-cicd\" >Is continuous localization the same as continuous integration\/continuous delivery (CI\/CD)?<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\" id=\"h-why-doesn-t-traditional-translation-work-with-agile-development\"><span class=\"ez-toc-section\" id=\"why-doesnt-traditional-translation-work-with-agile-development\"><\/span>Why doesn&rsquo;t traditional translation work with agile development?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p>In a waterfall model, each stage of a project has to finish before the next one starts. Translation is usually one of those stages, tacked on at the end.<\/p>\n\n<p>That creates two problems. First, any delay in translation delays the whole release, since nothing ships until every language is ready. Second, fixing an issue found late, whether a mistranslation, a string that doesn&rsquo;t fit the UI, or missing context, means reopening a \u00ab\u00a0finished\u00a0\u00bb stage, which is slow and disruptive by design.<\/p>\n\n<p>Some translation vendors describe themselves as agile without changing the underlying workflow: strings are still packaged into kits at the end of a sprint and sent to a separate team. The result is the same disconnect, just relabeled. Localization managers end up negotiating between developers and translators who are working on different pieces of the product at different times, which adds coordination overhead on every release.<\/p>\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"how-did-agile-change-localization\"><\/span>How did agile change localization?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p>Agile development works in small, iterative cycles rather than one long sequential build. Applied to localization, that means translation happens in the same cycle as development, not after it.<\/p>\n\n<p>Instead of one large translation drop at the end of a project, content moves to translators continuously, in the same small batches developers are shipping in. The localization team works embedded in the sprint rather than waiting for a handoff.<\/p>\n\n<p id=\"h-\">This shift gets teams faster turnaround and lets them catch and fix problems early. It does mean the localization process itself, tooling, workflows, and team structure, has to be rebuilt to support a continuous flow rather than periodic batches.<\/p>\n\n\n<div class=\"wp-block-group acf-blog-cta has-phrase-green-background-color has-background has-global-padding is-layout-constrained wp-block-group-is-layout-constrained\">\n\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-is-layout-7fc3d43a wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column is-vertically-aligned-top is-layout-flow wp-block-column-is-layout-flow\">\n<figure class=\"wp-block-image size-large is-style-not-rounded\"><img loading=\"lazy\" decoding=\"async\" width=\"791\" height=\"1024\" src=\"https:\/\/phrase.com\/wp-content\/uploads\/2023\/03\/continuous-localization-ebook-cover-791x1024.png\" alt=\"Continuous localization ebook cover | Phrase\" class=\"wp-image-42588\" srcset=\"https:\/\/phrase.com\/wp-content\/uploads\/2023\/03\/continuous-localization-ebook-cover-791x1024.png 791w, https:\/\/phrase.com\/wp-content\/uploads\/2023\/03\/continuous-localization-ebook-cover-232x300.png 232w, https:\/\/phrase.com\/wp-content\/uploads\/2023\/03\/continuous-localization-ebook-cover-768x994.png 768w, https:\/\/phrase.com\/wp-content\/uploads\/2023\/03\/continuous-localization-ebook-cover-1187x1536.png 1187w, https:\/\/phrase.com\/wp-content\/uploads\/2023\/03\/continuous-localization-ebook-cover-1583x2048.png 1583w, https:\/\/phrase.com\/wp-content\/uploads\/2023\/03\/continuous-localization-ebook-cover.png 1700w\" sizes=\"auto, (max-width: 791px) 100vw, 791px\" \/><\/figure>\n<\/div>\n\n\n\n<div class=\"wp-block-column is-vertically-aligned-center is-layout-flow wp-block-column-is-layout-flow\">\n\n\n<p class=\"subhead has-blue-color has-text-color has-link-color wp-elements-cc3c430b6c231527f3d119280d5fdc3c\" style=\"text-transform:uppercase\">Free download<\/p>\n\n\n\n<p class=\"has-larger-font-size\"><strong><span class=\"h6\" style=\"font-family: Inter, system-ui, -apple-system, 'Segoe UI', Roboto, 'Helvetica Neue', 'Noto Sans', 'Liberation Sans', Arial, sans-serif;\">How to build a localization workflow for continuous delivery<\/span><\/strong><\/p>\n\n\n\n<p>Explore how to implement continuous localization into agile product development to optimize content quality, shorten the release cycle time, and reduce costs.<\/p>\n\n\n\n<div class=\"wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button is-style-grey-filled\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/phrase.com\/resources\/continuous-localization\/\">Download ebook<\/a>\n<\/div><\/div>\n\n<\/div>\n<\/div>\n<\/div>\n\n\n<h2 class=\"wp-block-heading\" id=\"h-how-continuous-localization-works\"><span class=\"ez-toc-section\" id=\"how-continuous-localization-works\"><\/span>How continuous localization works<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p>Continuous delivery, the practice of keeping a product releasable at any time, is the model continuous localization borrows from. Developers don&rsquo;t want to wait days for QA, localization, and testing before shipping; they want to release as soon as a change is ready.<\/p>\n\n<p>For localization teams, that means managing an ongoing flow of content rather than large periodic drops. In practice, this usually runs through automated triggers: when a developer adds or changes a string in a source repository, it&rsquo;s picked up automatically and routed for translation, without anyone requesting a \u00ab\u00a0string freeze\u00a0\u00bb to buy translators time.<\/p>\n\n<p>This is where the tooling matters. A <a href=\"https:\/\/phrase.com\/platform\/tms\/\">translation management capability<\/a> that connects directly to your codebase, and an <a href=\"https:\/\/phrase.com\/platform\/orchestrator\/\">orchestration capability<\/a> that can trigger translation workflows automatically from a webhook or API event, is what makes \u00ab\u00a0continuous\u00a0\u00bb actually continuous rather than just \u00ab\u00a0frequent.\u00a0\u00bb <a href=\"https:\/\/phrase.com\/platform\/strings\/\">Phrase Strings<\/a> is built specifically for this: it syncs with your source repositories via API or CLI, so string changes flow into translation as they happen and translated strings flow back into your codebase the same way. See the <a href=\"https:\/\/developers.phrase.com\/en\/api\/overview\">API and developer documentation<\/a> for how the integration works.<\/p>\n\n<p>The goal for the development team is to notice as little friction as possible: they keep shipping, and localization keeps pace in the background, surfacing only the feedback that actually needs a developer&rsquo;s attention.<\/p>\n\n<h2 class=\"wp-block-heading\" id=\"h-benefits-of-continuous-localization\"><span class=\"ez-toc-section\" id=\"benefits-of-continuous-localization\"><\/span>Benefits of continuous localization<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p>Bringing localization into the development cycle, instead of after it, changes how translators and developers work together. Translators stop being passive recipients of localization kits and start working alongside the people building the product.<\/p>\n\n<h3 class=\"wp-block-heading\" id=\"h-shorter-release-cycles\"><span class=\"ez-toc-section\" id=\"shorter-release-cycles\"><\/span>Shorter release cycles<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n<p>Localization no longer sits on the critical path as a separate stage, so overall time to market comes down. <a href=\"https:\/\/phrase.com\/customers\/pega\/\">Pega<\/a> cut translation turnaround time by up to 75%, taking marketing content that used to lag English releases by up to four weeks down to as little as one week, without adding headcount. A <a href=\"https:\/\/phrase.com\/customers\/global-saas-company-mt-optimize\/\">global SaaS company<\/a> went further: after automating its web content translation, launch cycles compressed from weeks to same-day release across multiple languages, with external vendor costs dropping to zero.<\/p>\n\n<h3 class=\"wp-block-heading\" id=\"h-better-quality\"><span class=\"ez-toc-section\" id=\"better-quality\"><\/span>Better quality<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n<p>Translators working with real product context, rather than a disconnected string list, produce fewer errors and fewer follow-up queries. Issues surface while the relevant developer is still in the codebase, not weeks later.<\/p>\n\n<h3 class=\"wp-block-heading\" id=\"h-simultaneous-global-launches\"><span class=\"ez-toc-section\" id=\"simultaneous-global-launches\"><\/span>Simultaneous global launches<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n<p>Eliminating the lag between development and localization means a feature can ship in every market at once, instead of a staggered rollout over subsequent weeks or months.<\/p>\n\n<h2 class=\"wp-block-heading\" id=\"h-how-do-you-implement-continuous-localization\"><span class=\"ez-toc-section\" id=\"how-do-you-implement-continuous-localization\"><\/span>How do you implement continuous localization?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p>Moving to continuous localization is a process change, not just a tooling change. A few practices make the transition smoother:<\/p>\n\n<h3 class=\"wp-block-heading\" id=\"h-1-prepare-the-team-for-a-different-way-of-working\"><span class=\"ez-toc-section\" id=\"1-prepare-the-team-for-a-different-way-of-working\"><\/span>1. Prepare the team for a different way of working<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n<p>Prepare your team so that they welcome the change and not avoid it. The more you refuse the inevitability of change the harder it will bite when it comes.<\/p>\n\n<h3 class=\"wp-block-heading\" id=\"h-2-map-your-current-workflow-before-changing-it\"><span class=\"ez-toc-section\" id=\"2-map-your-current-workflow-before-changing-it\"><\/span>2. <strong>Map your current workflow before changing it.<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n<p>Look at localization as a flow of content and identify where it currently stalls. If the whole process feels too large to tackle at once, start with the single step that has the least friction, and expand from there.<\/p>\n\n<h3 class=\"wp-block-heading\" id=\"h-3-automate-the-handoffs\"><span class=\"ez-toc-section\" id=\"3-automate-the-handoffs\"><\/span>3. Automate the handoffs<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n<p>Manually batching strings, emailing files, and re-integrating translated content back into the codebase is where continuous localization breaks down in practice. Connecting your <a href=\"https:\/\/phrase.com\/platform\/tms\/\">TMS<\/a> directly to your issue tracker (for example, via API to a tool like Jira) keeps content and queries moving without manual intervention.<\/p>\n\n<h3 class=\"wp-block-heading\" id=\"h-4-keep-a-stable-dedicated-translation-team\"><span class=\"ez-toc-section\" id=\"4-keep-a-stable-dedicated-translation-team\"><\/span>4. Keep a stable, dedicated translation team.<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n<p>Translators who work with the same product over time build product knowledge and consistency that a rotating pool can&rsquo;t. Developers also learn to trust feedback from translators they recognize as familiar with the product, not just a name on a ticket.<\/p>\n\n<h3 class=\"wp-block-heading\" id=\"h-5-give-translators-context-not-just-strings\"><span class=\"ez-toc-section\" id=\"5-give-translators-context-not-just-strings\"><\/span>5. Give translators context, not just strings<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n<p>A screenshot, a short clip, or a linked ticket turns an ambiguous string into a fast, accurate translation. Missing context is one of the most common sources of translation errors and rework.<\/p>\n\n<h3 class=\"wp-block-heading\" id=\"h-6-treat-it-as-ongoing-not-a-one-time-migration\"><span class=\"ez-toc-section\" id=\"6-treat-it-as-ongoing-not-a-one-time-migration\"><\/span>6. Treat it as ongoing, not a one-time migration<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n<p>Expect to iterate on the workflow after the initial rollout. Agile methodology is the precondition for continuous localization working at all: if development itself isn&rsquo;t iterative, there&rsquo;s limited benefit to making localization so.<\/p>\n\n<h2 class=\"wp-block-heading\" id=\"h-is-continuous-localization-worth-it-for-every-team\"><span class=\"ez-toc-section\" id=\"is-continuous-localization-worth-it-for-every-team\"><\/span>Is continuous localization worth it for every team?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<p>If your product ships to a global audience on an agile cadence, yes: a translation workflow that still runs on waterfall assumptions will keep working against you, release after release. Continuous localization brings translation into the same rhythm as development, so it stops being a separate project and becomes part of how the product ships.<\/p>\n\n<div class=\"wp-block-group acf-blog-cta has-phrase-green-background-color has-background has-yellow-background-color has-global-padding is-layout-constrained wp-block-group-is-layout-constrained\">\n<p class=\"has-text-align-center has-larger-font-size\"><strong>Parlez \u00e0 un expert<\/strong><\/p>\n\n\n\n<p class=\"has-text-align-center has-text-align-center\">Vous souhaitez savoir comment nos solutions peuvent vous aider \u00e0 d\u00e9verrouiller l\u2019opportunit\u00e9 mondiale ? Nous serions heureux de vous faire d\u00e9couvrir la <a href=\"https:\/\/phrase.com\/fr\/platform\/\">Plateforme de localisation Phrase<\/a> et de r\u00e9pondre \u00e0 toutes vos questions.<\/p>\n\n\n\n<div class=\"wp-block-buttons is-content-justification-center is-layout-flex wp-container-core-buttons-is-layout-a89b3969 wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button is-style-default\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/phrase.com\/fr\/demo\/\">R\u00e9servez une d\u00e9mo<\/a><\/div>\n<\/div>\n<\/div>\n\n\n<h2 class=\"wp-block-heading\" id=\"h-continuous-localization-faq\"><span class=\"ez-toc-section\" id=\"continuous-localization-faq\"><\/span>Continuous localization FAQ<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n<div class=\"wp-block-wearerequired-accordion\">\n<div id=\"acc-what-is-continuous-localization\" tabindex=\"-1\" class=\"wp-block-wearerequired-accordion-section\">\n<h3 class=\"wp-block-wearerequired-accordion-heading\"><span class=\"ez-toc-section\" id=\"what-is-continuous-localization\"><\/span><span aria-hidden=\"true\" class=\"wp-block-wearerequired-accordion-heading__icon\"><\/span><span class=\"wp-block-wearerequired-accordion-heading__text\">What is continuous localization?<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<div class=\"wp-block-wearerequired-accordion-content is-layout-flow wp-block-wearerequired-accordion-content-is-layout-flow\">\n<p>Continuous localization is the practice of translating content in step with software development, using automated workflows that route new or changed strings to translators as soon as they&rsquo;re added to the codebase, rather than in a separate batch after development finishes.<\/p>\n<\/div>\n<\/div>\n\n\n\n<div id=\"acc-how-is-continuous-localization-different-from-traditional-localization\" tabindex=\"-1\" class=\"wp-block-wearerequired-accordion-section\">\n<h3 class=\"wp-block-wearerequired-accordion-heading\"><span class=\"ez-toc-section\" id=\"how-is-continuous-localization-different-from-traditional-localization\"><\/span><span aria-hidden=\"true\" class=\"wp-block-wearerequired-accordion-heading__icon\"><\/span><span class=\"wp-block-wearerequired-accordion-heading__text\">How is continuous localization different from traditional localization?<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<div class=\"wp-block-wearerequired-accordion-content is-layout-flow wp-block-wearerequired-accordion-content-is-layout-flow\">\n<p>Traditional localization treats translation as a distinct project phase that starts after development ends. Continuous localization runs translation in parallel with development, integrated into the same sprint cycle, so there&rsquo;s no separate handoff or \u00ab\u00a0string freeze.\u00a0\u00bb<\/p>\n<\/div>\n<\/div>\n\n\n\n<div id=\"acc-is-continuous-localization-the-same-as-continuous-integration-continuous-delivery-ci-cd\" tabindex=\"-1\" class=\"wp-block-wearerequired-accordion-section\">\n<h3 class=\"wp-block-wearerequired-accordion-heading\"><span class=\"ez-toc-section\" id=\"is-continuous-localization-the-same-as-continuous-integrationcontinuous-delivery-cicd\"><\/span><span aria-hidden=\"true\" class=\"wp-block-wearerequired-accordion-heading__icon\"><\/span><span class=\"wp-block-wearerequired-accordion-heading__text\">Is continuous localization the same as continuous integration\/continuous delivery (CI\/CD)?<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<div class=\"wp-block-wearerequired-accordion-content is-layout-flow wp-block-wearerequired-accordion-content-is-layout-flow\">\n<p>Not exactly. CI\/CD refers to automating code build, test, and release. Continuous localization applies the same always-ready principle to translation, and in practice, it&rsquo;s often implemented by connecting a translation management capability directly into a CI\/CD pipeline via API or webhook triggers.<\/p>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>La localisation continue consiste \u00e0 int\u00e9grer la traduction dans le d\u00e9veloppement logiciel agile afin de permettre une livraison ininterrompue de contenu multilingue. Voici comment cela fonctionne.<\/p>\n","protected":false},"author":61,"featured_media":1238,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"post-refresh-updated","format":"standard","meta":{"_acf_changed":false,"_stopmodifiedupdate":false,"_modified_date":"","_searchwp_excluded":"","episode_type":"","audio_file":"","podmotor_file_id":"","podmotor_episode_id":"","cover_image":"","cover_image_id":"","duration":"","filesize":"","filesize_raw":"","date_recorded":"","explicit":"","block":"","itunes_episode_number":"","itunes_title":"","itunes_season_number":"","itunes_episode_type":"","footnotes":""},"categories":[43],"class_list":["post-150293","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-localization-strategy-fr"],"acf":[],"_links":{"self":[{"href":"https:\/\/phrase.com\/fr\/wp-json\/wp\/v2\/posts\/150293","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/phrase.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/phrase.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/phrase.com\/fr\/wp-json\/wp\/v2\/users\/61"}],"replies":[{"embeddable":true,"href":"https:\/\/phrase.com\/fr\/wp-json\/wp\/v2\/comments?post=150293"}],"version-history":[{"count":3,"href":"https:\/\/phrase.com\/fr\/wp-json\/wp\/v2\/posts\/150293\/revisions"}],"predecessor-version":[{"id":150302,"href":"https:\/\/phrase.com\/fr\/wp-json\/wp\/v2\/posts\/150293\/revisions\/150302"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/phrase.com\/fr\/wp-json\/wp\/v2\/media\/1238"}],"wp:attachment":[{"href":"https:\/\/phrase.com\/fr\/wp-json\/wp\/v2\/media?parent=150293"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/phrase.com\/fr\/wp-json\/wp\/v2\/categories?post=150293"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}