naver_converter

Migrating Naver Blog to Hugo involves parsing naver.md, validating front matter, and generating English, Japanese, and Chinese posts with consistent slugs and translationKeys. The workflow enforces 1:1 image mapping and updates LINK_MAPPING.md to track slug references.

1:1 image mapping preserves the exact image order and captions from Naver Blog by downloading high-resolution variants directly into the Hugo structure. This ensures visual parity between the source and the generated multilingual posts.

Handling link mapping during Hugo migration uses LINK_MAPPING.md to resolve mapped slugs and automatically marks unmapped references with TODOs. This tracking mechanism ensures no external or internal links are lost during translation.

Manual front matter translation is unnecessary because the workflow enforces front matter constraints and language-specific tag alignment automatically. It validates required fields and maintains translationKey consistency across all generated English, Japanese, and Chinese posts.

Yes, the workflow supports automated high-resolution image download and enforces language-specific tag and category alignment. It validates the Naver HTML structure parsed into naver.md to ensure complex tags are correctly mapped across multilingual outputs.

Image order issues occur when 1:1 image mapping is not enforced. This workflow specifically preserves image order and captions by downloading high-resolution variants and mapping them directly to the corresponding multilingual Hugo posts.