> For the complete documentation index, see [llms.txt](https://docs.klai.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/elements/table.md). # Table 📏 * [ ] Table header The value of each column to provide structure for the row content * [ ] Row style Borders and contrasting background colors can be explored to differentiate * [ ] Spacing Define the consistent padding of each row and the header * [ ] Search The ability to find a specific keyword or row * [ ] Actions Performing a task based on the row and information seen e.g. view, edit, delete * [ ] Filter and sort Allow users to customize what they want to see in the table and in which order * [ ] Responsiveness Determine the structure on significantly smaller devices - whether the information collapses into an accordion for example ⭐️ Horizontal scrolling is an alternative to rethinking a new layout * [ ] Pagination Breakpoints in the table for digesting information in parts --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/elements/table.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.