zengen 0.2.4 → 0.2.6

package/.zen/src/de-DE/48eb2ad3e174cd06ed16c959fa58e0381dbc4a4147fa3456b21eea2b3d67c329.md

@@ -1,81 +0,0 @@
----
-title: ZEN - Markdown-Dokumentationsseiten-Generator
-summary: ZEN ist ein minimalistisches, statisches Site-Generierungstool für Markdown, das Inhalte priorisiert und Minimalismus betont. Es nutzt KI für intelligente Navigation und mehrsprachige Übersetzung, um Nutzern zu helfen, sich auf das Schreiben zu konzentrieren, ohne komplexe Konfigurationen.
-tags:
-  - Markdown
-  - Statische Site-Generierung
-  - KI-Übersetzung
-  - Mehrsprachig
-  - Minimalismus
-  - Dokumentationstool
-  - ZEN
-inferred_lang: de-DE
----
-
-# ZEN - Minimalistisches Markdown-Dokumentationsseiten-Tool
-
-[简体中文](https://zccz14.github.io/ZEN/zh-Hans) |
-[English](https://zccz14.github.io/ZEN/en-US) |
-[Español](https://zccz14.github.io/ZEN/es-ES) |
-[Português](https://zccz14.github.io/ZEN/pt-PT) |
-[Русский](https://zccz14.github.io/ZEN/ru-RU) |
-[Français](https://zccz14.github.io/ZEN/fr-FR) |
-[日本語](https://zccz14.github.io/ZEN/ja-JP) |
-[한국어](https://zccz14.github.io/ZEN/ko-KR) |
-[Deutsch](https://zccz14.github.io/ZEN/de-DE) |
-
-Warum noch ein statischer Markdown-Site-Generator? Ich habe überlegt, wie Dokumentationstools im KI-Zeitalter Autoren besser dienen können:
-
-- **Zurück zu den Inhalten**: Minimale Ablenkung, Fokus auf das Schreiben
-
-  Lasst die Dokumentation zu ihrem Wesen zurückkehren und das Schreiben zur Ruhe.
-
-  Erstens: Ich möchte kein Bibliothekar sein. Manchmal möchte ich etwas aufschreiben, aber vielleicht habe ich noch keinen Titel dafür oder es ist noch nicht besonders organisiert. Ich wünsche mir, dass eine LLM automatisch Titel generiert, Zusammenfassungen erstellt, kategorisiert, Navigation erstellt und andere organisatorische Aufgaben übernimmt.
-
-  Zweitens: Mein Arbeitszimmer muss aufgeräumt sein. Ich möchte keine komplexen Build-Tools konfigurieren, mich nicht mit komplizierten Dokumenteneinstellungen herumschlagen und keine komplexen Strukturen. Jedes Mal, wenn ich die Konfigurationsdateien und Projektstrukturen von Tools wie Docusaurus, VuePress oder Astro sehe, bekomme ich Kopfschmerzen. Jetzt versteckt ZEN alle Konfigurationen im `.zen`-Verzeichnis, schiebt sie in die Ecke. Der Nutzer muss sich nur auf den Inhalt konzentrieren, den Rest erledigt ZEN. Alle anderen Verzeichnisse sind Ihr Schreibbereich, Sie können Ihre Markdown-Dateien beliebig organisieren.
-
-- **Zurück zur Muttersprache**: In der Muttersprache schreiben, nahtlos mehrsprachige Versionen erstellen
-
-  Das Leben ist kurz, ich bin zu faul zum Übersetzen. Man denkt am tiefsten in seiner Muttersprache. Gleichzeitig ist es notwendig, mit der Welt verbunden zu bleiben, ich möchte den mehrsprachigen Austausch nicht aufgeben. Daher wünsche ich mir ein Tool, mit dem ich in meiner Muttersprache schreiben kann, aber gleichzeitig mehr Menschen meine Inhalte zugänglich machen kann. Aktuelle i18n-Lösungen erfordern nicht nur eigene Übersetzungen, sondern auch die Pflege von Inhaltsaktualisierungen – das ist zu umständlich. Ich nutze LLMs für Übersetzungen, das spart mir viel Zeit und mehrsprachige Übersetzungen sind mit einem Klick erledigt.
-
-## Grundlegende Funktionen
-
-1. **Statische Site-Generierung**
-   - Erstellt aus einem beliebigen Ordner mit Markdown-Dateien eine statische HTML-Website.
-
-2. **Intelligente Navigation**
-   - Generiert eine Sitemap und Navigation. Die ursprüngliche Verzeichnisstruktur der Markdown-Quelldateien muss nicht beibehalten werden, Quelldateien können beliebig verschoben werden.
-
-3. **Inkrementelle i18n-Übersetzung**
-   - Nutzt LLMs für inkrementelle i18n-Übersetzungen. Nutzer schreiben Markdown in ihrer Muttersprache, können aber mehrsprachige Inhalte bereitstellen.
-
-## Designphilosophie
-
-- **Minimalismus**: Minimale Konfiguration, maximale Flexibilität.
-- **Inhalte zuerst**: Fokus auf das Schreiben, nicht auf Tool-Konfiguration.
-- **KI-gestützt**: Nutzt KI für Übersetzung und Inhaltsorganisation.
-- **Mehrsprachig**: Unterstützt mehrsprachige Inhaltserstellung und -darstellung.
-
-## Schnellstart
-
-### Empfohlene Verwendung
-
-**Es wird empfohlen, in das Verzeichnis mit den Markdown-Dateien zu wechseln und direkt mit dem folgenden Befehl mit dem Build zu beginnen:**
-
-```bash
-# Umgebungsvariablen setzen (an Ihre Situation anpassen)
-export OPENAI_API_KEY="sk-xxxxxx"  # Erforderlich: Bitte durch Ihren OpenAI API Key ersetzen
-export OPENAI_BASE_URL="https://api.openai.com/v1"  # Optional, standardmäßig wird die offizielle OpenAI-API verwendet
-export OPENAI_MODEL="gpt-3.5-turbo"  # Optional, standardmäßig wird das gpt-3.5-turbo-Modell verwendet
-
-# Site bauen, mit mehrsprachiger Übersetzungsunterstützung
-npx zengen@latest build --lang zh-Hans --lang en-US --verbose
-```
-
-**Weitere Parameter oder Hilfe anzeigen**:
-
-```bash
-npx zengen
-```
-
-**Hinweis**: ZEN erzwingt die Verwendung des aktuellen Verzeichnisses als Quellverzeichnis und gibt die Dateien im Verzeichnis `.zen/dist` aus. Das Angeben von Quell- und Ausgabeverzeichnissen als Parameter wird nicht unterstützt.

package/.zen/src/en-US/01d04f7c17b4a541ead9d759d877b30b403e15b849182a49eb1f62bd29ecd18c.md

@@ -1,120 +0,0 @@
----
-title: GitHub Pages Deployment Configuration
-summary: This document describes the GitHub Pages deployment configuration for the ZEN project documentation site, including workflow, trigger conditions, build steps, custom configuration, troubleshooting, and manual trigger methods.
-tags:
-  - GitHub Pages
-  - Deployment Configuration
-  - Workflow
-  - Documentation Build
-  - Troubleshooting
-  - ZEN Project
-inferred_lang: en-US
----
-
-# GitHub Pages Deployment Configuration
-
-This directory contains the GitHub Pages deployment configuration for the ZEN project documentation site.
-
-## Workflow
-
-### `pages.yml`
-
-This workflow automatically builds the ZEN project documentation site and deploys it to GitHub Pages.
-
-**Trigger Conditions:**
-
-- Push to the `main` branch (when changes occur in `demo/src/`, `package.json`, or workflow files)
-- Pull Request targeting the `main` branch
-- Manual trigger
-
-**Workflow Steps:**
-
-1.  **Checkout code**: Check out code from the remote branch to ensure code synchronization.
-2.  **Set up Node.js**: Configure the Node.js 20.x environment.
-3.  **Install dependencies**: Install project dependencies using `npm ci`.
-4.  **Build zengen**: Build the local zengen package.
-5.  **Install zengen**: Install the locally built zengen as a global tool.
-6.  **Test zengen CLI**: Verify the CLI tool functions correctly.
-7.  **Build documentation site**: Build the documentation using `cd demo/src && zengen build`, outputting to the `.zen/dist` directory.
-8.  **Configure Pages**: Set up GitHub Pages.
-9.  **Upload artifact**: Upload the built documentation site as a Pages artifact.
-10. **Deploy to GitHub Pages**: Automatically deploy to GitHub Pages.
-
-## Accessing the Documentation Site
-
-After successful deployment, the documentation site will be accessible at the following URL:
-
-```
-https://[username].github.io/[repository-name]/
-```
-
-## Custom Configuration
-
-### Custom Domain
-
-If a custom domain is needed, you can add a CNAME file after the build step:
-
-```yaml
-# Create CNAME file (if a custom domain is needed)
-echo "docs.example.com" > docs-dist/CNAME
-```
-
-### Build Options
-
-Currently used build command:
-
-```bash
-cd demo/src
-zengen build --verbose
-```
-
-Available options:
-
-- `--verbose`: Show verbose output.
-- `--watch`: Watch mode (not suitable for CI/CD).
-- `--template`: Specify a custom template file.
-- `--config`: Specify a configuration file.
-
-### Environment Variables
-
-The workflow uses the following environment variables:
-
-- `GITHUB_TOKEN`: Automatically provided GitHub token.
-- `NODE_VERSION`: Node.js version (defaults to 20.x).
-
-## Troubleshooting
-
-### Build Failure
-
-1.  **Check Node.js version**: Ensure a supported Node.js version is used.
-2.  **Verify dependency installation**: Ensure `npm ci` executes successfully.
-3.  **Check build output**: Review the verbose output of `zengen build`.
-4.  **CLI output directory issue**: ZEN now forces output to the `.zen/dist` directory and no longer supports the `--out` parameter.
-
-### Deployment Failure
-
-1.  **Check permissions**: Ensure the workflow has correct write permissions for Pages.
-2.  **Verify artifact**: Ensure the `.zen/dist` directory contains valid HTML files.
-3.  **Review logs**: Check GitHub Actions logs for detailed error messages.
-
-### Documentation Not Updated
-
-1.  **Check trigger conditions**: Ensure files in the `demo/src/` directory were modified.
-2.  **Wait for deployment completion**: GitHub Pages deployment may take a few minutes.
-3.  **Clear browser cache**: The browser may be caching an old version.
-
-## Manual Trigger
-
-Deployment can be manually triggered via the GitHub Actions interface:
-
-1.  Go to the repository's "Actions" tab.
-2.  Select the "Deploy to GitHub Pages" workflow.
-3.  Click the "Run workflow" button.
-4.  Select the branch and run.
-
-## Related Files
-
-- `demo/src/`: Documentation source files (Markdown format).
-- `package.json`: Project configuration and dependencies.
-- `src/cli.ts`: zengen CLI tool implementation.
-- `src/builder.ts`: Documentation builder implementation.

package/.zen/src/en-US/04319611d7cde718d0e82da8e034e04b15fb3bb37c3784d8f7313577c5178b06.md

@@ -1,73 +0,0 @@
----
-title: ZEN - Markdown Documentation Site Builder
-summary: ZEN is a minimalist Markdown static site generator focused on content writing. It leverages AI for translation and navigation, supports multilingual builds, and requires no complex configuration.
-tags:
-  - Markdown
-  - Static Site Generator
-  - AI Translation
-  - Multilingual
-  - Minimalism
-  - Documentation Tool
-  - ZEN
-inferred_lang: en-US
----
-
-# ZEN - A Minimalist Markdown Documentation Site Builder
-
-[简体中文](https://zccz14.github.io/ZEN/zh-Hans) | [English](https://zccz14.github.io/ZEN/en-US)
-
-Why create another Markdown static site generator? I've been rethinking how documentation tools can better serve writers in the AI era:
-
-- **Return to Content**: Minimize distractions, focus on writing.
-
-  Let documentation return to its essence, and let writing return to tranquility.
-
-  First, I don't want to be a librarian. Sometimes I want to jot down some content, but I might not have thought of a title yet, or haven't formed a specific structure. I hope LLMs will automatically help me generate titles, summaries, categorize, and organize navigation.
-
-  Second, my study must be kept tidy. I don't want complex build tools, fiddling with intricate documentation configurations, or complicated structures. Every time I see the configuration files and project structures of tools like Docusaurus, VuePress, or Astro, my head hurts. Now, ZEN chooses to hide all configurations in the `.zen` directory, swept into a corner. Users only need to focus on writing content; everything else is handled by ZEN. All other directories are your writing space; you can organize your Markdown files however you like.
-
-- **Return to Native Language**: Write in your native language, build multilingual versions seamlessly.
-
-  Life is short; I'm too lazy to translate. People can best express the depth of their thinking when using their native language. Yet, staying connected to the world is necessary; I don't want to give up multilingual communication. So, I wanted a tool that allows me to write in my native language while enabling more people to see my content. Current i18n solutions not only require manual translation but also self-maintenance of content updates, which is too troublesome. I choose to use LLMs to handle translation for me, saving a lot of time and enabling one-click translation into multiple languages.
-
-## Core Features
-
-1. **Static Site Generation**
-   - Build any folder containing Markdown files into a static HTML site.
-
-2. **Intelligent Navigation**
-   - Generate site maps and navigation. You don't need to maintain the original directory structure of the Markdown source files; you can move source files around freely.
-
-3. **Incremental i18n Translation**
-   - Use LLMs for incremental i18n translation, allowing users to write Markdown in their native language while the site can be multilingual.
-
-## Design Philosophy
-
-- **Minimalism**: Minimal configuration, maximum flexibility.
-- **Content First**: Focus on writing, not tool configuration.
-- **AI-Powered**: Leverage AI for translation and content organization.
-- **Cross-Language**: Support multilingual content creation and display.
-
-## Quick Start
-
-### Recommended Usage
-
-**It is recommended to switch to the directory containing your Markdown files and directly use the following command to start building:**
-
-```bash
-# Set environment variables (modify according to your actual situation)
-export OPENAI_API_KEY="sk-xxxxxx"  # Required: Replace with your OpenAI API Key
-export OPENAI_BASE_URL="https://api.openai.com/v1"  # Optional, defaults to the official OpenAI API
-export OPENAI_MODEL="gpt-3.5-turbo"  # Optional, defaults to the gpt-3.5-turbo model
-
-# Build the site with support for multilingual translation
-npx zengen@latest build --lang zh-Hans --lang en-US --verbose
-```
-
-**To view more parameters or help**:
-
-```bash
-npx zengen
-```
-
-**Note**: ZEN enforces using the current directory as the source directory and outputs to the `.zen/dist` directory. It does not support specifying source and output directory parameters.

package/.zen/src/en-US/1b798c44a4f353e47296ca83d5905e37e6aba3e90bbd9bc3b3d34fc12059a2ca.md

@@ -1,75 +0,0 @@
----
-title: ZEN - Markdown Documentation Site Builder
-summary: ZEN is a minimalist static site generator focused on building HTML sites from Markdown folders. It supports intelligent navigation and AI-powered incremental translation, emphasizing content-first and cross-language support without complex configuration.
-tags:
-  - Markdown
-  - Static Site Generation
-  - AI Translation
-  - Minimalism
-  - Multilingual
-  - Documentation Tool
-  - ZEN
-inferred_lang: en-US
----
-
-# ZEN - A Concise Markdown Documentation Site Builder
-
-> 📖 **Reading Note**: This README is the Chinese version. The English version will be automatically generated by AI translation.
-
-## Project Motivation
-
-### Return to Content
-
-I enjoy contemplation but dislike complex build tools, fiddling with intricate documentation configurations, and complicated structures.
-
-### Return to Native Language
-
-Life is short, I use AI translation. Stay connected with the world.
-
-## Core Features
-
-1. **Static Site Generation**
-   - Build a static HTML site from any folder containing Markdown files.
-
-2. **Intelligent Navigation**
-   - Generate site maps and navigation without needing to preserve the original directory structure of the Markdown source files.
-
-3. **Incremental i18n Translation**
-   - Use LLM for incremental i18n translation, allowing users to write Markdown in their native language while supporting multilingual audiences.
-
-## Design Philosophy
-
-- **Minimalism**: Minimal configuration, maximum flexibility.
-- **Content-First**: Focus on writing, not tool configuration.
-- **AI-Powered**: Leverage AI for translation and content organization.
-- **Cross-Language**: Support multilingual content creation and display.
-
-## Quick Start
-
-### Recommended Usage
-
-**It is recommended that users switch to the directory containing Markdown files and directly use the following command to start building:**
-
-```bash
-npx zengen build
-```
-
-### Other Usages
-
-1. **Live Preview (Watch for file changes)**:
-
-```bash
-npx zengen build --watch
-```
-
-2. **View more parameters or help**:
-
-```bash
-npx zengen
-```
-
-**Note**: ZEN enforces using the current directory as the source directory and outputs to the `.zen/dist` directory. Specifying source and output directory parameters is no longer supported.
-
----
-
-**ZEN** - Let documentation return to its essence, let writing return to tranquility.

package/.zen/src/en-US/1e96be58d76c60056b708eb5bd8b8b81d7b5845d9cfe0b879d85068a5f11df3a.md

@@ -1,189 +0,0 @@
----
-title: ZEN Documentation Site Best Practices
-summary: This document introduces best practices for building documentation sites using ZEN, covering multilingual management, performance optimization, deployment strategies, maintenance recommendations, common issue solutions, and advanced techniques, aiming to help users efficiently develop and maintain documentation.
-tags:
-  - ZEN
-  - Documentation Site
-  - Best Practices
-  - Performance Optimization
-  - Deployment Strategy
-  - Multilingual Management
-  - Maintenance Recommendations
-inferred_lang: en-US
----
-
-# Best Practices
-
-This document introduces best practices for building documentation sites using ZEN.
-
-## Multilingual Management
-
-### Translation Strategy
-
-1.  **Primary Language First**: Write the complete documentation in your native language first.
-2.  **Incremental Translation**: Only translate modified parts after each update.
-3.  **Terminology Consistency**: Create a glossary to maintain translation consistency.
-4.  **Human Review**: It is recommended to perform human review after AI translation.
-
-## Performance Optimization
-
-### Build Optimization
-
-1.  **Incremental Builds**: Use `--watch` mode for development.
-2.  **Cache Utilization**: ZEN automatically caches processing results.
-3.  **Parallel Processing**: Files are automatically processed in parallel on multi-core CPUs.
-
-### Development Workflow
-
-```bash
-# Watch for changes during development
-cd docs
-npx zengen build --watch
-
-# Start development server
-npx zengen build --watch --serve
-
-# Production build
-npx zengen build
-```
-
-## Deployment Strategy
-
-### CI/CD Integration
-
-#### GitHub Actions Example
-
-```yaml
-name: Build and Deploy Documentation
-on:
-  push:
-    branches: [main]
-    paths:
-      - 'docs/**'
-      - '.github/workflows/docs.yml'
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20.x'
-
-      - name: Build documentation
-        run: |
-          cd docs
-          npx zengen build --base-url /my-docs
-
-      - name: Deploy to GitHub Pages
-        uses: peaceiris/actions-gh-pages@v3
-        with:
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          publish_dir: docs/.zen/dist
-```
-
-#### Custom Deployment Script
-
-```bash
-#!/bin/bash
-# deploy-docs.sh
-
-# Switch to the documentation directory
-cd docs
-
-# Build documentation
-npx zengen build
-
-# Sync to server
-rsync -avz .zen/dist/ user@server:/var/www/docs/
-
-# Clean cache
-rm -rf .zen/cache
-```
-
-### Cloud Deployment Options
-
-- **GitHub Pages**: Free hosting for documentation.
-- **Vercel**: Automatic deployment for static sites.
-- **Netlify**: Supports form handling and redirects.
-- **AWS S3 + CloudFront**: Enterprise-grade static hosting.
-
-## Maintenance Recommendations
-
-### Regular Updates
-
-1.  **Content Review**: Check documentation accuracy monthly.
-2.  **Link Checking**: Regularly check for broken links.
-3.  **Performance Monitoring**: Monitor page load speed.
-4.  **User Feedback**: Collect user feedback to improve documentation.
-
-### Version Control
-
-1.  **Documentation Versioning**: Synchronize with software versions.
-2.  **Changelog**: Record documentation update history.
-3.  **Rollback Mechanism**: Support quick rollback to previous versions.
-
-## Common Issues
-
-### Slow Build Speed
-
-**Solutions:**
-
-- Reduce unnecessary images and resources.
-- Use `--watch` mode for incremental development.
-- Split large documents into multiple smaller files.
-- Disable unnecessary processors.
-
-### Poor Translation Quality
-
-**Solutions:**
-
-- Provide context to the AI translator.
-- Create a glossary to improve consistency.
-- Perform human review for critical content.
-- Adjust translation prompts.
-
-### Complex Navigation Structure
-
-**Solutions:**
-
-- Maintain a flat directory structure.
-- Use clear heading hierarchies.
-- Provide search functionality.
-- Use sidebar navigation appropriately.
-
-### High Memory Usage
-
-**Solutions:**
-
-- Reduce the number of files processed simultaneously.
-- Disable caching (not recommended).
-- Increase system memory.
-- Process large documents in batches.
-
-## Advanced Techniques
-
-### Custom Template Techniques
-
-1.  **Responsive Design**: Ensure the template displays correctly on mobile devices.
-2.  **Theme Switching**: Implement dark/light themes.
-3.  **Code Highlighting**: Integrate highlight.js or other highlighting libraries.
-4.  **Search Functionality**: Add client-side search.
-
-### Integrating Other Tools
-
-1.  **Image Optimization**: Use sharp or imagemin to optimize images.
-2.  **SEO Optimization**: Add meta tags and structured data.
-3.  **Analytics Integration**: Integrate Google Analytics or Plausible.
-4.  **CDN Acceleration**: Use a CDN to accelerate static resources.
-
-### Monitoring and Logging
-
-1.  **Build Logs**: Use `--verbose` to view detailed logs.
-2.  **Error Monitoring**: Set up error monitoring and alerts.
-3.  **Performance Monitoring**: Monitor build time and resource usage.
-4.  **User Analytics**: Analyze documentation usage.

package/.zen/src/en-US/48eb2ad3e174cd06ed16c959fa58e0381dbc4a4147fa3456b21eea2b3d67c329.md

@@ -1,81 +0,0 @@
----
-title: ZEN - Markdown Documentation Site Builder
-summary: ZEN is a clean Markdown static site generator that emphasizes content-first and minimalism. It leverages AI for intelligent navigation and multilingual translation, helping users focus on writing without complex configurations.
-tags:
-  - Markdown
-  - Static Site Generator
-  - AI Translation
-  - Multilingual
-  - Minimalism
-  - Documentation Tool
-  - ZEN
-inferred_lang: en-US
----
-
-# ZEN - A Clean Markdown Documentation Site Builder
-
-[简体中文](https://zccz14.github.io/ZEN/zh-Hans) |
-[English](https://zccz14.github.io/ZEN/en-US) |
-[Español](https://zccz14.github.io/ZEN/es-ES) |
-[Português](https://zccz14.github.io/ZEN/pt-PT) |
-[Русский](https://zccz14.github.io/ZEN/ru-RU) |
-[Français](https://zccz14.github.io/ZEN/fr-FR) |
-[日本語](https://zccz14.github.io/ZEN/ja-JP) |
-[한국어](https://zccz14.github.io/ZEN/ko-KR) |
-[Deutsch](https://zccz14.github.io/ZEN/de-DE) |
-
-Why create another Markdown static site generator? I've rethought how documentation tools can better serve writers in the AI era:
-
-- **Return to Content**: Minimize distractions, focus on writing
-
-  Let documentation return to its essence, let writing return to tranquility.
-
-  First, I don't want to be a librarian. Sometimes I want to jot down some content, but I might not have thought of its title yet, or haven't formed a specific organization. I hope LLMs will automatically help me generate titles, create summaries, categorize, navigate, and handle other organizational tasks.
-
-  Second, my study must be kept clean. I don't want complex build tools, fiddling with intricate documentation configurations, or complicated structures. Every time I see the configuration files and project structures of tools like Docusaurus, VuePress, or Astro, I get a headache. Now, ZEN chooses to hide all configurations in the `.zen` directory, sweeping them into a corner. Users only need to focus on writing content; everything else is handled by ZEN. All other directories are your writing space; you can organize your Markdown files however you like.
-
-- **Return to Native Language**: Write in your native language, smoothly build multilingual versions
-
-  Life is short; I'm too lazy to translate. People can best express the depth of their thinking when using their native language. But staying connected with the world is also necessary; I don't want to give up multilingual communication. So, I want a tool that lets me write in my native language while allowing more people to see my content. Current i18n solutions not only require you to translate yourself but also maintain content updates, which is too troublesome. I choose to use LLMs to help with translation, saving me a lot of time and enabling one-click multilingual translation.
-
-## Core Features
-
-1. **Static Site Generation**
-   - Build any folder containing Markdown files into a static HTML site.
-
-2. **Intelligent Navigation**
-   - Generate site maps and navigation. You don't need to maintain the original directory structure of the Markdown source files; you can move source files around freely.
-
-3. **Incremental i18n Translation**
-   - Use LLMs for incremental i18n translation, allowing users to write Markdown in their native language while the site can be multilingual.
-
-## Design Philosophy
-
-- **Minimalism**: Minimal configuration, maximum flexibility.
-- **Content-First**: Focus on writing, not tool configuration.
-- **AI-Powered**: Leverage AI for translation and content organization.
-- **Cross-Language**: Support multilingual content creation and display.
-
-## Quick Start
-
-### Recommended Usage
-
-**It is recommended that users switch to the directory containing Markdown files and directly use the following command to start building:**
-
-```bash
-# Set environment variables (modify according to your actual situation)
-export OPENAI_API_KEY="sk-xxxxxx"  # Required: Please replace with your OpenAI API Key
-export OPENAI_BASE_URL="https://api.openai.com/v1"  # Optional, defaults to the official OpenAI API
-export OPENAI_MODEL="gpt-3.5-turbo"  # Optional, defaults to the gpt-3.5-turbo model
-
-# Build the site, supporting multilingual translation
-npx zengen@latest build --lang zh-Hans --lang en-US --verbose
-```
-
-**View more parameters or help**:
-
-```bash
-npx zengen
-```
-
-**Note**: ZEN enforces using the current directory as the source directory and outputs to the `.zen/dist` directory. It does not support specifying source and output directory parameters.

package/.zen/src/en-US/5ec990146b35e00de2630559126ee07f7cdcddeb23b0e8cab3d85b4181353e26.md

@@ -1,53 +0,0 @@
----
-title: ZEN Advanced Usage Guide
-summary: This document introduces the advanced features of ZEN, including custom HTML templates, configuration options (such as source directory, output directory, template, base URL, and multilingual support), and the plugin system, helping users extend and customize the ZEN tool.
-tags:
-  - ZEN
-  - Advanced Usage
-  - Custom Templates
-  - Configuration Options
-  - Plugin System
-  - Documentation Generation
-  - Multilingual Support
-inferred_lang: en-US
----
-
-# Advanced Usage
-
-An in-depth introduction to the advanced features and configuration options of ZEN.
-
-## Custom Templates
-
-ZEN supports custom HTML templates:
-
-```bash
-zengen build --src ./docs --out ./dist --template ./custom-template.html
-```
-
-## Configuration Options
-
-Can be configured in the `.zenrc` file:
-
-```json
-{
-  "srcDir": "./docs",
-  "outDir": "./dist",
-  "template": "./template.html",
-  "baseUrl": "https://example.com",
-  "i18n": {
-    "sourceLang": "zh-Hans",
-    "targetLangs": ["en-US", "ja-JP"]
-  }
-}
-```
-
-## Plugin System
-
-ZEN supports plugin extensions:
-
-```typescript
-interface MarkdownProcessor {
-  beforeParse?(content: string, fileInfo: FileInfo): string | Promise<string>;
-  afterParse?(html: string, fileInfo: FileInfo): string | Promise<string>;
-}
-```

package/.zen/src/en-US/6124ea88edec5bde737b26b21f71ecfeffe4e73151784856edf813ee231a4baa.md

@@ -1,11 +0,0 @@
----
-title: Test Document
-summary: 这是一个测试文档，内容为空，仅包含标题。
-tags:
-  - 测试
-  - 文档
-  - 示例
-inferred_lang: en-US
----
-
-# Test Document