Both. SleekView reads H5P tables and the finished column at the database level, so whichever tier you run the board still builds. Paid add-ons that add custom fields or extra status values are picked up automatically because SleekView scans the live schema on render.

SleekView calls the H5P result update functions, which fire the same hooks the admin uses on a manual result change. Any custom listener you have on h5p_alter_user_result runs exactly as if you had edited the result from the standard H5P result screen yourself.

Yes. Card layouts are per board. Your results board can show learner, content, score, and attempt time. A per content board can show content, interaction count, and failure rate. Each board remembers its own card template so the team does not reconfigure when switching context.

Yes. SleekView respects every WordPress capability check H5P registers. A user who can view but not edit results can drag a card to inspect, but the writeback only fires for users with the same capabilities the result edit screen would enforce on a manual save action.

Add the new state in H5P the way you normally would, by adding a custom xAPI verb mapping or a custom result meta through the plugin filters. SleekView picks it up on the next board load because columns are derived from the distinct values present on rows, not hard coded.

No. SleekView paginates cards per column instead of loading every result up front. The board fetches counts via an indexed status query, and each column loads a window of cards on demand, so even an H5P library with hundreds of thousands of results stays responsive on hosting.

Yes. Any H5P related table with a status like column is a valid board. The per content interaction log, the LRS event queue, and the per cohort summary all work the same way as the main results board does once you point SleekView at the right table and choose a column to group cards on.

It stays in sync because there is no separate database. SleekView reads the same wp_h5p_results table the H5P admin reads. Changes on the kanban appear in the result list immediately, and edits from the admin appear on the next board refresh without cron sync.