translate-sync

To synchronize website content between English and Spanish, this Skill detects the source language and content type from file paths, then creates or updates the target file to ensure multilingual parity. It automatically translates pages, blog posts, and translation strings while preserving formatting.

Yes, you can translate markdown blog posts without losing formatting and technical terms. The Skill preserves markdown formatting and technical terms during translation, ensuring only the user-facing text is translated for the target language file.

The best way to keep multilingual translation strings updated is to synchronize content directly from source file paths. This Skill detects when source content changes and updates the corresponding target language files, preventing outdated or missing translations across the website.

This content synchronization Skill works by detecting source language and content type directly from file paths. As long as your website file structure clearly distinguishes between language directories, it can create or update the target files accordingly.

A limitation of automated content synchronization for i18n is that it currently supports English and Spanish translations only. Additionally, while it preserves markdown and technical terms, complex structural elements in user-facing text may require manual review after synchronization.

To generate a Spanish counterpart for an English blog post, point the Skill to the source file path. It will translate the title, description, and body into Spanish, creating a new file that mirrors the original content while maintaining multilingual parity.