# Phase 16: Content Localization - Context

**Gathered:** 2026-02-02
**Status:** Ready for planning

<domain>
## Phase Boundary

Translate database content (trade categories) and system content (email templates, static pages) to Polish and German. This phase covers structured content that requires the Translate plugin's model integration and WinterCMS content file localization — NOT user-generated content.

</domain>

<decisions>
## Implementation Decisions

### Trade Categories
- Use Golem15.Translate plugin with translatable model trait (consistent with theme approach)
- Translate both name AND description fields for full localization
- Translate all levels equally — parent categories and subcategories all get full translations
- Use Translate plugin's import/export CLI commands for managing translations (research needed on exact commands)

### Email Templates
- Translate ALL system emails: quote notifications, job notifications, account emails
- Emails sent in recipient's preferred locale (user's saved language preference)
- Translate both subject lines AND body content
- Research needed: Check if templates already use |_ filter or have hardcoded English

### Static Pages
- Use Winter.Content plugin with language-specific file pattern (`file.lang.htm`)
- Translate all CMS static pages (legal, informational, all public content)
- FAQ content: Same questions translated to PL/DE (not locale-specific questions)
- Research needed: Audit which static pages currently exist in English

### Fallback Behavior
- Show English when content isn't translated (configured in Phase 11)
- No visual indicator for fallback — users see content normally
- User-generated content (job descriptions, reviews) stays in original language

### Claude's Discretion
- Legal page approach (direct translation vs placeholder) — recommend direct translation with note that legal review may be needed
- Exact CLI commands for Translate plugin import/export
- Order of translation work (categories vs emails vs pages)

</decisions>

<specifics>
## Specific Ideas

- Leverage existing `translate:export` and `translate:import` commands from Golem15.Translate plugin
- Content files use `content/file.lang.htm` pattern (e.g., `about.pl.htm`, `about.de.htm`)
- Email locale determined by `User->locale` preference field (added in Phase 15)

</specifics>

<deferred>
## Deferred Ideas

- AI/Google Translate integration for user-generated content (job descriptions, reviews) — future phase
- Locale-specific FAQ content (different questions per market) — not needed now

</deferred>

---

*Phase: 16-content-localization*
*Context gathered: 2026-02-02*