Rewrite homepage "Achievements & Awards" as a genuine Impact section
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
- Issue 類型
- 文件
- 描述清晰度
- 基本清楚
- 活躍度
- 冷清
- 領域
- content
研究方向
從 content/home/5-achievements.md 開始，並比較現有的 /awards 和 /impact 頁面，以了解它們各自的範圍和命名。決定首頁區段的資訊架構，接著圍繞具體的組織成果重新撰寫，移除重複的獎項內容，並決定哪些里程碑統計數據應作為輔助證據保留。
由索引模型根據 Issue 內容生成。
描述
Problem
The homepage's content/home/5-achievements.md section (just rebuilt visually in #814, replacing a yearly-regenerated infographic image with a CSS-based list) still carries its old content, which is a mix of:
- Vanity/activity metrics — social followers, Slack members, subscriber counts, contributor counts.
- A bulleted list of awards FORRT has received (Dorothy Bishop Prize, OSC Award, Open Scholarship Prize), which duplicates
/awards.
None of this actually answers "what has FORRT changed?" — e.g. how many educators have adopted FORRT materials, what policy/institutional change the policy briefings drove, what's shifted in teaching practice as a result of the Educational NEXUS, etc. That's a genuine impact narrative, and it's currently missing.
Naming collision to resolve deliberately
"Impact" is already used for two other, unrelated things on the site:
/awards— page titled "Awards & Impact"./impact(nav: Educational NEXUS → "Impact of OS on students") — a specific published review (Pownall et al., 2023, Royal Society Open Science) on the evidence for teaching open/reproducible scholarship, unrelated to FORRT's own organizational impact.
If the homepage section becomes "Impact", we'd have three differently-scoped "Impact" surfaces. Whoever picks this up should decide the IA explicitly (e.g. rename/merge one of the existing pages, or pick a distinct label for the homepage section) rather than adding a fourth ad-hoc meaning.
Proposal
- Decide what "impact" means for the homepage section and how it relates to
/awardsand/impact(rename, merge, or clearly differentiate labels/scope). - Rewrite the copy to lead with concrete outcomes (reach, adoption, institutional/policy influence, evidence of behavior change) rather than follower/member counts.
- Move the awards bullet list to live solely on
/awards(linked from the homepage, not duplicated). - Decide whether any of the current milestone stats (Slack members, newsletter subscribers, contributors, projects, partnerships) still belong in this section as supporting evidence, or should move/shrink.
This is primarily a content/messaging decision — implementation (the CSS-based milestones list from #814) can be reused once the copy and structure are agreed.
Raised while rebuilding the homepage Achievements & Awards section (#814).
- 主要語言
- HTML
- 星號
- 42
- 分支
- 33
- 平均合併
- 16 小時 3 分鐘
- 30 天內合併 PR
- 121
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
forrtproject/forrtproject.github.io 的其他 Issue
-
難度 1/5 1 小時以內 新手友好度 90/100
forrtproject/forrtproject.github.io#1035 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
forrtproject/forrtproject.github.io#987 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
forrtproject/forrtproject.github.io#977 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 90/100
forrtproject/forrtproject.github.io#947 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 66/100
forrtproject/forrtproject.github.io#933 · 1 則留言 ·
維護者通常 1 天內回覆
查看 forrtproject/forrtproject.github.io 的全部 Issue
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 74/100
lukasz-madon/awesome-remote-job#1242 ·
-
難度 1/5 1 小時以內 新手友好度 88/100
akitaonrails/ai-book-2026#13 ·
-
難度 1/5 1 小時以內 新手友好度 76/100
-
難度 1/5 1 小時以內 新手友好度 85/100
-
approved check:passed streams:add
難度 1/5 1 小時以內 新手友好度 72/100
維護者通常 1 天內回覆