Feeds paginated with configurable limits and custom accent color support
Gitpulse now supports paginated homepage feeds, paginated releases lists, and customizable accent colors—all configurable through .gitpulse.json. A new Releases tab provides direct navigation between stories and releases.
Publications using Gitpulse can now handle large archives without overwhelming readers. The homepage feed is split into pages showing two days of content each, with Older/Newer navigation links at the bottom. The releases section follows the same pattern, displaying up to 10 releases per page.
The pagination behavior is configurable—site operators can adjust how many days appear on each feed page or how many releases show per page by adding options to their .gitpulse.json file.
A new Releases tab appears in the section navigation, automatically highlighted when browsing releases at /releases/ or /releases/page/ routes. The Latest tab stays active on the homepage and paginated feed pages. Screen readers get explicit aria-current="page" context on the active tab.
Site operators who want their publication to feel more on-brand can now override the default gold/orange accent color. Setting theme.accentColor in .gitpulse.json injects the new color as a style tag in the document head, ensuring it applies before hydration in both light and dark modes.
A few behind-the-scenes improvements prevent potential issues: canonical URLs now correctly reference each specific paginated page rather than always pointing to page one, invalid pagination size inputs are guarded against, and the Releases tab no longer incorrectly activates on routes like /releases-notes-style.
This work lives primarily in the site package where the Next.js pages and components live, with configuration plumbing through the CLI package connecting .gitpulse.json settings to the generated repo.json.