Dt Tables Laravel Package

Use when working with the nyumbani/dt-tables package's own web UI under /dt-tables: the landing page (/dt-tables), the table admin at /dt-tables/data-tables (registering a DataTable and its mode, the cards list with search and mode tabs, the edit page with its sidebar sections, columns and search types, name/mode/theme/buttons/behaviour/loader settings, rename and delete), the documentation at /nyumbani-dt-tables/docs (adding or editing a docs page, the x-docs components of nyumbani/docs, the DtTablesDocs page list), or debugging why a table isn't picking up its resources/data-tables/{key}.json configuration. Covers the package's own routes, controllers, TablePresenter, Blade views and admin.js under package/src and package/resources. Do not use for writing Table classes in app/DataTables/, the <x-data-table> component itself, or the DataTables JS/CSS bundle (client.js) — see the dt-tables-development and dt-tables-server-side skills for those.

Use this skill whenever creating, modifying, or debugging DataTables using the nyumbani/dt-tables package. Covers creating Table classes in app/DataTables/, defining queries with Eloquent, mapping rows via handle(), configuring column search types, rendering tables in Blade views with <x-data-table>, passing data from controllers, using the DataTable facade for attributes and styling, and registering tables as resources/data-tables/{key}.json files. Also covers export configuration, action buttons, shared data patterns, conditional columns, the before()/after() lifecycle hooks, and listening for the DtButtonTriggered event fired when copy/excel export buttons are clicked. Do not use for generic HTML tables, Livewire tables, or JavaScript-only table libraries. For tables that should page, search and sort in the database (ServerSideTable, ApiTable, <x-data-table :source>), use the dt-tables-server-side skill. For the package's built-in admin UI at /dt-tables/data-tables (registering tables, editing columns/settings), use the dt-tables-admin skill instead.

Use when a DataTable has too many rows to load at once and should page, search and sort on the server instead, either in the database (ServerSideTable) or through an HTTP API (ApiTable): creating ServerSideTable classes in app/DataTables/ (php artisan make:data-table --server-side), ApiTable classes for tables whose rows come from a remote API (php artisan make:data-table --api; client(), endpoint(), params(), parse(), PageRequest, Page, 502/504 errors, page-only enrichment), defining query(), columnMap() (SQL expressions, search closures, the global opt-out, or remote field names for APIs), keyColumn(), filterOptions() and authorize(), rendering with <x-data-table :source :params>, the server-side endpoints and config('dt-tables.server_side') settings, and debugging searches, sorting, counts, loader/error messages or 403/419 responses. Do not use for inline tables built with BaseTable::build() and :payload, or for the admin UI — see the dt-tables-development and dt-tables-admin skills.