You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+36-6Lines changed: 36 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,7 @@ hugegraph-doc/
59
59
60
60
## Documentation Versions
61
61
62
-
The source tree keeps only current documentation and version metadata. Docusaurus release snapshots are generated before `npm run start` and `npm run build` from Docusaurus-native Markdown sources. A version entry may set `sourceRef` to read from a Git branch or tag; when it is omitted, the current working tree is used.
62
+
The source tree keeps only current documentation and version metadata. Docusaurus release snapshots are generated before `npm run start` and `npm run build` from the configured Git source refs. A version entry may set `sourceRef` to read from a Git branch or tag; when it is omitted, the current working tree is used.
63
63
64
64
Version semantics:
65
65
@@ -68,6 +68,19 @@ Version semantics:
68
68
|`stable`|`/docs/`, `/cn/docs/`| Latest stable release documentation and the default navbar target |
69
69
|`current` / `next`|`/docs/next/`, `/cn/docs/next/`| Unreleased development documentation with an unreleased banner |
The source branch prefix is never shown in the UI. The archived release branches listed above were authored before this Docusaurus migration, so any import repair for those snapshots is isolated under `legacyCompatibility` in `src/data/versions.json`. That compatibility layer is only for adapting those historical branches to a previewable Docusaurus build; it is not part of the normal documentation authoring or version generation pipeline. Future Docusaurus-native release branches should keep the standard `content/{en,cn}/docs` layout and should not require those adapters.
83
+
71
84
Generate the Docusaurus version files locally:
72
85
73
86
```bash
@@ -82,12 +95,14 @@ List configured versions:
82
95
npm run docs:versions:list
83
96
```
84
97
85
-
To update the stable release source:
98
+
To update a release source:
86
99
87
-
1. Update the stable entry in `src/data/versions.json`, especially `label`, `githubTagUrl`, and `sourceRef` if the stable docs should come from a branch or tag.
88
-
2. Make sure the source ref contains Docusaurus-native docs and is fetched locally. CI uses `fetch-depth: 0`, so tags and release branches are available there.
100
+
1. Update the entry in `src/data/versions.json`, especially `label`, `docusaurusVersion`, `path`, `cnPath`, `githubTagUrl`, and `sourceRef`.
101
+
2. Make sure the source ref is fetched locally. CI uses `fetch-depth: 0`, so tags and release branches are available there.
89
102
3. Run `npm run docs:versions:prepare`, then `npm run build`.
90
103
104
+
Only archived pre-Docusaurus branches should use `legacyCompatibility` fields such as `sourcePaths`, `sourceIncludes`, `sourceOverlays`, `indexFrom`, or Markdown normalization. These fields document deliberate compatibility work for old snapshots, not guidance for new documentation.
105
+
91
106
Do not use `latest` ambiguously in docs navigation. Use `stable` for the latest released documentation and `next` for unreleased documentation.
92
107
93
108
## Team and User Data
@@ -220,13 +235,26 @@ hugegraph-doc/
220
235
221
236
### 文档版本
222
237
223
-
源码分支只保留当前文档和版本元数据。Docusaurus 需要的版本快照会在 `npm run start` 和 `npm run build` 前,从 Docusaurus 原生 Markdown 源生成。版本条目可以通过 `sourceRef` 指向 Git 分支或标签;未设置时使用当前工作区文档。
238
+
源码分支只保留当前文档和版本元数据。Docusaurus 需要的版本快照会在 `npm run start` 和 `npm run build` 前,从配置的 Git source ref 生成。版本条目可以通过 `sourceRef` 指向 Git 分支或标签;未设置时使用当前工作区文档。
0 commit comments