Make curated-resource browsing incremental and crawlable
Los mantenedores suelen responder en 1 día
@richarddushime ya está trabajando en esto.
Desde el 25/8/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Context and corrected finding
The audit claimed that /curated_resources/page/2/ through /page/136/ form a 136-click sequence. That exact claim does not reproduce against the current deployment: /resources/ is the canonical landing page, /resources/page/2/ returns 404, and the current landing page is a roughly 3.8 MB headless page that renders the full resource collection with client-side filtering.
The underlying concern is still valid: visitors receive a very large initial document, and the resource collection does not have a server-rendered, crawlable browse structure by type, education level, subject, or language.
Requested change
- Replace the all-resources client-rendered monolith with an incremental, server-rendered browse experience.
- Provide crawlable links to stable subsets (for example, numbered pages or carefully selected taxonomy landing pages).
- Keep individual resource URLs stable.
- Do not create indexable combinations for every arbitrary filter; use canonical/noindex rules for filter variants where appropriate.
- Ensure each subset has useful title/description metadata and ordinary links to its resource pages.
Acceptance criteria
- Initial HTML is materially smaller than the current
/resources/response. - A crawler without executing filter JavaScript can discover all resource pages through links and/or the sitemap.
- Keyboard users can browse and filter the collection without losing access to results.
- Representative subsets have unique canonical URLs and no duplicate-content explosion.
- 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