Components
Archive pagination
Provide addressable archive pages rather than hiding all navigation inside a client-only list.
On this page
Purpose and placement
Provide addressable archive pages rather than hiding all navigation inside a client-only list.
Anatomy
| Part | Behavior |
|---|---|
| Current page | Selected page indication. |
| Neighbor links | Page destinations based on the archive path. |
| Bounds | First/last availability from page and totalPages. |
Configuration and contract
| Input or decision | Implementation |
|---|---|
| StoryPagination | path, page and totalPages. |
| Navigation model | Uses actual links; archive server loader determines page data. |
States and feedback
- First, intermediate and last page require different available actions.
- Component specimen shows page 2 of 5; archive fixture advertises three pages as layout data.
Usage rules
- Keep page numbers and URL state consistent in a live integration.
- Do not claim fixture pagination proves filtering or page retrieval; isolated data ignores query conditions.
Accessibility and verification
Use link names and current-page semantics that can be understood without color. Check keyboard order and phone wrapping.
Source references
| File | Responsibility |
|---|---|
| components/story-pagination.tsx | Audited Townwell implementation; use this file when extending this interface. |
| lib/story-pagination.ts | Audited Townwell implementation; use this file when extending this interface. |
Examples from the app
Actual Boise Today and Townwell UI with synthetic editorial, business, review, media metadata and analytics. Existing Boise imagery; no live data changes. Captured at 2× resolution or higher. Select an image to inspect it full size.
Related topics
Source audit: 2026-10-07 · Revision ce8bc72b96da · Documentation v0.1