Drych

Translations contains the canonical searchable content list. It filters by the customer-facing translation states, shows matched English and Welsh state, translation scope and priority, current batch and next action, and keeps content refresh beside the inventory it updates. Page and batch histories use the same concise stages while preserving page-level exceptions and factual progress.

Home opens by default. Publishing English immediately is selected by default, with equal bilingual release available during setup. More than one eligible package can remain with Clear at once. Pages and Posts retain a compact English/Cymraeg pair view. The launch requires the administrator to review every selected waiting page before translation begins. Overview later keeps one complete update batch available for review: it applies the included-word balance to whole items in the saved priority order and, when needed, offers the current Drych billing authority one exact VAT-inclusive payment for the remaining translation words.

Search terms such as “Welsh bilingual site”, “Welsh website translation” and “Welshify your site” all describe the same guided Drych workflow. Supported multilingual providers are Polylang and WPML. Participating WordPress tables must use InnoDB for transactional safety.

External service

This plugin connects to the Drych service at https://drych.cymru. Drych Ltd (company number 17402546) owns and licenses the software. Clear Translations Ltd is the current Drych operator, provides the customer service and is responsible for professional translation and review. The service is required for Drych account matching, translation workflow, monitoring and controlled publication. An explicitly configured, visibly labelled sandbox installation may instead connect only to https://testing.drych.cymru for isolated test accounts, translations and Stripe test payments; production remains the default and arbitrary service addresses are not accepted.

No connection data is sent merely by installing or activating the plugin. When an administrator chooses to create an account or connect, the browser sends the site’s public URL and the exact Drych setup-step return URL to Drych. The focused account hand-off keeps the website and return route visible while the administrator signs in, registers, verifies their email, chooses the eligible organisation and matches or deliberately adds the website. After final approval, WordPress sends Drych the one-time pairing code, site URL, REST API URL, WordPress user ID, plugin version, safety-test result and a revocable site-scoped credential. Once connected, WordPress exchanges entitlement, managed-content, translation-batch, review, publication and recovery state with Drych. Drych calculates and locks exact selected wording and prices before a short-lived sign-in link opens Stripe checkout; card details are handled by Stripe and are not sent to WordPress. When managed English content is published or updated, the plugin also sends its numeric WordPress content ID, managed-catalogue revision, event type and event time so Drych can refresh that site’s authorised translation catalogue without waiting for the fallback refresh. On the explicitly allowlisted testing sandbox only, an administrator can explicitly reset unreturned test translation packages or the complete onboarding fixture. Once the bilingual workflow is enabled, authorised source wording, Welsh translation segments and the metadata required to stage, verify, publish, read back and safely roll back that wording are also exchanged with the service.

Service information and terms: https://drych.cymru/wordpress-service

Privacy notice: https://drych.cymru/privacy

Security and data

Every protected resource request requires the paired WordPress administrator and edit permission for its exact target. Every write also requires that target post type’s publish capability, a strong If-Match value and a unique Drych operation key. The plugin locks authoritative post and locale rows, verifies the exact result, stores an idempotent receipt in the same database transaction and fails closed on ambiguity.

Operation receipts contain hashes and the protected response required for safe replay. Pending receipts, which can represent an uncertain outcome, are retained until an administrator resolves them. Completed and rejected receipts are retained for 180 days and then removed in bounded daily batches. Deactivation pauses publication immediately and stops that maintenance schedule; it does not erase evidence.