Make curated-resource browsing incremental and crawlable

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

维护者通常 1 天内回复

@richarddushime 已经在做这个了。

开始于 2026年8月25日。

评估

这个 Issue 还没有评估数据。

描述

enhancement new website

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.

Reference: https://developers.google.com/search/docs/specialty/ecommerce/pagination-and-incremental-page-loading

主要语言
HTML
星标
42
派生
33
平均合并
17 小时 18 分钟
30 天内合并 PR
111

环境准备

从这里开始

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

forrtproject/forrtproject.github.io 的其他 Issue

查看 forrtproject/forrtproject.github.io 的全部 Issue

把新 issue 发到你的邮箱

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