school_compare

763 Commits 91 Branches 0 Tags

2 Commits

Include renames

Author	SHA1	Message	Date
TudorandClaude Opus 5	8967966eef	feat(places): list schools alphabetically on place pages PR Checks / Frontend Typecheck + Tests (pull_request) Successful in 1m2s Details PR Checks / Backend Smoke (pull_request) Successful in 8s Details PR Checks / Build Backend (no push) (pull_request) Successful in 16s Details PR Checks / Build Frontend (no push) (pull_request) Successful in 44s Details PR Checks / Build Pipeline (no push) (pull_request) Successful in 11s Details PR Checks / AI Code Review (Claude) (pull_request) Canceled after 1m21s Details Someone on a place page is usually looking for a school they can name, so the order should serve scanning for it rather than ranking. /api/rankings keeps its league-table ordering; this is a place-page decision, not a site-wide one. Sorted case-insensitively, or a capitalised name would sort ahead of every lowercase one. The change made five pieces of copy untrue, so they go with it. The phase variant titled itself "— Ranked", and all four route families described themselves as "ranked by SATs and GCSE results". A page that opens by claiming an order it does not keep is worse than one that claims nothing. The ItemList markup carried `position` with no declared order, which reads as a ranking. It now declares ItemListOrderAscending, so the structured data says what the table does. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015mWQnpye9F299NVRCCSRvj	2026-08-22 00:09:58 +01:00
TudorandClaude Opus 5	c5af476213	feat(places): /api/places registry and place detail endpoints The registry is cached for the process and reset by the same admin endpoint that rebuilds the sitemaps, so places and sitemap always describe the same corpus rather than drifting apart. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015mWQnpye9F299NVRCCSRvj	2026-08-21 18:13:05 +01:00

Author

SHA1

Message

Date

TudorandClaude Opus 5

8967966eef

feat(places): list schools alphabetically on place pages

PR Checks / Frontend Typecheck + Tests (pull_request) Successful in 1m2s

Details

PR Checks / Backend Smoke (pull_request) Successful in 8s

Details

PR Checks / Build Backend (no push) (pull_request) Successful in 16s

Details

PR Checks / Build Frontend (no push) (pull_request) Successful in 44s

Details

PR Checks / Build Pipeline (no push) (pull_request) Successful in 11s

Details

PR Checks / AI Code Review (Claude) (pull_request) Canceled after 1m21s

Details

Someone on a place page is usually looking for a school they can name, so the
order should serve scanning for it rather than ranking. /api/rankings keeps
its league-table ordering; this is a place-page decision, not a site-wide one.
Sorted case-insensitively, or a capitalised name would sort ahead of every
lowercase one.

The change made five pieces of copy untrue, so they go with it. The phase
variant titled itself "— Ranked", and all four route families described
themselves as "ranked by SATs and GCSE results". A page that opens by claiming
an order it does not keep is worse than one that claims nothing.

The ItemList markup carried `position` with no declared order, which reads as
a ranking. It now declares ItemListOrderAscending, so the structured data says
what the table does.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015mWQnpye9F299NVRCCSRvj

2026-08-22 00:09:58 +01:00

TudorandClaude Opus 5

c5af476213

feat(places): /api/places registry and place detail endpoints

The registry is cached for the process and reset by the same admin endpoint
that rebuilds the sitemaps, so places and sitemap always describe the same
corpus rather than drifting apart.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015mWQnpye9F299NVRCCSRvj

2026-08-21 18:13:05 +01:00