Work in progress · Version 1.1, last updated 6 November 2026
Systems

Localisation

Country, content region and language are decided once at the edge and carried in the URL, so every localised page can be cached.

Locale model

Every page lives at /{country}/{language}/…. The address alone decides what a visitor sees, so the same address returns the same page to everyone. Country, region and language are independent: a visitor in Benin gets UK-region content in French; Korea and Taiwan get Australia-region content.

21
languages enabled in the CMS and served by the website
3
content regions
235
countries served
5
countries blocked, plus Crimea and Sevastopol
Content region Covers Countries
www_padi_com (US) United States and the Americas, including Canada 59
uk Europe, Middle East, Africa and Central Asia, including Russia and Belarus 136
australia Asia-Pacific, including Korea and Taiwan 40
Own site China, Hong Kong, Macau (padi.com.cn), Japan (padi.co.jp), home page only 4
Blocked Cuba, Iran, North Korea, Sudan, Syria; Crimea and Sevastopol 5

Each Drupal page is tagged to one or more regions; migrated pages are tagged to all three. Menus and settings are per region. The site adds hreflang alternates, right-to-left layout for Arabic, and fonts for Japanese, Korean, Chinese and Thai.

Request-time resolution

Figure 24. Locale and region resolution.
Figure 24. Locale and region resolution.

Only entry points redirect: the root, bare paths such as /blog, and legacy /{language}/ paths. Country paths, assets, APIs, non-GET requests, Travel, finder and account pages are never redirected. A crawler at the root is sent to /us/en. The Worker has three modes (act, observe, passthrough) and fails open. Legacy URL handling is checked after each deploy by a replay of real URLs.

Translation

What How it is translated Method
Drupal content: pages, articles, blog, blocks, terms, menu links, author bios, image text Drupal sends one file per item to one of PADI's Crowdin projects, chosen by source, billing type and method AI only, or AI plus human review, chosen per language
Website labels (about 700) Synced by developers with the Crowdin CLI and committed; the build fails on missing labels AI only
Finder text Pipeline sends English text to Crowdin and stores translations in FinderDB Machine only, by PADI decision
Image alt text and descriptions in Acquia DAM DAM's built-in AI translation on upload Machine
Video Tool under evaluation Undecided
Figure 25. Content translation round trip.
Figure 25. Content translation round trip.
Figure 26. Localisation entities.
Figure 26. Localisation entities.

Decisions needed before go-live

The open localisation decisions are Q-15, Q-17, Q-18 and Q-19 in Open questions: the account app and its 26 locales, the system of record for image text, old Russian URLs and blog-path blocking, and the two blocked-market lists.