ZEVA 2 - Implement standardized Table component based on Design System #279
Description
Describe the task
Implement a standardized Table component across the system based on the approved Table Design in the Design System.
Purpose
This task aims to:
- establish a single, reusable Table component aligned with the Design System
- ensure visual and interaction consistency across all pages
Prototype Page level design reference
A full-page prototype has been added to illustrate how the table component appears within a real layout (eg Admin page) - in relation to page header, tabs, and surrounding actions.
Acceptance Criteria
- Table styling (spacing, typography, borders, colors, states) matches the Design System (see Figma)
- A single base Table component is implemented and reused across the system
- The following features are optional and enabled when required: pagination, column sorting ,text-based, search / filtering, row-level copy action
- Copy action behavior: only the copy icon is clickable - clicking the icon copies the corresponding cell value (e.g. email) to the clipboard
- All enabled features follow the visual and interaction patterns defined in the Design System
Additional context
Table layouts, states, and feature examples are documented in the Design System (see Figma reference)
This task focuses on UI styling and interaction behavior, not on changing existing data logic
Different tables may require different feature combinations, but all must reuse the same base Table component
If additional or advanced filtering is required (e.g. dropdown filters, multi-selects, or table-specific logic), this will be defined in separate supporting tickets for specific use cases