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

Collect documentation for standard GH-pages components

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
文档
描述清晰度
需要澄清
活跃度
停滞
技术栈
github, ruby, sass
领域
documentation

调研方向

该 issue 没有列出任何文件、测试或入口点。首先检查 #651 中的兼容性问题,以及受支持的 Jekyll、Liquid 和 Sass 版本;当一个维护中的网站收集了 GitHub Pages 支持的版本和工具的文档时,即视为完成。

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

描述

I understand the reasons outlined in #651 for not automatically upgrading to Jekyll 4.0 along with all the consequent dependencies, among them Liquid and Sass. The problem now is that as all of these projects continue to evolve, it becomes harder and harder to learn what capabilities are natively supported by GH-pages—one has to dig extra hard into any part of the the documentation to discover whether any particular claim is true for a GH-pages site. Consequently, GH-pages becomes harder and harder to use. Ease-of-use is one of the things that has made GH-pages so incredibly popular and powerful over the years, so not paying attention to the erosion of this quality is a threat to the system's continued relevance.

Personally I would prefer if GH would avoid breaking old websites by adding a "legacy jekyll" checkbox to repository configuration—frankly it seems easier than what I'm about to suggest—but failing that, I'd like to see GitHub maintain a site that collects all the documentation for versions of jekyll and the tools on which it's built that are actually supported.

Thanks for your attention.

主要语言
Ruby
星标
1.9k
派生
361
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

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

github/pages-gem 的其他 Issue

查看 github/pages-gem 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

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