Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Add RH answers page?

未关闭
#531 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
停滞
技术栈
html
领域
documentation

调研方向

首先查看 clojure.org 上现有的指南和 FAQ，然后将拟议内容与链接的 gist 进行比较。确定页面结构，并整理答案，使每个答案都能在可能的情况下得到清晰的引用、日期标注和来源链接；完成的标准是 RH 答案拥有一个专门且包含上下文的页面，而不是并入 FAQ。

由索引模型根据 Issue 内容生成。

描述

content help wanted

Add a page similar to https://gist.github.com/reborg/dc8b0c96c397a56668905e2767fd697f to the guides. These are all quotes from Rich, so there is no problem here in migrating this content.

One thing I would like to do better is to contextualize these answers. In general, these are useful things to surface (we may need to do a bit of curation and review by Rich), but it's important for readers to understand that they are answers at a point in time. As such, they should clearly be quotes, and they should be visibly anchored to the time the answer was given, and whenever possible, a link or reference to the source, which often can provide further context. In some cases, there are useful follow-up links into the FAQ or other places on the site.

One open question is whether this should actually be integrated into https://clojure.org/guides/faq instead. My current thinking is no - while there is overlap, the framing and intent is different and they are both independently useful.

主要语言
HTML
星标
259
派生
275
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

clojure/clojure-site 的其他 Issue

查看 clojure/clojure-site 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。