LearnPress is unusual: almost every learner-to-content relationship is a row in wp_learnpress_user_items with extra fields in wp_learnpress_user_itemmeta. Courses, lessons, quizzes, assignments — all user items, all keyed on user and parent course, with status and grade columns. Orders live in wp_learnpress_order_items. The default admin's three screens (Courses, Quizzes, Orders) never join up.

SleekView Charts reads the user-items table the same way SleekView Tables does, and turns it into a dashboard. A Number card counts active enrolments. A Pie card breaks user-items down by status across the catalogue. A Bar card averages grade per item or per course. An Area card plots new enrolments over time using start_time so launch and campaign effects show up immediately.

Order data joins the dashboard too. A revenue Area card uses learnpress_order_items.subtotal aggregated by order date. A refund-share Donut surfaces refund rate at a glance. Same underlying data the default reports show, configurable as cards on a shared dashboard, with cross-card filters scoping to course, instructor, or date range.

LearnPress made an opinionated choice years ago: store every learner-to-content relationship as a row in a single user-items table. That choice powers a lot of the plugin's flexibility — assignments, quizzes, custom item types, all live in the same model. But the default admin never reflects it.

Three screens, three siloed slices, and a dashboard that requires either Pro reporting or external tools. SleekView Charts treats the user-items table the same way the Tables view does: as a source you point chart cards at, with filters that carry across the whole dashboard. The plugin's data model has always been good; the missing piece was a reporting surface shaped to match it.