No. The standard posts list stays in place and remains the right place for individual draft review and editorial workflow. SleekView Charts adds the cross-cutting weekly dashboard the default screens do not assemble, so the two layers complement each other rather than competing for the same screen real estate inside the admin.

Yes. The post_author column on wp_posts is a natural groupBy dimension. SleekView pivots author IDs into named editors at the dataset level so a Bar card resolves to display names from wp_users. Editor in chief uses it to spot uneven AI adoption across the team and to flag heavy users for workflow conversations.

Yes. The _contentbot_tokens meta key on wp_postmeta carries the token count for each generation. SleekView Charts sums tokens across the dataset and renders a Sum card alongside the daily area trend, so finance sees ContentBot cost as a live KPI rather than a monthly invoice surprise.

Yes. Dashboard-level filters apply to every chart card so the whole dashboard responds to a single category or tag filter using the wp_term_relationships join. That makes per-section editorial reviews a one-click switch rather than a per-card configuration job for each chart in the layout.

Yes. Aggregations run on the indexed columns WordPress already maintains on wp_posts and wp_postmeta, so sites with thousands of AI drafts render charts in seconds. The Charts engine uses pagination and indexed joins rather than scanning every meta blob on every render of the chart card on screen.

Yes. Each chart card exposes its underlying post row set, which exports to CSV with the active filters applied. Studio owners hand the CSV straight to the monthly review without round-tripping through a spreadsheet rebuild, and finance uses it for ContentBot subscription decisions with leadership.

ContentBot leaves the _contentbot_generated meta key on the post regardless of subsequent edits, so the dashboard counts the row as AI-originated even after editor revision. A second meta key or post_modified comparison can split fully-AI from human-revised in a separate Bar card on the same dashboard if needed.

Yes. SleekView Charts can build a separate dataset and dashboard per AI writer installed on the site, so the ContentBot meta dashboard lives next to an AIKit or Copy.ai dashboard without overlap. Each chart card references its own dataset and refreshes independently of the others on the admin sidebar.