Yomiya Content System Docs Index
Yomiya Content System Docs Index
Section titled “Yomiya Content System Docs Index”用途:Yomiya 内容系统文档总导航
目标:在保留原始研究、策略、实施过程与历史留档的前提下,把当前执行文档、历史文档、开放问题和未来规划做成真正有层级的目录结构,让 GitHub 文件夹视图本身就能反映阅读顺序。
最后更新:2026-03-28
1. 当前目录结构
Section titled “1. 当前目录结构”YomiyaContentSystem/├── README.md├── 01-Foundations/├── 02-Current-Execution/├── 03-History-and-Governance/└── 04-Open-Questions-and-Future/这 4 层的含义分别是:
01-Foundations
Section titled “01-Foundations”原始基础文档层。回答:
- 为什么做这条线
- 最终想做成什么
- 当前工程差距在哪里
02-Current-Execution
Section titled “02-Current-Execution”当前执行层。回答:
- Phase 1 现在到底做什么
- 名词怎么统一
- 当前边界是什么
- 当前实施规格是什么
- 当前交付任务怎么拆
03-History-and-Governance
Section titled “03-History-and-Governance”历史与治理层。回答:
- 原始 implementation spec 留档
- 为什么要拆文档
- 历史 review 里发现过什么问题
- 产品运营层面曾发现过什么问题
04-Open-Questions-and-Future
Section titled “04-Open-Questions-and-Future”未决与未来层。回答:
- 还有哪些问题没定
- 后面阶段怎么演化
2. 现在最重要的 5 份文档
Section titled “2. 现在最重要的 5 份文档”如果你现在要进入 Yomiya 并开始执行,优先看这 5 份:
-
02-Current-Execution/yomiya-phase1-execution-spec.md
看当前阶段目标、指标、首页定位、核心合集、阶段判断标准。 -
02-Current-Execution/yomiya-canonical-naming.md
看命名冻结表。所有 Channel / Collection / Series / Topic / Tag / Featured / Tab 的定义以这里为准。 -
02-Current-Execution/yomiya-phase1-scope-boundary.md
看 Phase 1 边界,明确必做、可延后、明确不做。 -
02-Current-Execution/yomiya-implementation-spec-core.md
看当前有效实施规格主文档。 -
02-Current-Execution/yomiya-phase1-delivery-plan.md
看当前交付任务拆解与周级推进节奏。
3. 推荐阅读顺序
Section titled “3. 推荐阅读顺序”当前执行规则以 02-Current-Execution/ 为准。
01-Foundations/ 与 03-History-and-Governance/ 继续保留,但默认按“背景与来时路”理解,不能覆盖当前 Phase 1 冻结方案。
3.1 想快速理解项目
Section titled “3.1 想快速理解项目”01-Foundations/yomiya-research.md02-Current-Execution/yomiya-phase1-execution-spec.md02-Current-Execution/yomiya-canonical-naming.md02-Current-Execution/yomiya-phase1-scope-boundary.md02-Current-Execution/yomiya-implementation-spec-core.md01-Foundations/yomiya-content-strategy.md
3.2 研发 / 产品 / 运营现在要开工
Section titled “3.2 研发 / 产品 / 运营现在要开工”02-Current-Execution/yomiya-phase1-execution-spec.md02-Current-Execution/yomiya-canonical-naming.md02-Current-Execution/yomiya-phase1-scope-boundary.md02-Current-Execution/yomiya-implementation-spec-core.md02-Current-Execution/yomiya-phase1-delivery-plan.md
3.3 想看为什么后来要拆分、有哪些历史问题
Section titled “3.3 想看为什么后来要拆分、有哪些历史问题”03-History-and-Governance/yomiya-implementation-spec-split-plan.md03-History-and-Governance/yomiya-implementation-review-log.md03-History-and-Governance/yomiya-product-ops-review-log.md03-History-and-Governance/yomiya-implementation-spec.md
3.4 想看还有哪些问题没定、后面怎么走
Section titled “3.4 想看还有哪些问题没定、后面怎么走”04-Open-Questions-and-Future/yomiya-implementation-open-questions.md04-Open-Questions-and-Future/yomiya-implementation-future-phases.md
4. 哪些文档是原始来时路,必须保留
Section titled “4. 哪些文档是原始来时路,必须保留”以下文档属于原始基础资料或关键历史留档,当前明确保留,不粗暴重写,不随意删除:
01-Foundations/yomiya-research.md01-Foundations/yomiya-content-strategy.md01-Foundations/yomiya-engineering-gap-analysis.md03-History-and-Governance/yomiya-implementation-spec.md
它们不是现在唯一执行入口,但它们是来时路的一部分,必须保留。
5. 哪些文档不要合并
Section titled “5. 哪些文档不要合并”research+content-strategyengineering-gap-analysis+implementation-spec-corereview-log+open-questionsfuture-phases与任何当前执行文档
原因很简单:这些文档层级不同,合并后会重新变重、变脏、变难读。
6. 哪些文档未来可以考虑收敛
Section titled “6. 哪些文档未来可以考虑收敛”02-Current-Execution/yomiya-phase1-execution-spec.md+02-Current-Execution/yomiya-phase1-scope-boundary.md03-History-and-Governance/yomiya-implementation-spec-split-plan.md最终压缩为索引说明
但不是现在。现在更重要的是让目录层级先清楚成立。
7. 一句话总括
Section titled “7. 一句话总括”YomiyaContentSystem 目录现在已经按 Foundations / Current Execution / History and Governance / Open Questions and Future 四层重组。当前执行优先看 02-Current-Execution/;原始文档继续保留,作为来时路,不删、不粗暴重写。
文档体系总览图(新增)
Section titled “文档体系总览图(新增)”flowchart TD
A[YomiyaContentSystem] --> B[01-Foundations]
A --> C[02-Current-Execution]
A --> D[03-History-and-Governance]
A --> E[04-Open-Questions-and-Future]
按角色阅读(新增)
Section titled “按角色阅读(新增)”- 产品 / PM:优先看
02-Current-Execution/yomiya-implementation-spec-core.md、02-Current-Execution/yomiya-frontend-page-architecture.md、02-Current-Execution/yomiya-phase1-execution-spec.md;01-Foundations/yomiya-content-strategy.md与03-History-and-Governance/yomiya-product-ops-review-log.md只作为背景补充阅读。 - iOS / 前端:优先看
02-Current-Execution/yomiya-frontend-page-architecture.md、02-Current-Execution/yomiya-implementation-spec-core.md、02-Current-Execution/assets/*.html。 - 运营 / Content Ops:优先看
02-Current-Execution/yomiya-phase1-delivery-plan.md、02-Current-Execution/yomiya-implementation-spec-core.md;01-Foundations/yomiya-content-strategy.md只作为背景补充阅读。 - Reviewer / 对齐人员:优先看
README.md、02-Current-Execution/yomiya-phase1-execution-spec.md、02-Current-Execution/yomiya-phase1-delivery-plan.md。