website-maintainer

yamadashy's avatarfrom yamadashy

Use this skill when working on the Repomix documentation website in `website/` directory, including VitePress configuration, multi-language content, or translation workflows.

⭐21.0kstars🔀963forks📁View on GitHub🕐Updated Jan 4, 2026

When & Why to Use This Skill

The Website Maintainer skill is a specialized tool designed to manage and optimize the Repomix documentation website built with VitePress. It streamlines the complexities of maintaining a multi-language documentation site, handling everything from core configuration and sidebar navigation to intricate translation workflows across 14 different languages. By automating the structural requirements of the directory, it ensures technical consistency and simplifies the process of keeping documentation synchronized with the codebase.

Use Cases

  • Multi-language Content Synchronization: Effortlessly update documentation across 14 languages (including Japanese, Chinese, Spanish, etc.) while ensuring the English 'source of truth' is accurately reflected.
  • VitePress Configuration Management: Modify global settings, PWA configurations, and locale-specific sidebars or navigation menus through structured config shards.
  • New Language Localization: Streamline the expansion of the documentation site by automating the creation of new language directories and integrating them into the VitePress locale configuration.
  • Documentation Maintenance: Update technical guides and installation instructions in the directory while preserving critical code examples and CLI options across all versions.
namewebsite-maintainer
descriptionUse this skill when working on the Repomix documentation website in `website/` directory, including VitePress configuration, multi-language content, or translation workflows.

Website Maintainer

VitePress documentation site with 14 languages.

Structure

website/client/
├── .vitepress/
│   ├── config.ts           # Main config (imports all locales)
│   └── config/
│       ├── configShard.ts  # Shared settings (PWA, sitemap, etc.)
│       └── config[Lang].ts # Per-language config (nav, sidebar, search)
└── src/
    └── [lang]/             # en, ja, zh-cn, zh-tw, ko, de, fr, es, pt-br, id, vi, hi, it, ru

Adding New Language

  1. Create config/configXx.ts based on existing (exports config + search translations)
  2. Import and add to locales in config.ts
  3. Add search config to configShard.ts
  4. Create src/xx/ directory with content (copy from en/)

Editing Content

  • Documents: Edit src/[lang]/guide/*.md (e.g., src/ja/guide/installation.md)
  • Navigation/Sidebar: Edit config/config[Lang].ts → themeConfig.sidebar
  • Shared settings (logo, footer): Edit configShard.ts

Translation Guidelines

  • English (src/en/) is source of truth
  • Keep code examples and CLI options unchanged
  • Translate UI labels in config file (nav, sidebar, search modal)