nacos-doc-sync-en

Mirror zh-cn documentation changes to English en counterparts in structured repositories.

115|205|Updated Jul 20, 2018

Search Tags:#documentation #translation #docs #workflows #en #synchronize #zh-cn

Ready to run

npx skills add https://github.com/nacos-group/nacos-group.github.io --skill nacos-doc-sync-en

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nacos-doc-sync-en
Source: https://github.com/nacos-group/nacos-group.github.io/tree/main/.agents/skills/nacos-doc-sync-en
Command: npx skills add https://github.com/nacos-group/nacos-group.github.io --skill nacos-doc-sync-en

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The tool automatically keeps Chinese zh-cn documentation in sync with its English en counterparts. It creates or updates en docs whenever zh-cn content is added or modified under src/content/docs/ or src/content/download/, ensuring bilingual parity across versions.

Core Features & Use Cases

Automatic mirroring: when a zh-cn doc is created or edited, the corresponding en document is created or updated at the same path with translated frontmatter and synchronized structure.
Version-aware synchronization: supports docs and downloads across multiple versions, preserving existing en content while applying changes from zh-cn.
Workflow integration: fits into standard content pipelines, triggering on file changes to maintain parity between zh-cn and en documentation.

Quick Start

Create or edit a zh-cn document under src/content/docs/ or src/content/download/, and the system will automatically create or update the corresponding en document.

Frequently Asked Questions about nacos-doc-sync-en

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I synchronize Chinese and English documentation automatically?▼

To synchronize bilingual documentation, this Skill mirrors zh-cn content to en paths automatically. When you create or edit a zh-cn file under src/content/docs/ or src/content/download/, it computes the corresponding en path and creates or updates the English file.

Does the documentation synchronization preserve existing English translations?▼

Yes, the documentation synchronization preserves existing en translations where present. When updating English files from zh-cn changes, it applies translated frontmatter and synchronizes structure without overwriting previously completed translation content.

Can I use this workflow to sync documentation across multiple versions?▼

Yes, you can sync documentation across multiple versions. The workflow supports version-aware synchronization for docs and downloads, applying zh-cn changes to en counterparts while maintaining the correct directory structure across different documentation versions.

How does the mirroring mechanism map zh-cn file paths to en counterparts?▼

The mirroring mechanism maps paths by replacing the zh-cn segment with en in the repository structure. It identifies zh-cn files under src/content/docs/ or src/content/download/, computes the equivalent en path, and generates or updates the target English document.

What happens when I create a new zh-cn doc without an existing English version?▼

When you create a new zh-cn doc without an English version, the workflow automatically creates the corresponding en document. It translates the frontmatter and mirrors the content structure to establish initial bilingual parity for the newly added file.

Are there limitations on which directories trigger automatic documentation synchronization?▼

Yes, a limitation is that synchronization only triggers for file changes under src/content/docs/ or src/content/download/. Modifying zh-cn files outside these specific repository directories will not initiate the automatic creation or update of en counterparts.