UI Components

Pagination

Page navigation control with ellipsis, prev/next buttons, and keyboard support.

Quick Preview

Installation

// Copy from
src/components/ui/Pagination.tsx

Usage

'use client'
import { useState } from 'react'
import { Pagination } from '@/components/ui/Pagination'

export default function Page() {
  const [page, setPage] = useState(1)
  return (
    <Pagination
      total={200}
      page={page}
      pageSize={20}
      onChange={setPage}
    />
  )
}

Examples

Many pages

Few pages

Prompt Preview

Copy a prompt that recreates this UI

Paste this into your AI coding assistant to generate code that closely matches the reference, including color, size, shape, typography, spacing, and polish.

Copy-ready AI prompt

Starts from the current visual reference and project constraints.

Build a ui component named Pagination in React/Next.js.
Goal: recreate the same overall UI and behavior as the Pagination reference from a component gallery.
What it needs to communicate: Page navigation control with ellipsis, prev/next buttons, and keyboard support..

Project constraints:
- Use Next.js 16.2.6 with the App Router, React 19, TypeScript strict mode, and Tailwind CSS v4.
- Do not create a tailwind.config.js file. Use Tailwind v4 utilities and CSS variables where design tokens are needed.
- If you are implementing this inside the same project, use the Prompt font via next/font/google. If not, use the closest equivalent typeface.
- Return production-ready code with imports, responsive behavior, keyboard accessibility, and polished empty, hover, focus, active, and disabled states where relevant.
- Match the reference closely: color palette, spacing scale, border radius, shadows, icon scale, typography hierarchy, and motion timing.

Component-specific expectations:
- Keep the API concise and reusable.
- Make visual states feel polished and consistent across variants and sizes.
- Avoid unnecessary dependencies unless the behavior truly requires them.
- No explicit color literals were found in the examples. Match the live reference and the project accent color when appropriate.

Props to support:
- total: number — required — Total number of items
- page: number — required — Current active page (1-based)
- pageSize: number — default 10 — Items per page
- siblingCount: number — default 1 — Pages shown on each side of current
- onChange: (page: number) => void — required — Callback when page changes
- className: string — Additional CSS classes

Reference usage patterns:
- No examples were documented. Infer a sensible default presentation and one richer usage example.

Feature expectations:
- Ellipsis for large ranges
- Prev/Next buttons
- Configurable sibling count
- Accessible aria labels

Output requirements:
- Return complete code, not pseudocode.
- Include all necessary imports and helper types.
- Keep the implementation accessible, responsive, and visually finished.
- Match the reference for color, size, shape, typography, spacing, and interaction states as closely as possible.
- If multiple files are needed, organize them cleanly and explain the file structure briefly.

Tweak only product-specific copy or data after the first generation pass.

Props

Prop	Type	Default	Description
`total`*	`number`	-	Total number of items
`page`*	`number`	-	Current active page (1-based)
`pageSize`	`number`	`10`	Items per page
`siblingCount`	`number`	`1`	Pages shown on each side of current
`onChange`*	`(page: number) => void`	-	Callback when page changes
`className`	`string`	-	Additional CSS classes