Pagination

Use page controls for finite collections with an explicit current position.

Start with your first page. Shared ui* providers are registered by createAdmin. Examples belong inside a route template, not the root HTML document. The page and its optional controller load through Atrium’s lazy route registry.

Minimal example

<nav aria-label="Results pages">
  <ul class="pagination">
    <li class="page-item active"><button class="page-link" aria-current="page">1</button></li>
    <li class="page-item"><button class="page-link" @click="loadPage(2)">2</button></li>
  </ul>
</nav>

Settings and behavior

• Your provider supplies loadPage and keeps active state synchronized.
• Disable unavailable previous and next buttons.
• For real record lists prefer dataTable, which handles page bounds and URL state.
• Reset to the first page when filters change.

Integration notes

Use theme tokens instead of fixed colors. Keep accessible labels on controls. Test with keyboard navigation, both themes, and a narrow RTL viewport.

Working reference

See the production example. Return to the component index.

Author

Laurent Declercq l.declercq@agon-innovation.ch

License

Unless otherwise stated all source code is licensed under LGPL 2.1 and has the following copyright:

© 2026, Agon Partners Innovation AG, All rights reserved.

The design material and the “Agon Ātrium” trademark is the property of their authors. Reuse of them without prior consent of their respective authors is strictly prohibited.

Version

Version: 20260921