Paging, not lazy-loading: 48 tiles per request, server-side offset
paging against /api/orion/scorecards, exactly as jobdb pages
its job tiles (jobdb uses 50; 48 divides evenly into the 1/2/3/4-column breakpoints, so no
row is left ragged). The whole high-ranking set fits inside the API's
from + size ≤ 10000 ceiling, so every
page of it is reachable this way. Only the tiles on screen exist in the DOM, so the grid
stays flat whether the set is 5,000 papers or 50,000.
Reproducibility candidates — published data, redone in R