Repository navigation
Generate the clusters data from the Google Doc, with no hand edits - #984
Conversation
…s note The Google Doc's formatting had drifted: the parser found no Cluster 11 sub-clusters and read two citations as headings. It also published an editor's note at the start of Cluster 10's description. Fixes #978 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
👍 All image files/references (if any) are in webp format, in line with our policy. |
✅ Spell Check PassedNo spelling issues found when checking 9 changed file(s)! 🎉 |
|
✅ Staging Deployment Status This PR has been successfully deployed to staging as part of an aggregated deployment. Deployed at: 2026-11-04 17:38:37 UTC The staging site shows the combined state of all compatible open PRs. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
All reported issues were addressed across 4 files
Reply with feedback, questions, or to request a fix.
View guided diff | Turn on auto-fix | Re-trigger cubic
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sub-cluster names repeat across clusters, so grouping references by name alone gave both "Reflexivity and positionality" sections the same combined list. The export now groups them by cluster as well. Citations returned by doi.org lose stray whitespace, the "Portico" publisher, capitalised surnames and titles cut off at a line break. Moves the stated-count test from #980 here and runs the cluster tests on relevant PRs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
data/clusters_v4.json and the cluster pages now come from the generator, with no hand edits. The earlier link, DOI and count corrections were made in the doc. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
LukasWallrich
changed the title
There was a problem hiding this comment.
All reported issues were addressed across 8 files (changes from recent commits).
Reply with feedback, questions, or to request a fix.
View guided diff | Turn on auto-fix | Re-trigger cubic
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>
data/clusters_v4.jsonnow comes straight from the Clusters v4.1 Google Doc, with no hand edits. Before this change, re-running the parser would have emptied Cluster 11, added false sub-clusters and undone earlier hand fixes.Parser fixes
Corrections made in the Google Doc
What visitors will notice
Keeping it this way:
CONTRIBUTING.mdand the parser's docstring now say not to edit the generated files by hand. A new workflow runs the parser tests and the count test (moved from #980) on PRs that touch this data. It can't detect a hand edit that passes those tests, so that part is a rule, not a check.Verified: the output comes from running the parser against the live doc, using the local DOI cache. All 11 stated counts match, where a cluster states one. The cluster tests pass, a local build (Hugo 0.164) succeeds, and
check_seo_html.pyexits cleanly.Timing:
data/clusters_v4.jsonis in the data artifact, so the new text reaches forrt.org after the next data-processing run onmain.Fixes #978
Fixes #964
🤖 Generated with Claude Code