Translation Documentation

Overview

This directory contains comprehensive translation guides and status files for all 13 languages supported by the Hack23 AB website.

⚠️ Translation Gap Analysis (March 2026 — Measured)

Critical finding: Prior quality scores of 75–99% measured infrastructure completeness only (hreflang tags, Schema.org, navigation elements). The table below reflects actual measured body-content translation across all 96 pages per language.

Flag	Language	Code	Infrastructure %	Body Content %	Files w/ English Body	Priority
🇳🇱🌷	Dutch	nl	100%	15%	82 / 96	⚡ CRITICAL
🇩🇰⚓	Danish	da	100%	27%	70 / 96	⚡ CRITICAL
🇫🇮🦌	Finnish	fi	100%	29%	68 / 96	🔴 HIGH
🇫🇷🥐	French	fr	100%	30%	67 / 96	🔴 HIGH
🇸🇪👑	Swedish	sv	100%	37%	60 / 96	🔴 HIGH
🇩🇪🦅	German	de	100%	42%	56 / 96	🔴 HIGH
🇰🇷🏯	Korean	ko	100%	43%	55 / 96	🔴 HIGH
🇪🇸🎭	Spanish	es	100%	45%	53 / 96	🟠 MEDIUM
🇳🇴⛷️	Norwegian	no	100%	46%	52 / 96	🟠 MEDIUM
🇮🇱✡️	Hebrew	he	100%	48%	50 / 96	🟠 MEDIUM
🇸🇦🌙	Arabic	ar	100%	59%	39 / 96	🟡 LOWER
🇨🇳🐉	Chinese	zh	100%	66%	33 / 96	🟡 LOWER
🇯🇵🗾	Japanese	ja	100%	68%	31 / 96	🟡 LOWER

Across all languages: Infrastructure completion = 100% (1,248 / 1,248 files). Body content translated = ~32% (~395 / 1,248 files).

📏 Measurement Methodology

What "Infrastructure %" Measures

A file counts as infrastructure-complete when all of the following exist:

✅ HTML file is present with valid HTML5 semantic structure
✅ hreflang tags present (28 per file, covering all 14 language variants)
✅ Schema.org structured data (Organization, WebSite, BreadcrumbList, etc.)
✅ Localized metadata — <title>, <meta name="description">, <meta name="keywords">
✅ Localized navigation labels, page headings, and footer elements
✅ RTL dir="rtl" attribute for Arabic and Hebrew

What "Body Content %" Measures

A file is counted as body-translated when its main article / page body paragraphs are in the target language — i.e., the human-readable prose that visitors actually read.

Detection method: English-sentence patterns are searched in <p> elements using the heuristic:

<p>[A-Z][a-z]+ [a-z]+ [a-z]+

A file whose <p> blocks still match this pattern is classified as body = English and increments the "Files w/ English Body" counter. A file whose primary paragraphs do not match (because they are in the target script or a translated sentence structure) is counted as body translated.

Summary: Infrastructure metrics show SEO plumbing completeness. Body content metrics show what visitors actually read.

🎉 Latest Update: Translation Infrastructure Complete (January 2026)

📊 STATUS UPDATE (January 13, 2026): Infrastructure Complete, Content Translation In Progress

Important Clarification: Previous reports overstated translation completion. This update reflects the actual state.

Current State: Infrastructure vs. Content Translation

Infrastructure Complete: 1,248/1,248 files ✅
- HTML5 semantic structure
- Complete hreflang tags (28 per file)
- Schema.org structured data
- Localized metadata (titles, descriptions, keywords)
- RTL support for Arabic and Hebrew
Content Translation Status: MIXED ⚠️
- High Quality (Swedish, German, English): Body content fully translated
- Infrastructure-Only (243 blog files): Metadata translated, body content pending
  - Arabic: 27 blog files
  - Danish: 27 blog files
  - Spanish: 27 blog files
  - Finnish: 27 blog files
  - Hebrew: 27 blog files
  - Japanese: 27 blog files
  - Korean: 27 blog files
  - Norwegian: 27 blog files
  - Chinese: 27 blog files

Revised Summary Statistics (March 2026 — Measured Values):

Total Files Created: 1,248 / 1,248 (100% infrastructure coverage) ✅
Body Content Translated: ~395 / 1,248 files (~32% of all translation files)
Infrastructure-Only Files: ~853 / 1,248 files (~68% — HTML/hreflang/Schema.org complete, body still English)
Languages with Full Content Translation: 0 languages (none exceed 80% body content)
Languages Needing Body Content Translation: All 13 languages
Infrastructure: Complete hreflang tags, Schema.org metadata, and RTL support across all files ✅

⚠️ Translation Quality Clarification (January 13, 2026)

IMPORTANT: Previous quality scores (85-98%) measured infrastructure completeness, not body content translation.

Known Content Translation Issues:

243 Blog Files (Infrastructure-Only): Created with complete HTML structure, hreflang, and metadata, but body content remains in English or incorrect language
- Affected languages: Arabic (27), Danish (27), Spanish (27), Finnish (27), Hebrew (27), Japanese (27), Korean (27), Norwegian (27), Chinese (27)
- Status: Awaiting professional translation of body content
- What exists: Translated titles, descriptions, keywords, navigation
- What's missing: Translated article body, blog post content
Nordic Language Mixing: Some Danish, Finnish, and Norwegian files contain Swedish text instead of target language
- Root cause: Swedish files used as templates without full language replacement
- Impact: ~54-81 files affected
- Example: Danish files showing "Mönstret Avslöjar Sig" (Swedish) instead of Danish equivalent
Quality Score Correction: Previous claims of "zero English content" were incorrect
- Previous claim: 85-98% quality across most languages
- Reality: Infrastructure 100%, body content variable (30-100% depending on language and file type)
- Corrected approach: Separate infrastructure and content metrics

Revised Language Status (March 2026 — Actual Measured Values):

🇳🇱 Dutch: Infrastructure 100%, Body Content 15% ⚠️ CRITICAL
🇩🇰 Danish: Infrastructure 100%, Body Content 27% ⚠️ CRITICAL
🇫🇮 Finnish: Infrastructure 100%, Body Content 29% 🚧 HIGH
🇫🇷 French: Infrastructure 100%, Body Content 30% 🚧 HIGH
🇸🇪 Swedish: Infrastructure 100%, Body Content 37% 🚧 HIGH
🇩🇪 German: Infrastructure 100%, Body Content 42% 🚧 HIGH
🇰🇷 Korean: Infrastructure 100%, Body Content 43% 🚧 HIGH
🇪🇸 Spanish: Infrastructure 100%, Body Content 45% 🚧 MEDIUM
🇳🇴 Norwegian: Infrastructure 100%, Body Content 46% 🚧 MEDIUM
🇮🇱 Hebrew: Infrastructure 100%, Body Content 48% 🚧 MEDIUM
🇸🇦 Arabic: Infrastructure 100%, Body Content 59% 🚧 LOWER
🇨🇳 Chinese: Infrastructure 100%, Body Content 66% 🚧 LOWER
🇯🇵 Japanese: Infrastructure 100%, Body Content 68% 🚧 LOWER

Action Plan for Full Translation:

Option A (Current): Accept infrastructure-complete state, document accurately Option B (Future): Professional translation services for 243+ blog files Option C (Future): AI-assisted translation with native speaker review

📋 Historical: Previous Infrastructure Updates (Early January 2026)

Note: The updates below refer to infrastructure completion, not full content translation.

File Infrastructure Completion (January 2-4, 2026):

🇸🇦 Arabic: 93/96 → 96/96 (+3 files infrastructure)
🇮🇱 Hebrew: 94/96 → 96/96 (+2 files infrastructure)
🇩🇪 German: 95/96 → 96/96 (+1 file infrastructure)
🇫🇷 French: 86/96 → 96/96 (+10 files infrastructure)
🇸🇪 Swedish: 95/96 → 96/96 (+1 file infrastructure)

🎉 Previous Update: PR #912 Complete - Massive Translation Expansion (December 30, 2025)

PR #912 delivered 278 new translation files across 10 languages, completing ISMS policy translations:

European ISMS Policies - 113 Files Completed ✅

🇩🇪 German: 77 → 95 files (+18 files, 80.21% → 98.96%) - 18 new files added
🇪🇸 Spanish: 60 → 96 files (+36 files, 62.5% → 100%) - 36 new files added (100% COMPLETE!)
🇫🇷 French: 60 → 86 files (+26 files, 62.5% → 89.58%) - 26 new files added
🇳🇱 Dutch: 63 → 96 files (+33 files, 65.62% → 100%) - 33 new files added (100% COMPLETE!)

RTL & Asian ISMS Policies - 87 Files Completed ✅

🇸🇦 Arabic (RTL): 62 → 93 files (+31 files, 64.58% → 96.88%) - 31 new files added
🇯🇵 Japanese: 68 → 96 files (+28 files, 70.83% → 100%) - 28 new files added (100% COMPLETE!)
🇨🇳 Chinese: 68 → 96 files (+28 files, 70.83% → 100%) - 28 new files added (100% COMPLETE!)

Nordic Languages - 78 Files Completed ✅

🇩🇰 Danish: 70 → 96 files (+26 files, 72.92% → 100%, Quality: 90.0% → 92.7%) - All ISMS complete!
🇫🇮 Finnish: 70 → 96 files (+26 files, 72.92% → 100%, Quality: 90.9% → 92.7%) - All ISMS complete!
🇳🇴 Norwegian: 70 → 96 files (+26 files, 72.92% → 100%, Quality: 90.3% → 95.0%) - All ISMS complete!

Summary Statistics:

Total New Files: 278 translation files across 10 languages
ISMS Policies: 48 core ISMS policy files with expanded translations across 10 languages in this PR
Languages at 100%: 8 languages now have complete file coverage (Dutch, Spanish, Japanese, Chinese, Korean, Danish, Finnish, Norwegian). Swedish is at 98.96% (95/96 files).
Overall Progress: 76.4% → 98.6% (+22.2 percentage points)
Quality Impact: Multiple languages improved quality scores with professional translations
Infrastructure: Complete hreflang tags, Schema.org metadata, and RTL support (where applicable) implemented across production files

🎉 Previous Update: Major Translation Milestones (December 24, 2025)

Comprehensive Q4 2025 translation achievements across multiple languages:

Swedish Excellence - 98.3% Quality 🎉

Achievement: Phase 1-5 Complete - 19 ISMS policy files added
Files: 95/96 (98.96% completion)
Quality: 98.3% fully/mostly translated (TARGET EXCEEDED - goal was 90%)
Breakdown: 87 fully translated, 8 mostly translated
Guide Version: v3.1 with comprehensive vocabulary tables

Korean Complete - 100% Infrastructure 🎉

Achievement: All 96 Korean files exist with professional translations
Homepage Quality: 75%+ → ~100% (December 24, 2025)
Terminology: 150+ standardization fixes applied
K-ISMS/PIPA: Regulatory context enhanced by 248-423%
Schema.org: 86.7% coverage (59/68 applicable files)
Guide Version: v6.0 with standardized terminology

Hebrew Quality Leap - 80%+ 🎉

Achievement: Phase 4 Terminology Standardization Complete
Files: 94/96 (97.9% completion)
Quality: 42.4% → 80%+ (89% improvement)
Terminology Consistency: 90%+ across all pages
Major Updates: 675 terminology replacements applied
Guide Version: v4.0 Finalized Terminology Edition

Nordic Homepage Translations 📊

Danish: 70.1% → ~80% (+10%) - Meta tags, hero, value propositions
Finnish: 71.6% → ~80% (+8%) - Main headings, core paragraphs
Norwegian: 68.1% → ~78% (+10%) - Critical sections, primary content
Methodology: Web-search assisted professional translation with guide v3.1 terminology
Cultural Adaptation: "Göteborg" localization maintained across all Nordic languages

European Blog Infrastructure ✅

Files Created: 12 new blog files (German, Spanish, French, Dutch)
Posts: blog-public-isms-benefits, blog-automated-convergence, blog-information-hoarding
Infrastructure: Complete HTML5, hreflang (28 tags), Schema.org structured data
Metadata: Fully translated for all 4 languages
Content Status: Infrastructure complete, professional body translation pending

Total Impact (December 24, 2025):

913 translation files across 13 languages (73.2% of 1,248 possible)
3 languages at 95%+ completion: Swedish (98.96%), Hebrew (97.92%), Korean (100%)
Quality scores improved: All languages now show 82.7%-93.7% quality with consistent methodology
Blog files: 338 total (26 English + 312 translations)

🆕 Enhanced Vocabulary Edition (v3.1 - December 2025)

All 13 translation guides have been enhanced with comprehensive vocabulary extracted from actual translated pages:

✅ Real-world vocabulary: Terms extracted from 784 translated HTML files across all languages
✅ Categorized tables: Navigation, Security, Technical, Business, and Products terminology
✅ Consistency verification: Cross-referenced with English base files
✅ 60-90 verified term pairs per language from actual usage
✅ Translation notes: Best practices and consistency guidelines included

This enhancement ensures translation guides reflect actual usage patterns and provide translators with proven, validated terminology from existing high-quality translations.

🎉 Translation Milestones (Q4 2025)

Swedish - Phase 1-5 Complete ✅

Swedish ISMS Policy Expansion (19 New Files):

Phase 1 (HIGH Priority - 7 files): Network security, secure development, vulnerability management, cryptography, data protection, privacy, cloud security
Phase 2 (MEDIUM Priority - 6 files): Classification, data classification, monitoring/logging, backup/recovery, disaster recovery, business continuity
Phase 3 (LOWER Priority - 6 files): Security strategy, security metrics, stakeholders, supplier reality, LLM security, CRA conformity
Quality Achievement: 98.3% fully/mostly translated (87 fully + 8 mostly out of 95 files)
File Coverage: 98.96% complete (95/96 files exist)
Status: 🎉 TARGET EXCEEDED - Quality goal was 90%, achieved 98.3%!

Korean - 100% Infrastructure Complete ✅

Korean Translation Infrastructure Achievement:

File Coverage: 100% (96/96 files - all English pages have Korean translations)
Quality Score: ~100% after homepage translation completion (December 24, 2025)
Terminology Standardization: 150+ surgical fixes applied for consistency
- 사이버보안, 정보보안 (no spaces - technical compounds)
- 규정 준수 (with space - action phrases)
- 위험 (proper Korean, not Konglish 리스크)
K-ISMS Context: 33 → 115+ mentions (+248%)
PIPA Context: 22 → 115+ mentions (+423%)
Schema.org Coverage: 86.7% (59/68 applicable files)

Hebrew - Phase 4 Terminology Standardization Complete ✅

Hebrew Terminology Excellence Achievement:

File Coverage: 97.9% (94/96 files exist)
Quality Score: 80%+ (Phase 4 Complete)
Terminology Consistency: 90%+ across all pages
Major Improvements:
- תגובה לאירועים (Incident Response): +66% usage
- אבטחת סייבר (Cybersecurity): +83% Hebrew usage (253 → 471)
- הערכת סיכונים (Risk Assessment): +95% Hebrew usage (38 → 74)
- ציות (Compliance): +253% standardization (356 → 1,360)
- CIA Triad: 66 replacements for complete consistency
Deliverables: Hebrew-Translation-Guide.md v4.0, comprehensive completion report

Nordic Languages - Homepage Translation Updates (Dec 24, 2025) ✅

Danish, Finnish, Norwegian Homepage Improvements:

Danish (index_da.html): Quality improvement to ~80% (from 70.1% baseline)
- Core English placeholders in visible sections replaced
- Meta tags, hero sections, value propositions translated
- Professional terminology: "Radikal gennemsigtighed", "Sikkerhed fremskynder innovation"
- Note: Overall file quality remains 70.1% (homepage represents subset of total files)
Finnish (index_fi.html): Quality improvement to ~80% (from 71.6% baseline)
- Main card headings and core paragraphs translated
- Professional terminology: "Radikaali läpinäkyvyys", "Turvallisuus vauhdittaa innovaatioita"
- Note: Overall file quality remains 71.6% (homepage represents subset of total files)
Norwegian (index_no.html): Quality improvement to ~78% (from 68.1% baseline)
- Critical homepage headings and primary paragraphs translated
- Professional terminology: "Radikal åpenhet", "Sikkerhet akselererer innovasjon"
- Note: Overall file quality remains 68.1% (homepage represents subset of total files)

European Blog Infrastructure (3 High-Priority Posts) ✅

German, Spanish, French, Dutch - Blog Translation Foundation:

Posts Completed: blog-public-isms-benefits, blog-automated-convergence, blog-information-hoarding
Infrastructure: Complete HTML5 semantic structure, 28 hreflang tags per file, Schema.org structured data
Metadata: Fully translated titles, descriptions, navigation, breadcrumbs for all 4 languages
Total: 12 new blog files created (4 languages × 3 posts)
Status: Infrastructure Complete ✅ | Content Translation Pending ⚠️

✅ Quality Assurance Status (December 2025)

QA Phase 1 Complete: Comprehensive hreflang and SEO validation across all 925 HTML pages

Validation Date: 2025-12-15
Pages Validated: 925 (100% coverage)
Compliance Rate: 92.4%
Full Report: TRANSLATION_QA_REPORT.md

Key Metrics

✅ 100% RTL Compliance - All 124 Arabic/Hebrew files properly implement dir="rtl"
✅ 99.2% Canonical Coverage - 918/925 files have canonical tags
✅ 97.7% x-default Coverage - 904/925 files have proper hreflang fallback
✅ 95.2% Lang Attribute Accuracy - 881/925 files have correct HTML lang
✅ Complete Sitemap - All 925 pages in sitemap.xml with 23,056 hreflang tags

Structure

Each language has two dedicated files:

[Language]-Translation-Guide.md - Translation instructions, terminology, and best practices
[Language]-Translation-Status.md - Current translation progress and completion status

Supported Languages (13)

RTL Languages ←

Flag	Language	Code	Files	Infra %	Body %	Guide Version	Status
🇸🇦🌙	Arabic	ar	96/96	100%	59% 🚧	v3.1 📖	Status 📊
🇮🇱✡️	Hebrew	he	96/96	100%	48% 🚧	v4.0 📖	Status 📊 \| Analysis 📊

Asian Languages 🌏

Flag	Language	Code	Files	Infra %	Body %	Guide Version	Status
🇯🇵🗾	Japanese	ja	96/96	100%	68% 🚧	v3.1 📖	Status 📊
🇨🇳🐉	Chinese	zh	96/96	100%	66% 🚧	v3.1 📖	Status 📊
🇰🇷🏯	Korean	ko	96/96	100%	43% 🚧	v6.0 📖	Status 📊

Nordic Languages ❄️

Flag	Language	Code	Files	Infra %	Body %	Guide Version	Status
🇩🇰⚓	Danish	da	96/96	100%	24% ⚠️	v3.1 📖	Status 📊
🇫🇮🦌	Finnish	fi	96/96	100%	25% 🚧	v3.1 📖	Status 📊
🇳🇴⛷️	Norwegian	no	96/96	100%	46% 🚧	v3.1 📖	Status 📊

European Languages 🇪🇺

Flag	Language	Code	Files	Infra %	Body %	Guide Version	Status
🇳🇱🌷	Dutch	nl	96/96	100%	12% ⚠️	v3.1 📖	Status 📊
🇩🇪🦅	German	de	96/96	100%	42% 🚧	v3.1 📖	Status 📊
🇫🇷🥐	French	fr	96/96	100%	28% 🚧	v3.1 📖	Status 📊
🇪🇸🎭	Spanish	es	96/96	100%	45% 🚧	v3.1 📖	Status 📊

Base Language 👑

Flag	Language	Code	Files	Infra %	Body %	Guide Version	Status
🇸🇪👑	Swedish	sv	96/96	100%	37% 🚧	v3.1 📖	Status 📊

Total: 1,248 translation files out of 1,248 possible (96 base × 13 languages) = 100% infrastructure complete ✅ | ~32% body content translated ⚠️

📊 Visual Translation Overview

%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#4CAF50','primaryTextColor':'#fff','primaryBorderColor':'#2E7D32','lineColor':'#666','secondaryColor':'#2196F3','tertiaryColor':'#FFC107','fontSize':'16px'}}}%%
graph TB
    subgraph "🌍 Translation Status Overview — March 2026 (Two-Tier Metrics)"
        A["📚 96 Base English Files"] --> B{"🌐 13 Languages"}
        B --> C["❄️ Nordic Group<br/>🇩🇰🇫🇮🇳🇴🇸🇪"]
        B --> D["🇪🇺 European Group<br/>🇩🇪🇳🇱🇫🇷🇪🇸"]
        B --> E["🌏 Asian Group<br/>🇯🇵🇨🇳🇰🇷"]
        B --> F["← RTL Group<br/>🇸🇦🇮🇱"]

        C --> C1["🇸🇪👑 Swedish\n100% Infra | 37% Body\n🚧 HIGH"]
        C --> C2["🇩🇰⚓ Danish\n100% Infra | 24% Body\n⚠️ CRITICAL"]
        C --> C3["🇫🇮🦌 Finnish\n100% Infra | 25% Body\n🚧 HIGH"]
        C --> C4["🇳🇴⛷️ Norwegian\n100% Infra | 46% Body\n🚧 MEDIUM"]

        D --> D1["🇩🇪🦅 German\n100% Infra | 42% Body\n🚧 HIGH"]
        D --> D2["🇳🇱🌷 Dutch\n100% Infra | 12% Body\n⚠️ CRITICAL"]
        D --> D3["🇫🇷🥐 French\n100% Infra | 28% Body\n🚧 HIGH"]
        D --> D4["🇪🇸🎭 Spanish\n100% Infra | 45% Body\n🚧 MEDIUM"]

        E --> E1["🇨🇳🐉 Chinese\n100% Infra | 66% Body\n🚧 LOWER"]
        E --> E2["🇯🇵🗾 Japanese\n100% Infra | 68% Body\n🚧 LOWER"]
        E --> E3["🇰🇷🏯 Korean\n100% Infra | 43% Body\n🚧 HIGH"]

        F --> F1["🇮🇱✡️ Hebrew\n100% Infra | 48% Body\n🚧 MEDIUM"]
        F --> F2["🇸🇦🌙 Arabic\n100% Infra | 59% Body\n🚧 LOWER"]

        style A fill:#4CAF50,stroke:#2E7D32,color:#fff,stroke-width:3px
        style B fill:#2196F3,stroke:#1565C0,color:#fff,stroke-width:3px
        style C fill:#00BCD4,stroke:#00838F,color:#fff,stroke-width:2px
        style D fill:#FF9800,stroke:#E65100,color:#fff,stroke-width:2px
        style E fill:#E91E63,stroke:#AD1457,color:#fff,stroke-width:2px
        style F fill:#9C27B0,stroke:#6A1B9A,color:#fff,stroke-width:2px
        style C1 fill:#F57C00,stroke:#FF9800,color:#fff,stroke-width:2px
        style C2 fill:#D32F2F,stroke:#B71C1C,color:#fff,stroke-width:3px
        style C3 fill:#F57C00,stroke:#FF9800,color:#fff,stroke-width:2px
        style C4 fill:#F57C00,stroke:#FF9800,color:#fff,stroke-width:2px
        style D1 fill:#F57C00,stroke:#FF9800,color:#fff,stroke-width:2px
        style D2 fill:#D32F2F,stroke:#B71C1C,color:#fff,stroke-width:3px
        style D3 fill:#F57C00,stroke:#FF9800,color:#fff,stroke-width:2px
        style D4 fill:#F57C00,stroke:#FF9800,color:#fff,stroke-width:2px
        style E1 fill:#FBC02D,stroke:#F9A825,color:#000,stroke-width:2px
        style E2 fill:#FBC02D,stroke:#F9A825,color:#000,stroke-width:2px
        style E3 fill:#F57C00,stroke:#FF9800,color:#fff,stroke-width:2px
        style F1 fill:#F57C00,stroke:#FF9800,color:#fff,stroke-width:2px
        style F2 fill:#FBC02D,stroke:#F9A825,color:#000,stroke-width:2px
    end

%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#4CAF50','fontSize':'16px'}}}%%
graph TB
    subgraph "📊 Body Content Translation % by Language — March 2026 (Worst → Best)"
        NL["🇳🇱🌷 Dutch\n100% Infra | 12% Body\n⚠️ CRITICAL"]
        DA["🇩🇰⚓ Danish\n100% Infra | 24% Body\n⚠️ CRITICAL"]
        FI["🇫🇮🦌 Finnish\n100% Infra | 25% Body\n🚧 HIGH"]
        FR["🇫🇷🥐 French\n100% Infra | 28% Body\n🚧 HIGH"]
        SV["🇸🇪👑 Swedish\n100% Infra | 37% Body\n🚧 HIGH"]
        DE["🇩🇪🦅 German\n100% Infra | 42% Body\n🚧 HIGH"]
        KO["🇰🇷🏯 Korean\n100% Infra | 43% Body\n🚧 HIGH"]
        ES["🇪🇸🎭 Spanish\n100% Infra | 45% Body\n🚧 MEDIUM"]
        NO["🇳🇴⛷️ Norwegian\n100% Infra | 46% Body\n🚧 MEDIUM"]
        HE["🇮🇱✡️ Hebrew\n100% Infra | 48% Body\n🚧 MEDIUM"]
        AR["🇸🇦🌙 Arabic\n100% Infra | 59% Body\n🚧 LOWER"]
        ZH["🇨🇳🐉 Chinese\n100% Infra | 66% Body\n🚧 LOWER"]
        JA["🇯🇵🗾 Japanese\n100% Infra | 68% Body\n🚧 LOWER"]

        style NL fill:#D32F2F,stroke:#B71C1C,color:#fff,stroke-width:3px
        style DA fill:#D32F2F,stroke:#B71C1C,color:#fff,stroke-width:3px
        style FI fill:#E64A19,stroke:#BF360C,color:#fff,stroke-width:2px
        style FR fill:#E64A19,stroke:#BF360C,color:#fff,stroke-width:2px
        style SV fill:#F57C00,stroke:#E65100,color:#fff,stroke-width:2px
        style DE fill:#F57C00,stroke:#E65100,color:#fff,stroke-width:2px
        style KO fill:#F57C00,stroke:#E65100,color:#fff,stroke-width:2px
        style ES fill:#F9A825,stroke:#F57F17,color:#000,stroke-width:2px
        style NO fill:#F9A825,stroke:#F57F17,color:#000,stroke-width:2px
        style HE fill:#F9A825,stroke:#F57F17,color:#000,stroke-width:2px
        style AR fill:#FBC02D,stroke:#F9A825,color:#000,stroke-width:2px
        style ZH fill:#FBC02D,stroke:#F9A825,color:#000,stroke-width:2px
        style JA fill:#FBC02D,stroke:#F9A825,color:#000,stroke-width:2px
    end

Base English Files: 96
Total Translation Files: 1,248 out of 1,248 possible (100% infrastructure complete ✅ | ~32% body content translated ⚠️)
Last Updated: March 2026

📋 Priority Recommendations (Based on Measured Body-Content Gaps)

Priorities are ordered by actual body-content translation percentage (lowest first), as measured in March 2026.

⚡ CRITICAL — Translate First (Body Content < 25%)

1. Dutch (nl) — 12% body translated (84 / 96 files still English) 🔴

Most infrastructure-only language; only 12 files have translated body content
Immediate action: Focus on homepage, services, and product pages first
Estimated scope: ~72,000 words across 84 files
Recommended tooling: DeepL Pro API with v3.1 glossary

2. Danish (da) — 24% body translated (73 / 96 files still English) 🔴

Previously reported as "95% quality" — that score was infrastructure-only
Note: Check for Swedish-text contamination in existing translated files
Immediate action: ISMS policy pages + homepage content
Recommended tooling: DeepL Pro API with Nordic glossary

🔴 HIGH Priority (Body Content 25–50%)

3. Finnish (fi) — 25% body translated (72 / 96 files still English)

Note: Cross-check for Swedish-text contamination in template-derived files
Focus: ISMS discordian pages first (highest search value)

4. French (fr) — 28% body translated (69 / 96 files still English)

Previously reported as "98% quality" — that was infrastructure only
Regulatory adaptation needed: CNIL, RGPD references
Focus: services, blog, ISMS policy pages

5. Swedish (sv) — 37% body translated (60 / 96 files still English)

Primary-market language; higher priority despite not being worst
Focus: remaining blog posts and newer product pages

6. German (de) — 42% body translated (56 / 96 files still English)

Previously reported as "98.9% quality" — that was infrastructure only
Regulatory adaptation: BSI, DSGVO references
Focus: blog content + newer product pages

7. Korean (ko) — 43% body translated (55 / 96 files still English)

K-ISMS/PIPA context already established in existing files; leverage as baseline

🟠 MEDIUM Priority (Body Content 45–50%)

8. Spanish (es) — 45% body translated (53 / 96 files still English)

Regulatory: AEPD references required
Focus: services + blog posts first

9. Norwegian (no) — 46% body translated (52 / 96 files still English)

Previously reported as "96.1% quality" — that was infrastructure only
Check for Swedish-text contamination

10. Hebrew (he) — 48% body translated (50 / 96 files still English)

RTL layout already validated; body translation is the remaining gap
Phase 4 terminology standardisation complete — use as glossary foundation

🟡 LOWER Priority (Body Content 59–68%)

11. Arabic (ar) — 59% body translated (39 / 96 files still English)

RTL layout solid; highest body-content coverage of RTL languages
Focus: remaining blog infrastructure pages

12. Chinese (zh) — 66% body translated (33 / 96 files still English)

Focus: remaining 33 files, prioritise product and service pages

13. Japanese (ja) — 68% body translated (31 / 96 files still English)

Best body-content coverage overall; focus on closing final 31 files

📋 Recommended Batch Approach

Phase 1 (CRITICAL — NL, DA): Target first to eliminate the largest gaps Phase 2 (HIGH — FI, FR, SV, DE, KO): Maximum SEO impact for European + Asian markets Phase 3 (MEDIUM — ES, NO, HE): Round out key markets Phase 4 (LOWER — AR, ZH, JA): Polish remaining files to achieve >80% body translation

🤖 AI Translation Batch Processing Workflows

Recommended Translation Platforms

For European Languages (DE, ES, FR, NL)

Primary: DeepL Pro API

Advantages: Superior quality for European language pairs, context-aware, technical terminology
Glossary Support: Upload v3.1 vocabulary tables for consistency
Cost: ~€20-25 per million characters (December 2025 pricing, volume discounts available)
Best For: Technical content, ISMS policies, blog posts

For RTL Languages (AR, HE)

Primary: Google Cloud Translation Advanced

Advantages: Better handling of RTL text flow, Schema.org preservation
Glossary Support: Custom terminology dictionaries
Cultural Adaptation: Regional variant support (Modern Standard Arabic, Israeli Hebrew)
Best For: Full page translation with HTML structure

For Asian Languages (JA, ZH, KO)

Primary: Google Cloud Translation Advanced + Native Speaker Review

Advantages: Neural MT improvements for Asian languages, glossary support
Korean Specific: Already at 100% - use as quality benchmark
Best For: Initial draft + professional review workflow

Quality Validation Workflow

Phase 1: Automated Translation (40% effort)

Prepare glossary: Extract terminology from translation guides v3.1-v6.0
Batch process: Upload source files to translation platform
Preserve HTML: Ensure tags, attributes, Schema.org remain intact
Initial review: Automated terminology consistency check

Phase 2: Human Review (40% effort)

Native speaker review: 100% content validation
Technical accuracy: Cybersecurity terminology verification
Cultural adaptation: Local regulatory body references
Brand voice: Maintain Discordian style where applicable

Phase 3: Quality Assurance (20% effort)

HTML validation: W3C compliance check
Hreflang verification: All 14 language variants present
Schema.org validation: Structured data integrity
Visual testing: Responsive design across viewports
Link functionality: Internal and external links working

Batch Processing Best Practices

Group by Language Family:

Nordic Batch: DA, FI, NO, SV (similar grammar structures)
European Batch: DE, NL (Germanic), FR, ES (Romance)
RTL Batch: AR, HE (right-to-left specific considerations)
Asian Batch: JA, ZH, KO (character-based scripts)

Quality Checkpoints:

10% spot-check rule: Native speaker validates 10% of translated content
Terminology consistency: Cross-reference with translation guides
A/B testing: Compare AI translation vs. human translation for sample pages
Iterative improvement: Use feedback to refine glossaries and prompts

Cost-Benefit Analysis

AI Translation Advantages:

Speed: 10-50x faster than human translation
Consistency: Glossary-based terminology enforcement
Cost: 5-10x lower than professional human translation
Scalability: Parallel processing across multiple languages

Human Review Critical For:

Cultural nuances: Local market adaptation
Brand voice: Discordian philosophical style preservation
Technical accuracy: Complex cybersecurity concepts
Regulatory compliance: Local authority references

Recommended Approach:

Initial draft: AI translation with glossary (€0.02-0.03 per word)
Review: Native speaker 20% spot-check (€0.08-0.12 per word)
Final validation: Quality assurance checklist (€0.02-0.03 per word)
Total cost: €0.12-0.18 per word (vs. €0.25-0.40 for full human translation)
Note: Pricing estimates as of December 2025, subject to market rates and volume discounts

Blog Translation Status

Overview

All 26 English blog posts now have translation files in all 13 languages (338 total blog files), achieving 100% infrastructure coverage. This milestone establishes a strong SEO foundation across international markets.

High-Priority Blog Posts (3)

The following thought leadership posts have complete technical infrastructure (HTML, hreflang, Schema.org) with translated metadata across all European languages (DE, ES, FR, NL):

blog-public-isms-benefits - Core value proposition (transparency as competitive advantage)
blog-automated-convergence - Technical thought leadership (DevSecOps, cloud security)
blog-information-hoarding - Security philosophy (organizational transparency)

Status: Infrastructure Complete ✅ | Content Translation Pending ⚠️

Implementation Summary

12 New Blog Files Created (December 2025):

German (DE): blog-public-isms-benefits_de.html, blog-automated-convergence_de.html, blog-information-hoarding_de.html
Spanish (ES): blog-public-isms-benefits_es.html, blog-automated-convergence_es.html, blog-information-hoarding_es.html
French (FR): blog-public-isms-benefits_fr.html, blog-automated-convergence_fr.html, blog-information-hoarding_fr.html
Dutch (NL): blog-public-isms-benefits_nl.html, blog-automated-convergence_nl.html, blog-information-hoarding_nl.html

Technical Implementation:

HTML5 semantic structure with proper lang attributes
Complete hreflang tags (28 per file covering all 13 languages)
Schema.org BlogPosting + BreadcrumbList structured data
Localized metadata (titles, descriptions, navigation, breadcrumbs)
Translation notice with link to English source
Mobile responsive, WCAG 2.1 AA compliant

Content Status:

Metadata: Fully translated for all 4 European languages
Body content: Pending professional translation services
Estimated scope: ~9,000 words per language (~36,000 words total)
Estimated effort: 17-20 hours per language
Estimated budget: €1,530-1,800 per language (€6,120-7,200 total)

Professional Translation Guidelines

Each language guide (German-Translation-Guide.md, Spanish-Translation-Guide.md, etc.) now includes a comprehensive "Blog Translation Guidelines" section with:

Translation Standards:

Blog-specific cybersecurity terminology tables
Regulatory body references (BSI, AEPD, CNIL, AP, DSGVO, RGPD, AVG)
Discordian style preservation guidelines (23 FNORD 5, Law of Fives, etc.)
HTML structure templates and hreflang patterns

Translation Workflow (3 Phases):

Setup ✅ Complete - Infrastructure and metadata ready
Content Translation ⚠️ Pending - Professional services required
Quality Assurance - Validation checklists provided

Blog-Specific Guidelines:

Individual guidance for each of 3 high-priority posts
Focus areas, complexity ratings, and cultural adaptation strategies
Effort estimates (5-7 hours per post)
Budget breakdowns (€480-640 per post)

Key Translation Requirements:

Keep code examples in English (translate explanations only)
Maintain professional C-suite business tone
Preserve Discordian philosophical voice with cultural adaptation
Adapt regulatory references for local markets
Ensure technical accuracy in cybersecurity terminology

Translator Qualifications:

Native-level proficiency in target language
Cybersecurity expertise (ISMS, ISO 27001, DevSecOps)
Business writing experience for executive audience
Understanding of local regulatory environment

Swedish Blog-Specific Documentation

Swedish has additional specialized documentation for blog translations:

SWEDISH_BLOG_TRANSLATION_GUIDE.md - CIA blog series translation guide
SWEDISH_BLOG_TRANSLATION_STATUS.md - CIA blog translation status
SWEDISH_BLOG_CREATION_STATUS.md - Blog creation progress

Note: These files use uppercase naming (SWEDISH_BLOG_*) as they are specialized, topic-specific documentation (CIA blog series), not general language guides. They are preserved from earlier work and referenced by the general Swedish translation files.

Quick Start

For Translators

Find your language: Locate [YourLanguage]-Translation-Guide.md
Read the guide: Understand terminology, structure, and requirements
Check status: Review [YourLanguage]-Translation-Status.md for current progress
Follow workflow: Use the step-by-step translation workflow in the guide
Validate: Complete the validation checklist before submission

For Project Managers

Check overall status: Review individual language status files
Identify priorities: Look for "Priority: HIGH" markers in status files
Track progress: Monitor completion percentages in status files
Estimate effort: Each status file includes effort estimates

For Developers

HTML structure: Each guide includes proper HTML templates
Hreflang tags: Comprehensive hreflang patterns documented
Schema.org: Structured data requirements specified
Validation: Technical validation checklists provided

Translation Approach

Two-Phase Strategy

Phase 1: Technical Infrastructure ✅ (Complete for high-priority blogs)

Create HTML files with proper structure
Implement complete hreflang tags
Add Schema.org structured data
Translate metadata (titles, descriptions, navigation)
Set up translation notices
Benefits: Immediate SEO improvement, professional presentation

Phase 2: Content Translation ⚠️ (Pending professional services)

Professional translation of blog body content
Cultural adaptation of examples and references
Quality assurance and native speaker review
Benefits: Complete multilingual thought leadership, improved user experience

This approach provides immediate international SEO benefits while enabling cost-effective professional translation when budget permits.

Translation Quality Standards

All translations must meet:

✅ Professional business tone appropriate for cybersecurity consulting
✅ Technical accuracy in cybersecurity terminology
✅ Terminology consistency using verified vocabulary from translation guides (v3.1+)
✅ Proper HTML structure with valid markup
✅ Complete hreflang tags for SEO
✅ Schema.org validation for structured data
✅ Native speaker review for language quality
✅ Mobile responsiveness maintained
✅ Accessibility standards (WCAG 2.1 AA)

Blog-Specific Quality Standards

For blog post translations, additionally ensure:

✅ Discordian voice preserved - Maintain unique philosophical style
✅ Code examples in English - Only translate explanations
✅ Cultural adaptation - Adjust references for local context
✅ Regulatory accuracy - Use correct local regulatory bodies
✅ Business value emphasis - Highlight competitive advantages
✅ Technical depth maintained - Preserve cybersecurity expertise

File Naming Convention

HTML Files

English: [page].html
Translations: [page]_[code].html
Example: index.html → index_sv.html, index_ja.html

Documentation Files

Guide: [Language]-Translation-Guide.md
Status: [Language]-Translation-Status.md
Example: Swedish-Translation-Guide.md, Swedish-Translation-Status.md

Infrastructure Status

Status	Languages	Details
✅ 100% Complete	All 13	HTML structure, hreflang, Schema.org
⚠️ Translation Required	Most	Professional content translation needed
✅ Substantially Complete	Swedish	~85-90% content translated

Translation Workflow

Infrastructure (✅ Complete for all languages)
- HTML files created with proper lang attributes
- Hreflang tags configured
- Schema.org structured data in place
- Navigation structure ready
Content Translation (⚠️ In Progress)
- Professional translation of content
- Technical terminology verification
- Native speaker review
- Quality assurance
Validation (Per File)
- HTML validation (W3C)
- Hreflang verification
- Schema.org validation
- Grammar and spelling check
- Link functionality test
- Mobile responsive test

Technology Stack

HTML5: Semantic markup
CSS3: Single styles.css with RTL support
Deployment: AWS S3 + CloudFront
CI/CD: GitHub Actions with Lighthouse audits
Security: ZAP security scanning

Success Metrics & Impact

SEO & Discoverability

✅ Complete hreflang implementation signals proper internationalization
✅ Rich structured data enhances search result appearance
✅ 100% blog infrastructure coverage across 13 languages
⏳ Improved rankings in European search engines (pending content translation)
⏳ Increased organic traffic from target markets

Business Value

✅ Foundation for European market expansion established
✅ Professional multilingual presence demonstrates commitment
✅ Immediate SEO benefits from complete technical infrastructure
⏳ Thought leadership in multiple languages (pending content translation)
⏳ Competitive advantage in international cybersecurity consulting

Technical Achievements

✅ 748 HTML files across 13 languages (up from 736)
✅ 338 blog files (26 English + 312 translations)
✅ 100% infrastructure coverage for all blog posts
✅ Consistent hreflang implementation (28 tags per file)
✅ Valid Schema.org structured data across all files

Documentation Efficiency

✅ Consolidated blog guidance into existing translation guides
✅ Single source of truth per language maintained
✅ Reduced documentation files by 21% while preserving all information
✅ Improved discoverability with integrated content

Contact

For questions about translation documentation:

Repository: https://github.com/Hack23/homepage
Issues: Create GitHub issue with translation label
Documentation: This file and individual language guides

Last Updated: March 2026
Guide Version: 3.1 (Enhanced Vocabulary Edition)
Maintainer: Hack23 AB Translation Team
Total Files: 1,248 translation files (100% infrastructure complete ✅ | ~32% body content translated ⚠️) | 29 documentation files (26 guides/status + 3 Swedish blog-specific)
Vocabulary Coverage: 60-91 verified term pairs per language extracted from real translated content

🔄 Session Progress Tracking

Session 9: Black Trigram Game Pages - Japanese Translation Fix (January 2026) ✅ COMPLETE

Focus: Fix corrupted Japanese translations in Black Trigram game pages (HEAD section metadata only)

Problem Identified:

Japanese translation files had extensive Korean character corruption in HEAD sections
Mixed scripts throughout JSON-LD structured data (e.g., "싱글プレ" - Korean + Japanese)
Invalid gaming terminology and mixed language particles

Files Fixed (3 Japanese files):

✅ black-trigram_ja.html - Main game landing page (HEAD fixed)
✅ black-trigram-features_ja.html - Game features page (HEAD fixed)
✅ black-trigram-docs_ja.html - Game documentation page (HEAD fixed)

Files Verified (3 Korean files - no changes):

✅ black-trigram_ko.html - Already properly translated
✅ black-trigram-features_ko.html - Already properly translated
✅ black-trigram-docs_ko.html - Already properly translated

Translation Fixes Applied:

Removed ALL Korean characters from HEAD sections ✅
Replaced with proper Japanese translations ✅
Fixed 50+ gaming and martial arts terms ✅
Corrected JSON-LD structured data ✅

Metadata Cleaned:

Meta description tags ✅
Meta keywords (gaming-specific) ✅
Open Graph tags (og:title, og:description) ✅
Twitter Card metadata ✅
Schema.org JSON-LD (VideoGame, gameTip, gameItem, etc.) ✅

Quality Metrics:

JSON-LD validation: 6/6 passed ✅
Korean characters in Japanese HEAD: 0 ✅
Gaming terminology accuracy: 100% ✅
Professional game marketing tone maintained ✅

Key Gaming Translations (Korean → Japanese):

게임 → ゲーム (game)
전투 → 戦闘 (combat)
캐릭터 → キャラクター (character)
무술 → 武術 (martial arts)
전사 → 戦士 (warrior)
난이도 → 難易度 (difficulty)

Scope Note:

⚠️ Only HEAD section metadata was fixed (as requested)
BODY content was intentionally NOT modified
Focus on SEO, Open Graph, and structured data only

Session 8: CIA Project & Features Pages (January 2026) ✅ COMPLETE

Focus: Japanese and Korean translations for CIA product pages

Files Completed (6/6):

✅ cia-project_ja.html - Main CIA project page (Japanese)
✅ cia-features_ja.html - CIA features page (Japanese)
✅ projects_ja.html - Projects overview page (Japanese)
✅ cia-project_ko.html - Main CIA project page (Korean)
✅ cia-features_ko.html - CIA features page (Korean)
✅ projects_ko.html - Projects overview page (Korean)

Translation Coverage:

Open Graph tags (og:title, og:description) ✅
Schema.org JSON-LD structured data ✅
Keywords meta tags ✅
Twitter Card metadata ✅
Page titles ✅
Breadcrumb navigation ✅
Application descriptions ✅
Feature lists ✅

Quality Metrics:

JSON-LD validation: 6/6 passed ✅
Professional B2B tone maintained ✅
OSINT and political transparency terminology accurate ✅
50+ individual text elements translated ✅

Key Terminology:

Japanese: 透明性 (transparency), 議会監視 (parliamentary monitoring), オープンソースインテリジェンス (OSINT)
Korean: 투명성 (transparency), 의회 모니터링 (parliamentary monitoring), 오픈소스 인텔리전스 (OSINT)

Previous Sessions (Summary)

Sessions 1-7: Core Website & Services Pages

56 files completed across Japanese and Korean
Homepage, services, about, and supporting pages
Foundation for CIA product pages established

Progress Totals:

Sessions 1-9: 68 files completed
Japanese files: 34 (with Session 9 fixes)
Korean files: 34 (verified in Session 9)

Next Priority (Session 10 Suggestion):

CIA documentation pages (cia-docs, cia-compliance-manager-docs)
CIA FAQ pages (cia-triad-faq)
Additional product pages in Japanese/Korean
Black Trigram body content translation (if needed)

FilesExpand file tree

TRANSLATION_DOCUMENTATION_README.md

Latest commit

History

TRANSLATION_DOCUMENTATION_README.md

File metadata and controls

Translation Documentation

Overview

⚠️ Translation Gap Analysis (March 2026 — Measured)

📏 Measurement Methodology

What "Infrastructure %" Measures

What "Body Content %" Measures

🎉 Latest Update: Translation Infrastructure Complete (January 2026)

Current State: Infrastructure vs. Content Translation

Revised Summary Statistics (March 2026 — Measured Values):

⚠️ Translation Quality Clarification (January 13, 2026)

Known Content Translation Issues:

Revised Language Status (March 2026 — Actual Measured Values):

Action Plan for Full Translation:

📋 Historical: Previous Infrastructure Updates (Early January 2026)

File Infrastructure Completion (January 2-4, 2026):

🎉 Previous Update: PR #912 Complete - Massive Translation Expansion (December 30, 2025)

European ISMS Policies - 113 Files Completed ✅

RTL & Asian ISMS Policies - 87 Files Completed ✅

Nordic Languages - 78 Files Completed ✅

🎉 Previous Update: Major Translation Milestones (December 24, 2025)

Swedish Excellence - 98.3% Quality 🎉

Korean Complete - 100% Infrastructure 🎉

Hebrew Quality Leap - 80%+ 🎉

Nordic Homepage Translations 📊

European Blog Infrastructure ✅

🆕 Enhanced Vocabulary Edition (v3.1 - December 2025)

🎉 Translation Milestones (Q4 2025)

Swedish - Phase 1-5 Complete ✅

Korean - 100% Infrastructure Complete ✅

Hebrew - Phase 4 Terminology Standardization Complete ✅

Nordic Languages - Homepage Translation Updates (Dec 24, 2025) ✅

European Blog Infrastructure (3 High-Priority Posts) ✅

✅ Quality Assurance Status (December 2025)

Key Metrics

Structure

Supported Languages (13)

RTL Languages ←

Asian Languages 🌏

Nordic Languages ❄️

European Languages 🇪🇺

Base Language 👑

📊 Visual Translation Overview

📋 Priority Recommendations (Based on Measured Body-Content Gaps)

⚡ CRITICAL — Translate First (Body Content < 25%)

1. Dutch (nl) — 12% body translated (84 / 96 files still English) 🔴

2. Danish (da) — 24% body translated (73 / 96 files still English) 🔴

🔴 HIGH Priority (Body Content 25–50%)

3. Finnish (fi) — 25% body translated (72 / 96 files still English)

4. French (fr) — 28% body translated (69 / 96 files still English)

5. Swedish (sv) — 37% body translated (60 / 96 files still English)

6. German (de) — 42% body translated (56 / 96 files still English)

7. Korean (ko) — 43% body translated (55 / 96 files still English)

🟠 MEDIUM Priority (Body Content 45–50%)

8. Spanish (es) — 45% body translated (53 / 96 files still English)

9. Norwegian (no) — 46% body translated (52 / 96 files still English)

10. Hebrew (he) — 48% body translated (50 / 96 files still English)

🟡 LOWER Priority (Body Content 59–68%)

11. Arabic (ar) — 59% body translated (39 / 96 files still English)

12. Chinese (zh) — 66% body translated (33 / 96 files still English)

13. Japanese (ja) — 68% body translated (31 / 96 files still English)

📋 Recommended Batch Approach

🤖 AI Translation Batch Processing Workflows

Recommended Translation Platforms

For European Languages (DE, ES, FR, NL)

For RTL Languages (AR, HE)

For Asian Languages (JA, ZH, KO)

Quality Validation Workflow

Phase 1: Automated Translation (40% effort)

Phase 2: Human Review (40% effort)

Phase 3: Quality Assurance (20% effort)

Batch Processing Best Practices

Cost-Benefit Analysis

Blog Translation Status

Overview