Echo Knowledge Base (EPKB) supports multiple separate knowledge bases on one WordPress install, each with its own post type (epkb_post_type_1, epkb_post_type_2, etc.), category taxonomy, and rating postmeta. The plugin's default admin shows each KB as a separate post list, which makes per-KB triage workable but cross-KB editorial decisions painful.

SleekView reads each KB's post type plus the matching wp_postmeta rows (including epkb_post_views, epkb_post_likes, and epkb_post_dislikes) and pivots them into a unified editorial table. Categories resolve to readable names, ratings derive into a helpful-ratio column, and saved views like "Cross-KB articles updated over 180 days ago with helpful ratio below 50%" become one-click reloads.

Inline edits to status, category, and assigned author route through WordPress core (wp_update_post, wp_set_object_terms) which is how EPKB reads them on its side. The plugin's transient caches and front-end KB caches invalidate normally, and the published help center reflects changes on the next request.

Running multiple knowledge bases on one WordPress install used to be an unusual setup. It has become routine for any company that ships a developer product alongside a customer product, or that maintains a partner KB separately from a public one. EPKB Pro handles the data model cleanly: each KB gets its own post type, its own taxonomy, its own ratings, its own URL prefix.

What the plugin doesn't try to do is unify the editorial surface. The default admin shows each KB as a separate screen, which keeps things tidy for single-KB teams but blocks the cross-KB editorial views a docs lead actually needs to plan a sprint. SleekView reads every configured EPKB post type at once, exposes the source KB as a column, and derives helpful-ratio from the per-article rating postmeta.

Saved views cover the editorial decisions teams already want to make: which articles across all KBs are aging fastest, which categories have the lowest helpful scores, which writers are behind. Inline edits route through WordPress core so EPKB's own caches invalidate and the public KB stays in sync. The plugin keeps its data model intact; SleekView turns it into a triage table the docs team actually opens every week.