Next.js 16 i18n Implementation

I’m rolling out a Next.js 16 App Router application and now need complete internationalization so the product speaks both English and Greek.

Scope
• Put in place a robust i18n infrastructure that fits the App Router paradigm—routing, server components, and static generation must keep working unchanged.
• Identify and extract every hard-coded string in the user-facing areas and the admin dashboard, replacing them with key-based look-ups.
• Build or wire up the translation system (e.g. next-intl, i18next, or another solid library) with automatic language detection and seamless locale switching.
• Translate all uncovered strings into Greek. I don’t have existing translations, so you will handle accurate wording and tone.
• Future-proof the setup so API responses could be localized later, even though that piece isn’t required right now.
• Deliver without breaking any current pages, routes, or build pipelines; all linting, tests, and TypeScript types must still pass.

I’m unsure whether any domain-specific terms need special handling, so flag anything that seems ambiguous during extraction.

Deliverables
1. Configured i18n framework inside the repo (PR or patch set).
2. Complete English and Greek JSON (or YAML) resource files.
3. Updated components/pages with string keys.
4. Brief read-me describing how to add new locales and run translation scripts.
5. Demo video or screenshots proving language toggle works across UI and dashboard.

If you’ve shipped multilingual Next.js apps before—and can translate to native-quality Greek—let’s talk.