mirror of
https://github.com/jacobinwwey/obsidian-NotEMD.git
synced 2026-07-22 12:40:25 +00:00
| .. | ||
| .vitepress | ||
| assets | ||
| brainstorms | ||
| dist | ||
| export | ||
| i18n | ||
| maintainer | ||
| releases | ||
| repo-saga | ||
| superpowers | ||
| architecture.md | ||
| architecture.zh-CN.md | ||
| chapter-split-toc.md | ||
| chapter-split-toc.zh-CN.md | ||
| index.md | ||
| index.zh-CN.md | ||
| README.md | ||
| README.zh-CN.md | ||
| SINGLE_FILE_BUNDLER.md | ||
| SLIDEV_HTML_FIX.md | ||
| SLIDEV_SOLUTION.md | ||
| STANDALONE_BUNDLE_FIX.md | ||
Notemd Docs Hub
Language: English | 简体中文
This directory contains repository-level documentation for maintainers and contributors.
User And Maintainer Entry Points
- Language Hub
- GitHub Pages Language And GEO Workflow
- Chapter Split + TOC Extraction
- Release Workflow
- Release Notes 1.8.2
Slide Export Documentation
- Slidev Standalone Acceptance, 2026-06-18 - Real
architecture.zh-CN.mdstrict native standalone acceptance - Slidev Export Workflow Verification - Maintainer gate for UI-equivalent export workflow
- Standalone Bundle Fix - Earlier export transformation bug fix (2026-06-16)
- Single-File Bundler - Architecture and implementation overview
- Slidev Solution Summary - Current standalone-first export truth
- Slidev HTML Fix - Original problem analysis and testing
Engineering Planning Docs
- Diagram Platform Phase 2 Requirements
- Local KB Retrieval Decision And Quality Truth
- Local KB RAG Quality And Execution Truth
- Chapter Split Knowledge Management And TOC Comparison Truth
- Diagram Rendering Platform Roadmap
- Language Support Multiphase Plan
- AGENTS And Provider Expansion Plan
- China Provider Expansion Round 2 Plan
Documentation Language Convention
- Plan docs under
docs/superpowers/plans/use explicit locale suffixes:name.en.mdandname.zh-CN.md. - Outside the plan directory, older source docs may still use
name.mdplus a companion language file until they are migrated. - Release notes are stored as two complete files, one English and one Simplified Chinese. GitHub release publishing composes those two files into one bilingual release body at publish time.
- Do not add inline bilingual summary blocks to active docs. Keep each language in its own complete file.