🎯 Objective

Translate body content in ~55 Korean (_ko) and ~50 Hebrew (_he) HTML files that currently contain English text despite having localized metadata and navigation.

📋 Background

Korean and Hebrew are critical for Hack23's Asian and Middle Eastern market presence. Both languages have ~50-57% of files with English body content. Hebrew additionally requires correct RTL (right-to-left) handling.

Korean (KO) breakdown:

Hebrew (HE) breakdown:

Good news: Both languages have their core pages and most product pages already translated. The primary gap is in blog posts and discordian ISMS policy articles.

Known Korean issue (from repository memory): index_ko.html has inconsistent tabindex="-1" on nav links — only the first two links have it while the remaining links do not. This should also be fixed.

✅ Acceptance Criteria

• All 18 Korean blog articles translated with Korean body content
• All 30 Korean discordian ISMS files translated with Korean body content
• Remaining 4 Korean industry/ISO files translated
• Remaining 3 Korean product files translated
• All 17 Hebrew blog articles translated with Hebrew body content
• All 30 Hebrew discordian ISMS files translated with Hebrew body content
• Remaining 3 Hebrew product files translated
• Korean uses proper Hangul characters throughout (no romanization of Korean terms)
• Hebrew uses proper RTL text direction and correct nikud where needed
• Hebrew files maintain dir="rtl" attribute where appropriate
• Korean index_ko.html tabindex inconsistency fixed (all nav links should have tabindex="-1")
• HTML structure, links, images, and metadata remain intact

🛠️ Implementation Guidance

Priority order:

1. Product pages (3 KO + 3 HE = 6 files) — finish remaining product translations
2. Industry/ISO pages (4 KO = 4 files) — complete Korean industry pages
3. Blog articles (18 KO + 17 HE = 35 files) — translate article body content
4. Discordian ISMS (30 KO + 30 HE = 60 files) — translate policy article bodies
5. Fix KO tabindex — add tabindex="-1" to remaining nav links in index_ko.html

Approach:

1. Translate <article>/<main> body content from English to Korean/Hebrew
2. For Korean: Use formal/professional register (합니다/습니다 endings)
3. For Hebrew: Ensure RTL text direction is maintained; use formal register
4. Keep HTML tags, attributes, links, images intact
5. Use index_ko.html / index_he.html as terminology reference
6. Cybersecurity terms: use standard Korean (사이버보안) / Hebrew (אבטחת סייבר) equivalents

🤖 Recommended Agent

Agent: @ui-enhancement-specialist
Rationale: This task involves HTML content translation with special requirements for Korean character encoding and Hebrew RTL support.

For implementation:

• Translate body content to professional Korean and Hebrew
• Maintain RTL layout integrity for Hebrew files
• Fix Korean nav link tabindex accessibility issue
• Preserve HTML structure, ARIA attributes, and semantic markup