Remaining pages with several <h1> (content headings, empty h1 on /coc/ and /manuscript/)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 55/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- html, markdown, python
- Área
- accessibility, content, testing
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- HTML
- Estrellas
- 42
- Forks
- 33
- Merge medio
- 17 h 18 min
- PR fusionados (30 d)
- 111
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de forrtproject/forrtproject.github.io
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
forrtproject/forrtproject.github.io#1035 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
forrtproject/forrtproject.github.io#987 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
forrtproject/forrtproject.github.io#977 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
forrtproject/forrtproject.github.io#947 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
forrtproject/forrtproject.github.io#933 ·
Los mantenedores suelen responder en 1 día
Todos los issues de forrtproject/forrtproject.github.io
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 2 días
-
area/accessibility component/storefront domain/discovery Platform(Default)
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
Sidebar user block: drop the separate log-out button; the chevron becomes a log-out icon buttonAbiertoui
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día