The ffeibr.wales delivery record

The goal. Give Wales’s publicly owned fibre network a home of its own that takes Welsh as seriously as English, that its own team can publish to without a developer, and that stands up to the scrutiny a public body’s suppliers get. Success meant a live, fully bilingual site the client runs themselves, with nothing for IT or procurement to worry about afterwards.

Language. Every field in the CMS is an English and Welsh pair; there is no separate Welsh site to fall behind. Translation is human, by ffeibr’s own translator, and every gap was tracked to completion. Since 18 August 2026 a publish gate enforces completeness: a page with either language incomplete cannot stay published. Owain Taylor-Shaw, who runs ffeibr’s marketing, calls it a backstop: “Nothing goes out unless it’s bilingual, so both languages get equitable prominence.” Layouts were designed against Welsh, the longer language, so nothing truncates in either. The sitemap carries English and Welsh pairs with hreflang, product names stay in English on Welsh pages by ffeibr’s decision, and ffeibr.cymru lands on the Welsh pages.

Security and resilience. The site is generated ahead of time and served from Cloudflare’s edge: no server and no database, and no administrative login exists on the public site. The contact form runs as an edge function with a honeypot, a rate limit of three requests per ten seconds per address, and honest failure states. The launch moved the domain off Microsoft hosting with zero downtime around live Microsoft 365 email at DMARC reject, every record restaged and verified before the nameserver change. Dependencies audited at zero known vulnerabilities on 20 August 2026. Ffeibr’s IT asked about vulnerability assessment and penetration testing; the written answer, based on the static architecture, was accepted the same day.

Accessibility and performance. Lighthouse, mobile, 20 August 2026: 90 performance, 100 accessibility, 100 best practices, cumulative layout shift 0, first paint 1.1 seconds, about 1MB per page. Reduced-motion and no-JavaScript users get the full static artwork. Text never drops below 16px on phones. The accessibility statement sits with ffeibr as a public body under WCAG 2.2 AA.

Governance. Every change went through a branch preview ffeibr could open before it merged. No CMS schema changed without a written diff approved first. Every content push is a repeatable script committed to the repository, so the CMS can be rebuilt from source. Editors hold editor roles, not admin, and publishing is a production deploy, which the team knows.

Handover. A plain-English editor guide ships at /editor-guide/. Ffeibr’s team published its first press release, in both languages, the evening it arrived, without a developer involved. Continuing support runs as a retainer priced per deliverable.