FluentFramework is the shared foundation used by the Fluent suite of plugins (FluentCRM, Fluent Forms, FluentSupport, FluentBooking, and FluentSMTP). Rather than living in wp_postmeta, the framework stores data in dedicated tables: wp_fc_subscribers and wp_fc_campaigns for FluentCRM, wp_ff_submissions for Fluent Forms, wp_fst_tickets for FluentSupport, and so on. Each plugin ships its own admin UI for its own tables, but cross-plugin views ("contacts who submitted form 12" or "customers with an open ticket") require building reports by hand.

SleekView reads any framework-backed table directly. A FluentCRM view shows email, status, tags, lists, and last_activity from wp_fc_subscribers in one row. A Fluent Forms view shows submission status, form name, and the most-used field values from wp_ff_submissions and wp_ff_submission_entry_details. Sorts and filters use the table's existing indexes, and joins follow the framework's defined relationships so a contact's tickets and form submissions can sit in adjacent columns.

Inline edits route through each plugin's own model layer where supported (FluentCRM contact updates, Fluent Forms submission notes, FluentSupport ticket status), with conflict detection on direct writes when no model API is exposed. SleekView is admin-only and coexists with each plugin's native admin: deactivating it leaves every custom table, including wp_fc_subscriber_meta and wp_ff_submission_logs, exactly as it was.

The Fluent suite is unusual in WordPress: a family of plugins that share a single framework and a single conventions-based custom table layer. The benefit is performance. CRM contacts, support tickets, and form submissions live in dedicated indexed tables, not in wp_postmeta, and queries stay fast at scale.

The cost is that each plugin ships its own admin for its own slice of the framework, and cross-plugin lookups end up as one-off SQL or hand-built dashboard widgets. Support teams flip between FluentSupport and FluentCRM to know who is filing tickets. Marketing teams export from FluentCRM to spreadsheet to know who is also active in Fluent Forms.

Developers build custom admin pages for every client that uses more than one Fluent plugin. SleekView treats the framework as what it already is: a coherent set of related tables with real columns and real indexes. Each table becomes a view, joins follow defined relationships, edits route through each plugin's model API.

The data stays where the framework put it; the admin finally reflects that the framework is one thing.