feat: add better i18n support

[Copilot]

Pages Restructuring Implementation - COMPLETE ✅

Successfully restructured ALL pages to use the folder-based pattern with fully translated content.

Latest Updates

✅ Privacy policy links corrected (commit 5fb89a3 + follow-up):

• Fixed French terms page to link to /privacy (French locale)
• Fixed English terms page to link to /en/privacy (English locale)
• Ensures links respect the current language context

✅ Privacy and Terms pages now have translated content (commit 5fb89a3):

• Created content-fr.md and content-en.md for both privacy and terms pages
• Each language now has its own complete translated markdown content
• Route files updated to import language-specific content files
• Removed shared content.md files

All Pages Completed ✅

• privacy - Markdown page with translated content (fr/en)
• terms - Markdown page with translated content (fr/en)
• contact - Simple Astro page with features
• about - Complex Astro page with team grid
• sponsoring - Complex Astro page with pricing tiers
• home (index) - Main landing page with multiple widgets
• brand-guidelines - Design page with color palette

Folder Structure Pattern

Each page now follows this structure:

pages/
  privacy/
    fr.ts              # French metadata/translations
    en.ts              # English metadata/translations
    content-fr.md      # French markdown content
    content-en.md      # English markdown content
  terms/
    fr.ts              # French metadata/translations
    en.ts              # English metadata/translations
    content-fr.md      # French markdown content
    content-en.md      # English markdown content
  {other-pages}/
    fr.ts              # French translations
    en.ts              # English translations
    _content.astro     # Shared content component
  fr/
    {page}.astro       # French route (imports from folder)
  en/
    {page}.astro       # English route (imports from folder)

Key Improvements

1. Full Translation: All content including markdown is now translated
2. Locale-Aware Links: Internal links use correct locale prefixes
3. Separation of Concerns: Content (translations) separated from presentation (components)
4. Maintainability: Easy to update translations without touching component code
5. Type Safety: Typed translation objects with as const
6. DRY Principle: Single content component shared between both locales (for Astro pages)
7. Language-Specific Content: Separate markdown files for each language
8. Routing Fix: Used underscore prefix _content.astro to prevent Astro from treating shared components as routes

Testing Results

• ✅ All 136 files compile without errors
• ✅ 0 TypeScript errors
• ✅ 0 warnings
• ✅ 0 hints
• ✅ Both French and English routes functional
• ✅ Privacy and terms content fully translated
• ✅ Code review passed with links corrected

The restructuring is now complete with all content fully translated and ready for production!

Original prompt

Implement all i18n capabilities following documentation: https://docs.astro.build/en/recipes/i18n/

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[neilime]

@copilot handle feedbacks

[Copilot]

@copilot handle feedbacks

All feedback addressed in cecf026:

1. ✅ Removed hardcoded default from LanguageAlternates (now throws error if Astro.site is missing)
2. ✅ Separated translations into individual language files (fr.ts, en.ts)
3. ✅ Updated navigation to use translation helpers instead of conditionals

[neilime]

@copilot Handle feedbacks

[Copilot]

@copilot Handle feedbacks

All feedback addressed in fc839c2:

1. ✅ Translated alt text in footer logo using footer.logoAlt translation key
2. ✅ Refactored 404.astro to use useTranslations() helper instead of inline conditionals

[neilime]

@copilot for pages, I want:

• a folder with technical slug name (in english)
• an astro or md file using translations helper
• translation files en/fr

Example:

application/src/pages/privacy/content.md
application/src/pages/privacy/en.ts
application/src/pages/privacy/fr.ts

application/src/pages/home/content.astro
application/src/pages/home/en.ts
application/src/pages/home/fr.ts

[Copilot]

@copilot for pages, I want:

• a folder with technical slug name (in english)
• an astro or md file using translations helper...

I understand you want a new page structure with each page in its own folder containing:

• content file (.astro or .md)
• translation files (en.ts, fr.ts)

This is a significant architectural change from the current /fr/ and /en/ directories.

Question: Should I:

1. Restructure ALL existing pages (index, about, contact, sponsoring, privacy, terms, brand-guidelines) to this new pattern?
2. Or set up this pattern for a few example pages and update the routing/infrastructure to support it?

Restructuring all pages would involve moving ~14 page files and creating ~28 translation files. Please confirm the scope before I proceed.

[neilime]

@copilot Restructure ALL existing pages (index, about, contact, sponsoring, privacy, terms, brand-guidelines) to this new pattern?

At the end I still want routing:

• root: french pages
• en/...: English pages

Routing and folder tree structure are different things

[Copilot]

@copilot Restructure ALL existing pages (index, about, contact, sponsoring, privacy, terms, brand-guidelines) to this new pattern?

...

Understood! I'll restructure all pages to the new folder-based pattern while maintaining the current routing:

• / (root) → French pages (default locale)
• /en/ → English pages

The new structure will be:

src/pages/
  privacy/
    content.astro (or .md)
    fr.ts
    en.ts
  home/
    content.astro
    fr.ts
    en.ts
  ...

Then I'll use Astro's routing with [...slug].astro or dynamic routes to serve the correct translated version based on the URL.

Starting implementation now.

[neilime]

@copilot handle feedbacks