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

Create a way to display and manage content freshness

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

还没有人认领这个 Issue。

评估

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

调研方向

未指定文件、测试或入口点。先审阅链接的 issue nodejs/nodejs.org#7197 和 #7294，然后明确范围是更新元数据、人工审查日期、版本指示器，还是关于过时内容的自动化 issue。完成条件应包括一份达成共识的设计，以及明确的审查或内容新鲜度工作流。

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

描述

Broken out of https://github.com/nodejs/nodejs.org/issues/7197

Add metadata on pages to display last update (git has this info of course)

  • we noted a distinction between last reviewed (by a human) and last updated
  • eventually, create a means to flag when content gets stale, perhaps via an action that opens issues, if one exists

@AugustinMauroy had these thoughts

I'm more in favour of the version used in the example. Because a date has no value in relation to the runtime. In addition, having the version allows the contributor/collaborator to know if a document needs to be revised.
And from a functional point of view, I think we should add a bit to the MetaBar that allows you to install (redirect to the installation of the correct version).

This is interesting, but would create LTS rollover moments where we have all to review all content. I think that would quickly become the norm, twice a year.
I suppose that's better than arbitrary dates, TBH.

Given that thought experiment, maybe we build on nodejs/nodejs.org#7294 and build something that asks the owners to review the content twice a year?

主要语言
JavaScript
星标
29
派生
165
平均合并
1 天 18 小时
30 天内合并 PR
2

贡献指南

打开贡献指南

从这里开始

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

nodejs/learn 的其他 Issue

查看 nodejs/learn 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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