docs(site): 同步v1.0.0文档与结构#18
Conversation
审阅者指南更新文档站点以反映 v1.0.0 版本发布,包括新的变更日志条目、下载矩阵(包含 ARM 和额外构建产物)、教程/快速上手/服务器 JAR 流程以适配全新的创建/导入体验、与 v1.0.0 代码库对齐的项目结构文档与侧边栏,以及指向 v1.0.0 GitHub Releases 的版本元数据。 更新后的服务器创建向导流程图(v1.0.0)flowchart TD
Start["User clicks Create Server"]
ChoiceSource["Choose import source"]
JAR["Server JAR"]
ExistingDir["Existing server directory"]
Script["Startup script (bat/sh)"]
Detect["Auto-detect startup mode from imported content"]
DetectOK{Startup mode matches expectation?}
CustomMode["User manually switches mode"]
CustomCmd["User enters custom startup command"]
Modpack["Optional: enable modpack auto-install"]
JavaScan["Scan system for installed Java (expanded paths)"]
JavaFound{Any Java runtime found?}
JavaSelect["User selects a detected Java version"]
JavaInstall["User triggers one-click Java installation"]
NameServer["Name server and confirm parameters"]
EULA["Accept Minecraft EULA on first launch"]
Done["Server created and ready to start"]
Start --> ChoiceSource
ChoiceSource --> JAR
ChoiceSource --> ExistingDir
ChoiceSource --> Script
JAR --> Detect
ExistingDir --> Detect
Script --> Detect
Detect --> DetectOK
DetectOK -->|Yes| Modpack
DetectOK -->|No| CustomMode --> CustomCmd --> Modpack
Modpack --> JavaScan
JavaScan --> JavaFound
JavaFound -->|Yes| JavaSelect --> NameServer
JavaFound -->|No| JavaInstall --> JavaSelect --> NameServer
NameServer --> EULA --> Done
文件级变更
提示与命令与 Sourcery 交互
自定义你的使用体验访问你的 控制面板 以:
获取帮助Original review guide in EnglishReviewer's GuideUpdates documentation site to reflect the v1.0.0 release, including new changelog entry, download matrix (with ARM and additional artifacts), tutorials/getting started/server-jar flow for the revamped creation/import experience, project structure docs and sidebars aligned with the v1.0.0 codebase, and version metadata now pointing to v1.0.0 GitHub releases. Flow diagram for the updated server creation wizard (v1.0.0)flowchart TD
Start["User clicks Create Server"]
ChoiceSource["Choose import source"]
JAR["Server JAR"]
ExistingDir["Existing server directory"]
Script["Startup script (bat/sh)"]
Detect["Auto-detect startup mode from imported content"]
DetectOK{Startup mode matches expectation?}
CustomMode["User manually switches mode"]
CustomCmd["User enters custom startup command"]
Modpack["Optional: enable modpack auto-install"]
JavaScan["Scan system for installed Java (expanded paths)"]
JavaFound{Any Java runtime found?}
JavaSelect["User selects a detected Java version"]
JavaInstall["User triggers one-click Java installation"]
NameServer["Name server and confirm parameters"]
EULA["Accept Minecraft EULA on first launch"]
Done["Server created and ready to start"]
Start --> ChoiceSource
ChoiceSource --> JAR
ChoiceSource --> ExistingDir
ChoiceSource --> Script
JAR --> Detect
ExistingDir --> Detect
Script --> Detect
Detect --> DetectOK
DetectOK -->|Yes| Modpack
DetectOK -->|No| CustomMode --> CustomCmd --> Modpack
Modpack --> JavaScan
JavaScan --> JavaFound
JavaFound -->|Yes| JavaSelect --> NameServer
JavaFound -->|No| JavaInstall --> JavaSelect --> NameServer
NameServer --> EULA --> Done
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Hey - 我这边发现了 3 个问题,并提供了一些整体性反馈:
- 在
structure页面(en/structure.md和zh-tw/structure.md)中,由于在链接前少了一个关闭的 ```,[Detailed Directory Structure]链接被包含在代码块里了;请把这个链接移动到代码块外面,以便它能作为普通链接正确渲染。 - 简体中文的
zh/structure.md现在不再包含指向完整结构页(现在在/zh/structure-full)的链接,而英文和繁体中文版本都有;建议也加上一个类似的链接以保持一致性。 - 你把
RELEASE_BASE改成了使用.../download/v${VERSION},但旧的变更日志链接仍然指向诸如sea-lantern-v0.6.5这样的 tag;请仔细确认新的基础 URL 以及所有 tag/制品名称(包括重命名后的 Arch 包)在各个版本上都与 GitHub 实际的 Release 命名约定一致。
给 AI 代理的提示
Please address the comments from this code review:
## Overall Comments
- 在 `structure` 页面(`en/structure.md` 和 `zh-tw/structure.md`)中,由于在链接前少了一个关闭的 ```,`[Detailed Directory Structure]` 链接被包含在代码块里了;请把这个链接移动到代码块外面,以便它能作为普通链接正确渲染。
- 简体中文的 `zh/structure.md` 现在不再包含指向完整结构页(现在在 `/zh/structure-full`)的链接,而英文和繁体中文版本都有;建议也加上一个类似的链接以保持一致性。
- 你把 `RELEASE_BASE` 改成了使用 `.../download/v${VERSION}`,但旧的变更日志链接仍然指向诸如 `sea-lantern-v0.6.5` 这样的 tag;请仔细确认新的基础 URL 以及所有 tag/制品名称(包括重命名后的 Arch 包)在各个版本上都与 GitHub 实际的 Release 命名约定一致。
## Individual Comments
### Comment 1
<location path="en/download.md" line_range="35-36" />
<code_context>
|--------|-------------|
| <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_aarch64.dmg`">DMG (Apple Silicon)</a> | M1 / M2 / M3 / M4 |
| <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_x64.dmg`">DMG (Intel)</a> | x64 architecture |
+| <a :href="`${RELEASE_BASE}/Sea.Lantern_aarch64.app.tar.gz`">app.tar.gz (Apple Silicon)</a> | Portable archive |
+| <a :href="`${RELEASE_BASE}/Sea.Lantern_x64.app.tar.gz`">app.tar.gz (Intel)</a> | Portable archive |
## Linux
</code_context>
<issue_to_address>
**issue (bug_risk):** macOS app.tar.gz 下载链接的文件名中似乎缺少 VERSION 占位符。
这两个 `app.tar.gz` 链接是这里唯一没有在文件名中包含 `${VERSION}` 的 macOS 制品。如果实际的 Release 文件是带版本号的,这些 URL 应该更新为(例如 `Sea.Lantern_${VERSION}_aarch64.app.tar.gz` 和 `Sea.Lantern_${VERSION}_x64.app.tar.gz`),以与现有命名方案保持一致并避免链接失效。
</issue_to_address>
### Comment 2
<location path="zh-tw/download.md" line_range="35-36" />
<code_context>
|------|------|
| <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_aarch64.dmg`">DMG (Apple Silicon)</a> | M1 / M2 / M3 / M4 |
| <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_x64.dmg`">DMG (Intel)</a> | x64 架構 |
+| <a :href="`${RELEASE_BASE}/Sea.Lantern_aarch64.app.tar.gz`">app.tar.gz (Apple Silicon)</a> | 可攜壓縮包 |
+| <a :href="`${RELEASE_BASE}/Sea.Lantern_x64.app.tar.gz`">app.tar.gz (Intel)</a> | 可攜壓縮包 |
## Linux
</code_context>
<issue_to_address>
**issue (bug_risk):** macOS app.tar.gz 下載連結似乎缺少 VERSION 參數。
同表中其他安裝包檔名都有 `${VERSION}`,但這兩個連結沒有。如果實際檔名是帶版本號的,建議改為 `Sea.Lantern_${VERSION}_aarch64.app.tar.gz` 與 `Sea.Lantern_${VERSION}_x64.app.tar.gz`,避免下載連結對不上檔名。
</issue_to_address>
### Comment 3
<location path="zh/download.md" line_range="35-36" />
<code_context>
|------|------|
| <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_aarch64.dmg`">DMG (Apple Silicon)</a> | M1 / M2 / M3 / M4 |
| <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_x64.dmg`">DMG (Intel)</a> | x64 架构 |
+| <a :href="`${RELEASE_BASE}/Sea.Lantern_aarch64.app.tar.gz`">app.tar.gz (Apple Silicon)</a> | 便携压缩包 |
+| <a :href="`${RELEASE_BASE}/Sea.Lantern_x64.app.tar.gz`">app.tar.gz (Intel)</a> | 便携压缩包 |
## Linux
</code_context>
<issue_to_address>
**issue (bug_risk):** macOS app.tar.gz 下载链接似乎少了 VERSION 占位符。
其他下载链接的文件名都包含 `${VERSION}`,而这两条没有。如果实际产物名也是带版本号的,建议统一为 `Sea.Lantern_${VERSION}_aarch64.app.tar.gz` 和 `Sea.Lantern_${VERSION}_x64.app.tar.gz`,以避免生成指向不存在文件的链接。
</issue_to_address>帮我变得更有用!请在每条评论上点 👍 或 👎,我会根据你的反馈改进后续评审。
Original comment in English
Hey - I've found 3 issues, and left some high level feedback:
- In the
structurepages (en/structure.mdandzh-tw/structure.md), the[Detailed Directory Structure]link is inside the fenced code block due to the missing closing ``` before it; move the link outside the code block so it renders as a normal link. - The Chinese
zh/structure.mdno longer contains a link to the full structure page (now at/zh/structure-full), unlike the English and Traditional Chinese versions; consider adding a similar link for consistency. - You changed
RELEASE_BASEto use.../download/v${VERSION}while older changelog links still point to tags likesea-lantern-v0.6.5; double-check that the new base URL and all tag/asset names (including the renamed Arch package) match the actual GitHub release naming convention across versions.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- In the `structure` pages (`en/structure.md` and `zh-tw/structure.md`), the `[Detailed Directory Structure]` link is inside the fenced code block due to the missing closing ``` before it; move the link outside the code block so it renders as a normal link.
- The Chinese `zh/structure.md` no longer contains a link to the full structure page (now at `/zh/structure-full`), unlike the English and Traditional Chinese versions; consider adding a similar link for consistency.
- You changed `RELEASE_BASE` to use `.../download/v${VERSION}` while older changelog links still point to tags like `sea-lantern-v0.6.5`; double-check that the new base URL and all tag/asset names (including the renamed Arch package) match the actual GitHub release naming convention across versions.
## Individual Comments
### Comment 1
<location path="en/download.md" line_range="35-36" />
<code_context>
|--------|-------------|
| <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_aarch64.dmg`">DMG (Apple Silicon)</a> | M1 / M2 / M3 / M4 |
| <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_x64.dmg`">DMG (Intel)</a> | x64 architecture |
+| <a :href="`${RELEASE_BASE}/Sea.Lantern_aarch64.app.tar.gz`">app.tar.gz (Apple Silicon)</a> | Portable archive |
+| <a :href="`${RELEASE_BASE}/Sea.Lantern_x64.app.tar.gz`">app.tar.gz (Intel)</a> | Portable archive |
## Linux
</code_context>
<issue_to_address>
**issue (bug_risk):** The macOS app.tar.gz download links appear to be missing the VERSION placeholder in the filenames.
These two `app.tar.gz` links are the only macOS artifacts here that don’t include `${VERSION}` in the filename. If the actual release files are versioned, these URLs should be updated (e.g. `Sea.Lantern_${VERSION}_aarch64.app.tar.gz` and `Sea.Lantern_${VERSION}_x64.app.tar.gz`) to match the existing naming scheme and avoid broken links.
</issue_to_address>
### Comment 2
<location path="zh-tw/download.md" line_range="35-36" />
<code_context>
|------|------|
| <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_aarch64.dmg`">DMG (Apple Silicon)</a> | M1 / M2 / M3 / M4 |
| <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_x64.dmg`">DMG (Intel)</a> | x64 架構 |
+| <a :href="`${RELEASE_BASE}/Sea.Lantern_aarch64.app.tar.gz`">app.tar.gz (Apple Silicon)</a> | 可攜壓縮包 |
+| <a :href="`${RELEASE_BASE}/Sea.Lantern_x64.app.tar.gz`">app.tar.gz (Intel)</a> | 可攜壓縮包 |
## Linux
</code_context>
<issue_to_address>
**issue (bug_risk):** macOS app.tar.gz 下載連結似乎缺少 VERSION 參數。
同表中其他安裝包檔名都有 `${VERSION}`,但這兩個連結沒有。如果實際檔名是帶版本號的,建議改為 `Sea.Lantern_${VERSION}_aarch64.app.tar.gz` 與 `Sea.Lantern_${VERSION}_x64.app.tar.gz`,避免下載連結對不上檔名。
</issue_to_address>
### Comment 3
<location path="zh/download.md" line_range="35-36" />
<code_context>
|------|------|
| <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_aarch64.dmg`">DMG (Apple Silicon)</a> | M1 / M2 / M3 / M4 |
| <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_x64.dmg`">DMG (Intel)</a> | x64 架构 |
+| <a :href="`${RELEASE_BASE}/Sea.Lantern_aarch64.app.tar.gz`">app.tar.gz (Apple Silicon)</a> | 便携压缩包 |
+| <a :href="`${RELEASE_BASE}/Sea.Lantern_x64.app.tar.gz`">app.tar.gz (Intel)</a> | 便携压缩包 |
## Linux
</code_context>
<issue_to_address>
**issue (bug_risk):** macOS app.tar.gz 下载链接似乎少了 VERSION 占位符。
其他下载链接的文件名都包含 `${VERSION}`,而这两条没有。如果实际产物名也是带版本号的,建议统一为 `Sea.Lantern_${VERSION}_aarch64.app.tar.gz` 和 `Sea.Lantern_${VERSION}_x64.app.tar.gz`,以避免生成指向不存在文件的链接。
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
There was a problem hiding this comment.
Pull request overview
This pull request synchronizes the documentation site with the v1.0.0 release of Sea Lantern. The PR updates version references, adds comprehensive v1.0.0 changelog entries, creates detailed structure documentation files, and updates feature descriptions across all language versions (Chinese Simplified, Traditional Chinese, and English).
Changes:
- Version bump from 0.6.5 to 1.0.0 with updated release URL pattern
- Added v1.0.0 changelog with highlights including enhanced server creation workflow, plugin system improvements, and ARM64 architecture support
- Created new detailed directory structure documentation (
structure-full.md) for all languages - Updated tutorial, getting-started, features, and intro pages to reflect new v1.0.0 capabilities including import sources, startup detection, and custom commands
- Enhanced download pages with ARM64 package links for Windows and Linux, plus macOS portable archives
- Reorganized sidebar navigation by moving "Project Structure" from Developer section to Project Info section
Reviewed changes
Copilot reviewed 32 out of 32 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
.vitepress/version.ts |
Updated version to 1.0.0 and corrected release URL pattern |
zh/changelog.md, zh-tw/changelog.md, en/changelog.md |
Added comprehensive v1.0.0 release notes with feature highlights and stability improvements |
zh/structure-full.md, zh-tw/structure-full.md, en/structure-full.md |
New detailed directory structure documentation based on v1.0.0 |
zh/structure.md, zh-tw/structure.md, en/structure.md |
Added v1.0.0 structure sync section and link to detailed docs |
zh/tutorial.md, zh-tw/tutorial.md, en/tutorial.md |
Updated server creation section to reflect new import sources and startup detection |
zh/getting-started.md, zh-tw/getting-started.md, en/getting-started.md |
Revised server creation steps to include new workflow options |
zh/features.md, zh-tw/features.md, en/features.md |
Added new v1.0.0 features including plugin market, expanded Java detection, and enhanced creation flow |
zh/download.md, zh-tw/download.md, en/download.md |
Added ARM64 packages and macOS portable archives |
zh/intro.md, zh-tw/intro.md, en/intro.md |
Updated feature list with Creation Flow 2.0 and removed System Tray item |
zh/server-jar.md, zh-tw/server-jar.md, en/server-jar.md |
Updated usage instructions to reflect new import capabilities |
.vitepress/config/zh.ts, .vitepress/config/zh-tw.ts, .vitepress/config/en.ts |
Moved Project Structure link from Developer to Project Info section |
STRUCTURE.md |
Added v1.0.0 structure sync section |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| | <a :href="`${RELEASE_BASE}/Sea.Lantern_aarch64.app.tar.gz`">app.tar.gz (Apple Silicon)</a> | 可攜壓縮包 | | ||
| | <a :href="`${RELEASE_BASE}/Sea.Lantern_x64.app.tar.gz`">app.tar.gz (Intel)</a> | 可攜壓縮包 | |
There was a problem hiding this comment.
The macOS app.tar.gz download links are missing the version number in the filename, unlike all other download formats (DMG, DEB, RPM, etc.). The URLs should be Sea.Lantern_${VERSION}_aarch64.app.tar.gz and Sea.Lantern_${VERSION}_x64.app.tar.gz to maintain consistency with other release assets and prevent issues when multiple versions are hosted simultaneously.
| | <a :href="`${RELEASE_BASE}/Sea.Lantern_aarch64.app.tar.gz`">app.tar.gz (Apple Silicon)</a> | 可攜壓縮包 | | |
| | <a :href="`${RELEASE_BASE}/Sea.Lantern_x64.app.tar.gz`">app.tar.gz (Intel)</a> | 可攜壓縮包 | | |
| | <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_aarch64.app.tar.gz`">app.tar.gz (Apple Silicon)</a> | 可攜壓縮包 | | |
| | <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_x64.app.tar.gz`">app.tar.gz (Intel)</a> | 可攜壓縮包 | |
| | <a :href="`${RELEASE_BASE}/Sea.Lantern_aarch64.app.tar.gz`">app.tar.gz (Apple Silicon)</a> | Portable archive | | ||
| | <a :href="`${RELEASE_BASE}/Sea.Lantern_x64.app.tar.gz`">app.tar.gz (Intel)</a> | Portable archive | |
There was a problem hiding this comment.
The macOS app.tar.gz download links are missing the version number in the filename, unlike all other download formats (DMG, DEB, RPM, etc.). The URLs should be Sea.Lantern_${VERSION}_aarch64.app.tar.gz and Sea.Lantern_${VERSION}_x64.app.tar.gz to maintain consistency with other release assets and prevent issues when multiple versions are hosted simultaneously.
| | <a :href="`${RELEASE_BASE}/Sea.Lantern_aarch64.app.tar.gz`">app.tar.gz (Apple Silicon)</a> | Portable archive | | |
| | <a :href="`${RELEASE_BASE}/Sea.Lantern_x64.app.tar.gz`">app.tar.gz (Intel)</a> | Portable archive | | |
| | <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_aarch64.app.tar.gz`">app.tar.gz (Apple Silicon)</a> | Portable archive | | |
| | <a :href="`${RELEASE_BASE}/Sea.Lantern_${VERSION}_x64.app.tar.gz`">app.tar.gz (Intel)</a> | Portable archive | |
| 2. 在 Sea Lantern 中点击「创建服务器」 | ||
| 3. 若是 `.jar`,直接导入 JAR;若是可执行文件,请用脚本启动模式(`bat` / `sh`) | ||
| 4. 详细步骤请参考 [快速开始](/zh/getting-started) | ||
| 2. 在 Sea Lantern 中点击「创建服务器」,选择导入来源(JAR / 既有服务器 / 启动脚本) |
There was a problem hiding this comment.
Terminology inconsistency: this file uses "既有服务器" while other Chinese documentation files (e.g., zh/tutorial.md, zh/getting-started.md) consistently use "已有服务器" for "existing server". For consistency across the documentation, consider using "已有服务器" here as well.
| 2. 在 Sea Lantern 中点击「创建服务器」,选择导入来源(JAR / 既有服务器 / 启动脚本) | |
| 2. 在 Sea Lantern 中点击「创建服务器」,选择导入来源(JAR / 已有服务器 / 启动脚本) |
| ``` | ||
|
|
||
| [詳細目錄結構](/zh-tw/structure-full) |
There was a problem hiding this comment.
The link to the detailed structure is placed inside the code block, which will render it as plain text rather than a clickable link. The link should be placed before the code block starts (before line 22), similar to how it's done in the zh/structure.md file where the link appears after the closing triple backticks on line 54.
| ``` | ||
|
|
||
| [Detailed Directory Structure](/en/structure-full) |
There was a problem hiding this comment.
The link to the detailed structure is placed inside the code block, which will render it as plain text rather than a clickable link. The link should be placed before the code block starts (before line 22), similar to how it's done in the zh/structure.md file where the link appears after the closing triple backticks on line 54.
Summary by Sourcery
将文档站点与 Sea Lantern v1.0.0 版本同步,包括更新的功能、下载内容以及项目结构参考。
Documentation:
Original summary in English
Summary by Sourcery
Sync documentation site with the Sea Lantern v1.0.0 release, including updated features, downloads, and project structure references.
Documentation: