Which approach best integrates Bulma's pagination component with server‑side data slicing for large datasets?

Goal

Integrate Bulma's pagination UI with a large dataset that is paginated on the server, ensuring correct page numbering and accessible navigation.

Constraints

Bulma's component only styles static links; it contains no built‑in state or asynchronous handling. The backend uses a 0‑based page index, while Bulma expects 1‑based page numbers. The dataset may contain thousands of items, requiring efficient server‑side slicing. Accessibility requirements mandate that navigation links be fully operable without JavaScript event listeners.

Unresolved Questions

1. How can the developer map a 0‑based page index to Bulma's 1‑based pagination links without introducing off‑by‑one errors?
2. Which strategy for generating URLs or data attributes will allow the pagination component to be fully accessible while remaining stateless?
3. Does Bulma provide any guidance or best practices for handling asynchronous data loads where the total page count changes after the initial render?