Remaining pages with several <h1> (content headings, empty h1 on /coc/ and /manuscript/)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 55/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- html, markdown, python
- 领域
- accessibility, content, testing
调研方向
Start with the report-only section of scripts/check_seo_html.py and inspect the listed page sources. Check the templates or widgets for empty h1 elements, the PDF embed on /cv/, and scripts/generate_sc_profiles.py; demote content headings as described and confirm their styling remains consistent. Done means the report lists no pages with multiple h1 elements and the check is promoted to a hard failure.
由索引模型根据 Issue 内容生成。
描述
Problem
After #882, 13 pages still have more than one <h1> (build of main, 2026-10-28; scripts/check_seo_html.py lists them in its report-only section). #882 deliberately left these out because most come from # headings in content files rather than from templates. #860 is closed.
/about/mission/: 2 h1 — "Mission"; "Mission Statement"/citation-politics/: 5 h1 — "Towards Citational Justice"; "Overview"; "Toolkit"; "Coming Up"; "Get involved!"/coc/: 2 h1 — ""; "Code of Conduct"/cv/: 2 h1 — "FORRT CV"; "This browser does not support PDFs. Please downloa"/educators-corner/002-transparencychecklist-balazsaczel/: 2 h1 — "Using the 'Transparency Checklist Guidelines&#"; "Transparency Checklist Guideline for Education"/manuscript/: 2 h1 — "Manuscript"; ""/neurodiversity/: 5 h1 — "Neurodiversity"; "Our Goals"; "What We’re About"; "Our Resources"; "About the Team"/nexus/: 2 h1 — "Nexus"; "FORRT’s Educational Nexus"/publications/: 8 h1 — "Publications"; "Academic peer-reviewed publications"; "Preprints"; "Op-Eds and Other Media"; "Policy Briefs"; "FORRT affiliated projects"; "Work in Progress"; "Find More About Ongoing Projects"/reversals/: 2 h1 — "Replications & Reversals"; "All Effects (sorted by discipline)"/summaries/: 2 h1 — "FORRT Summaries"; "100+ Summaries of Open and Reproducible Science Li"/testimonials/: 9 h1 — "Testimonials"; "FORRT Community Stories & Testimonials"; "Finding Belonging in Open Science"; "My Journey into Replications, Reproducibility, and"; "On Supportive Mentorship and Personal and Professi"; "Learning, Contributing, Belonging: My Experience w"; "Choosing Humanity: Why FORRT Feels Like Home"; "Doing Good Research, Together: Growing with FORRT"; "From Brazil to the world: How a seemingly ‘s"/about/steering-committee/: 2 h1 — "Steering Committee"; "Steering Committee"
Notes for fixing
- Empty
h1on/coc/and/manuscript/: this looks like a template or widget issue, not content. Check those first. /cv/: the PDF embed's fallback text ("This browser does not support PDFs…") is rendered as anh1./about/steering-committee/is generated byscripts/generate_sc_profiles.py, so demote the heading there rather than in the Markdown.- The rest (
/publications/,/testimonials/,/neurodiversity/,/citation-politics/, …): demote the content-level#headings to##. Check that styling stays the same. - Once the list is empty, promote the "several
<h1>" report incheck_seo_html.pyto a hard check.
- 主要语言
- HTML
- 星标
- 42
- 派生
- 33
- 平均合并
- 17 小时 18 分钟
- 30 天内合并 PR
- 111
环境准备
- 没有 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 天内回复
查看 forrtproject/forrtproject.github.io 的全部 Issue
相似的 Issue
-
accessibility good first issue
难度 2/5 1-3 小时 新手友好度 84/100
-
难度 2/5 1-3 小时 新手友好度 67/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复
-
area/accessibility component/storefront domain/discovery Platform(Default)
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复