Add Pacific telecom practice page (placeholder for post-launch case study)

[tomcounsell]

Plan: docs/plans/pacific_telecom_practice_page.md

Context: Yudame is currently delivering a project for a telecom operator in the Pacific region. That engagement cannot be publicly named or detailed until it launches, but the fact that Yudame operates in Pacific telecom is itself a credential that has zero surface on yuda.me today. ADB's Pacific Department covers 14 Pacific DMCs (Fiji, Samoa, Tonga, Vanuatu, Solomon Islands, PNG, etc.) and treats telecom/connectivity as a priority sector — an evaluator scanning yuda.me finds nothing connecting Yudame to either the region or the sector.

Problem

Current behavior: src/index.html contains no mention of telecom, the Pacific region, or the kind of work Yudame does for carriers. An evaluator from ADB's Pacific Department (or any Pacific-region buyer) sees zero signal that Yudame is active in their region or sector.

Desired outcome: A page or section that establishes Yudame's Pacific telecom practice area without naming the specific current client. The page should describe the kind of work Yudame does (mobile experience, digital financial services, network-adjacent products — whatever is accurate), the Pacific region focus, and serve as the structural home where a full named case study will land once the client launches publicly.

Definitions

Term	Definition	Reference
Pacific region	ADB's Pacific Department covers 14 Pacific DMCs — Fiji, Samoa, Tonga, Vanuatu, Solomon Islands, PNG, and others.	ADB Pacific Dept
DMC	Developing Member Country — ADB designation for countries eligible for ADB financing. Many Pacific nations are DMCs.	ADB countries
Practice area	A named area of repeatable expertise a firm offers — signals depth to institutional buyers (distinct from a single one-off project).	—

Prior Context

Related work in flight:

• ADB 2026 research brief (separate issue) — supplies vocabulary and thematic framing for how this practice area should speak.
• Case studies surface (separate issue) — the case studies structure may live on this page, on a shared surface, or both. Coordination needed in plan stage.
• Homepage reposition (separate issue) — will link to this practice page.

Solution Sketch

New page at a stable URL (e.g., /pacific-telecom or /practices/telecom). Structure along these lines:

• Practice statement — "We work with telecom operators in the Pacific on [specific product/service types]." Honest, specific to what Yudame actually does.
• Why this space — Connectivity gaps, digital financial services, digital public infrastructure in the Pacific — threaded into ADB vocabulary per the research brief.
• What we bring — Telecom-relevant capabilities: mobile UX, digital financial services integration, IP transfer, capacity transfer to local engineering teams.
• Case study — placeholder slot — structurally ready, explicitly marked "details pending client public launch." No partial identifying details.

Critical constraint — do not identify the current client. The specific current engagement must not be named in any public-facing surface (page copy, PR diff, commit messages, the issue's PR description). Internal references within the plan document are fine; anything shipped to main or linked from yuda.me is not. The placeholder must read naturally without any identifier — no logo, no industry-specific hints so narrow they'd identify the client, no country-level specificity that would single them out.

Open question for /do-plan: Dedicated page vs. homepage section? Likely a dedicated page given it will carry a full named case study later, but plan stage should confirm. Also: coordinate with the case studies surface issue — does the Pacific entry live on that surface, here, or in both places?

Recon Summary

Confirmed:

• No telecom / Pacific / regional content in current site or git history (searched commits and src/).
• Site is single-page; adding a new page is an editorial shift that should be acknowledged.

Revised:

• Scope explicitly does NOT include any named client detail. This is a practice-area placeholder page; the named case study is a future issue once the client launches.

Pre-requisites:

• Benefits from ADB 2026 research brief for vocabulary framing.
• Coordinate with case studies surface issue to avoid duplicate or conflicting case-study components.

Dropped:

• Full named case study for the current engagement — blocked until client launches; follow-up issue will handle that when unblocked.

Acceptance Criteria

• New page exists at a stable URL (e.g., /pacific-telecom or /practices/telecom)
• Linked from homepage above the footer
• Page describes the Pacific telecom practice area honestly (only claims Yudame can stand behind today)
• Includes a structurally-complete placeholder slot for the named case study, marked clearly as pending
• No public-facing surface (copy, PR, commit messages) names or uniquely identifies the current Pacific telecom client
• Visual aesthetic consistent with homepage
• Renders cleanly in npm run dev on desktop and mobile
• Build (npm run build) copies the new page into dist/ and GitHub Pages deploy workflow publishes it

Downstream

This issue feeds into /do-plan, which will produce a plan document at docs/plans/{slug}.md. Constraints:

• Client-identity confidentiality is a hard constraint — every artifact shipped to the public repo or the public site must pass a "can this identify the client?" check.
• Visual consistency with src/index.html.
• No external JS dependencies.

[tomcounsell]

Related issues in this ADB-visibility workstream:

• Research ADB 2026 digital priorities and produce positioning brief #5 — ADB 2026 research brief (vocabulary and thematic framing)
• Reposition homepage copy for ADB / DMC / Pacific audience #6 — Homepage reposition (will link to this page)
• Add development-outcomes case studies surface #7 — Case studies surface (coordinate on shared component pattern; Pacific placeholder case study coordination)