### Summary I did a translatability audit of the Haven site template, and reviewed all node type to check whether their editorial text fields are correctly marked as translatable. Three of the four node types — `blog`, `person_profile`, and `project` — have fields holding human-readable editorial content that are configured with `translatable: false`. These fields are excluded from translation workflows. The `page` and `page` content types are fully correct and included for reference only. ### Audit: Node type field translatability #### `page` | Field | Type | Translatable | Should Be | Sample values from fixtures | |-------|------|:---:|:---:|---| | `title` | string | ✅ | ✅ | "Privacy policy", "Terms of service" | | `field_content` | text_long | ✅ | ✅ | `<h2>This content needs to be edited before publishing</h2>...` | | `field_description` | string | ✅ | ✅ | "Nothing here yet.", "The terms of service for site and product." | All fields correct IMHO. #### `blog` | Field | Type | Translatable | Should Be | Sample values from fixtures | |-------|------|:---:|:---:|---| | `title` | string | ✅ | ✅ | "What your local council can do about climate change right now" | | `field_blog__byline` | string | ❌ | ❌ | "Saoirse Brennan", "Priya Anand", "Tomás Reyes" | | `field_content` | text_long | ✅ | ✅ | `<p>When people think about climate policy...` | | `field_description` | string | ✅ | ✅ | "National policy matters, but local government has more power..." | All fields correct IMHO. #### `person_profile` | Field | Type | Translatable | Should Be | Sample values from fixtures | |-------|------|:---:|:---:|---| | `title` | string | ✅ | ❌ | "Dr. Alice Grossmann" | | `field_role` | string | ❌ | ✅ | "Chief Officer for Strategic Climate Leadership" | | `field_badge` | string | ❌ | ✅ | "Our specialists" | | `field_content` | text_long | ❌ | ✅ | `<h2>Meet our specialist</h2><p>Dr. Alice Grossmann is a prominent climate scientist...` | | `field_callout_heading` | string | ❌ | ✅ | "Areas of expertise" | | `field_callout_content` | text_long | ❌ | ✅ | `<ul><li>Climate modeling and prediction</li><li>Carbon capture technologies</li>...` | | `field_sidebar` | text_long | ❌ | ✅ | `<h2>Education</h2><p><strong>Ph.D. in Atmospheric Sciences</strong>...` | Title holds the name so should not be translatable. On the other hand all the other fields contain display content that is human readable text and should be translatable. #### `project` | Field | Type | Translatable | Should Be | Sample values from fixtures | |-------|------|:---:|:---:|---| | `title` | string | ✅ | ✅ | "Restoring the outer reef", "Solarizing the south side" | | `field_description` | string_long | ❌ | ✅ | "A marine conservation partnership spent three years transplanting heat-resistant coral..." | | `field_introduction` | text_long | ❌ | ✅ | `<p>Three years of coral transplantation, local diver training...</p>` | | `field_content` | text_long | ❌ | ✅ | `<p>The reef had been in decline for over a decade...` | ### Fix Person profile title should be marked not translatable. The rest of the identified fields should be marked translatable. ### LLM disclosure I used LLM assistance to help me with this audit but personally reviewed the (multiple ways incorrect) output, so this is a personal recommendation :smile: