Files
hello-algo/docs/chapter_appendix/contribution.md
T
Yudong JinandClaude Opus 5.5 82da772c48 Retire the Docker MkDocs preview and dead MkDocs-only config (#2027)
* Name the current generator in the hero paint-seam header

The workspace generator moved from utils.hero.fit_paint_seams to
utils.site.homepage.art.fit_paint_seams; the seam metadata is unchanged.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

* Sync the homepages to the new installer version

The workspace homepage installer now imports its roots from
utils.core.paths; its own bytes feed the homepage version, so the six
homepages point at assets/home/bf55006c61fda74c. Content is unchanged.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

* Retire the Docker MkDocs preview and dead MkDocs-only config

The site is built only with Zensical. The root Dockerfile and compose file built a
MkDocs Material + glightbox preview that nothing else used, so remove them and the
"Docker deployment" section of the contribution guide in all six languages.

In mkdocs.yml, drop the keys the Zensical build never reads: glightbox (filtered
out by the builder), theme.features, extra_css and extra_javascript (replaced by
overrides/zensical/zensical.toml), and docs_dir, site_dir and theme.custom_dir (set
by the builder). The effective Zensical config is byte-identical for every language.

codes/Dockerfile (the code runtime environment) is unrelated and kept.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

* Remove the unused KaTeX script and the shadowed extra.css

overrides/javascripts/katex.js is referenced by no page or config (MathJax renders
formulas) and was only published as a dead file. overrides/stylesheets/extra.css is
always replaced by overrides/zensical/stylesheets/extra.css during the build.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

---------

Co-authored-by: Claude Opus 5.5 <[email protected]>
2026-11-10 14:41:25 +08:00

2.1 KiB

一起参与创作

由于笔者能力有限,书中难免存在一些遗漏和错误,请您谅解。如果您发现了笔误、链接失效、内容缺失、文字歧义、解释不清晰或行文结构不合理等问题,请协助我们进行修正,以给读者提供更优质的学习资源。

所有撰稿人的 GitHub ID 将在本书仓库、网页版和 PDF 版的主页上进行展示,以感谢他们对开源社区的无私奉献。

!!! success "开源的魅力"

纸质图书的两次印刷的间隔时间往往较久,内容更新非常不方便。

而在本开源书中,内容更迭的时间被缩短至数日甚至几个小时。

内容微调

如下图所示,每个页面的右上角都有“编辑图标”。您可以按照以下步骤修改文本或代码。

  1. 点击“编辑图标”,如果遇到“需要 Fork 此仓库”的提示,请同意该操作。
  2. 修改 Markdown 源文件内容,检查内容的正确性,并尽量保持排版格式的统一。
  3. 在页面底部填写修改说明,然后点击“Propose file change”按钮。页面跳转后,点击“Create pull request”按钮即可发起拉取请求。

页面编辑按键

图片无法直接修改,需要通过新建 Issue 或评论留言来描述问题,我们会尽快重新绘制并替换图片。

内容创作

如果您有兴趣参与此开源项目,包括将代码翻译成其他编程语言、扩展文章内容等,那么需要实施以下 Pull Request 工作流程。

  1. 登录 GitHub ,将本书的代码仓库 Fork 到个人账号下。
  2. 进入您的 Fork 仓库网页,使用 git clone 命令将仓库克隆至本地。
  3. 在本地进行内容创作,并进行完整测试,验证代码的正确性。
  4. 将本地所做更改 Commit ,然后 Push 至远程仓库。
  5. 刷新仓库网页,点击“Create pull request”按钮即可发起拉取请求。