✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Charts for Edit Flow Pro

SleekView Charts reads Edit Flow Pro's custom statuses taxonomy, editorial metadata in postmeta and User Groups, then renders pipeline counts, status splits, per-editor load and due-date trends as Number, Pie, Bar and Area cards.

♾️ Lifetime License available

SleekView Charts dashboard for Edit Flow Pro

Editorial pipelines are a chart, not a budget board

Edit Flow Pro stores custom editorial statuses as a taxonomy attached to posts, editorial metadata as postmeta under keys prefixed _ef_editorial_meta_ and User Group assignments in usermeta and a custom taxonomy. The Story Budget and Calendar views are good visual overviews, but neither rolls the data up into measurable shapes. Managing editors compensate with spreadsheets that go stale the moment the next status change lands inside Edit Flow.

SleekView Charts reads the same wp_posts joined with the Edit Flow status taxonomy and pivots editorial metadata into proper columns. A Number card counts posts in active editorial statuses (Pitch, Assigned, In review) so the cross-pipeline volume is one number, not a count of cards. A Pie splits posts by status so cross-status balance is a glance. A Bar groups by editor so per-editor load is bar height instead of a manual count. An Area trends new editorial tasks per week so backlog growth has a shape.

The plugin keeps owning custom statuses, editorial metadata and the notification module. SleekView Charts adds the cross-pipeline cockpit that the Story Budget hints at but does not deliver.

Workflow

Turn Edit Flow Pro data into a dashboard

1

Read posts with custom statuses

Join wp_posts with the Edit Flow custom-status taxonomy so each post's status (Pitch, Assigned, In review, Approved) becomes a queryable column on the chart dataset.
2

Pivot editorial metadata

Promote _ef_editorial_meta_* keys into named columns: due_date, editor, word_count, channel. Each becomes a group-by or filter dimension on the dashboard.
3

Expose User Groups

Bring User Groups in as a filter dimension so dashboards can scope to Marketing, Newsroom or any team Edit Flow Pro tracks.
4

Compose and save

Pick Number, Pie, Bar, Area or Radar cards. Group by status, editor, due_date, channel or User Group, and aggregate as Count, Average or Maximum on word_count. Save dashboards per role.

Sample dashboard

Charts you can build from Edit Flow Pro data

Each card below reads from wp_posts joined with the Edit Flow custom statuses and editorial metadata. Combine them into a daily editorial cockpit, a per-editor load view or a channel-balance board for content leads.
Number · Default

Posts in editorial pipeline

Single KPI counting posts in any active editorial status (Pitch, Assigned, In review, Approved). The anchor number for a daily editorial stand-up.
Count
Pie · Donut text

Posts by editorial status

Splits posts across each Edit Flow Pro custom status. The shape of the pipeline (front-heavy on Pitch, middle-heavy on In review) becomes one glance.
Count group by editorial_status
Bar · Horizontal

Posts per editor

Groups in-flight posts by the editor assigned in editorial metadata. Load balance becomes bar height instead of tribal knowledge across the editorial team.
Count group by editor
Area · Gradient

Pipeline volume per week

Time series of new posts entering the editorial pipeline each week. A rising line warns that intake has outrun shipping pace before deadlines start slipping.
Count group by post_date

Comparison

Default Edit Flow Pro admin vs SleekView Charts

Default Edit Flow Pro admin

  • Story Budget and Calendar are good overviews but not aggregated KPIs
  • Editorial metadata in postmeta is not exposed as charts
  • No pie split of custom statuses for cross-pipeline visibility
  • Per-editor load needs a manual count from the calendar view
  • Backlog growth has no trend line in the default admin

SleekView Charts

  • KPI card for posts in any active editorial status
  • Pie of custom statuses to see the shape of the pipeline
  • Bar of posts per editor so load is visible, not guessed
  • Area trend of pipeline intake per week
  • Same dataset feeds the chart cards and the editorial table view

Features

What SleekView Charts gives you for Edit Flow Pro

Editorial cockpit

Render the editorial pipeline as Number, Pie, Bar and Area cards. Stand-ups and weekly editorial reviews open on a single dashboard, not the Story Budget.

Per-editor load

Group by the editor meta field on a Bar card to see open work per editor. Hand-offs and reassignments get data instead of memory during a busy publication cycle.

User Group scoping

Use Edit Flow Pro's User Groups as a dashboard filter. The Marketing dashboard scopes to Marketing posts; the Newsroom dashboard scopes to Newsroom. Both run on the same data.

Audience

Who builds Edit Flow Pro charts dashboards with SleekView

Managing editors

Pin a daily cockpit with pipeline KPI, status pie and editor bar. The editorial morning starts with the same three cards instead of opening twelve drafts in tabs.

Section editors

Filter by User Group to scope the dashboard to a section (Tech, Lifestyle, Business). Each section editor sees their own pipeline shape on the same surface.

Content strategy leads

Trend pipeline intake per week to see whether the team is taking on more than it can ship. Plans for the next quarter get backed by an actual throughput line.

The bigger picture

Why editorial pipelines need a real cockpit

Editorial workflow plugins capture the right data and then surface it through views that work for one piece at a time. Edit Flow Pro is no exception: custom statuses, editorial metadata, User Groups and a notification module are all there, and the Story Budget gives them a visual board. The gap is the cross-pipeline question.

"How many posts are in active editorial status right now", "how does the load split across editors this week", "is intake outrunning shipping over the last month", "which section has the longest backlog". The answers live in the same data the editor uses every day, but the default surface does not aggregate them. Charts do.

The plugin keeps owning the editorial workflow and the per-post detail, the dashboard becomes the cross-pipeline view, and editorial leadership finally has a cockpit instead of a budget board.

Questions

Common questions about SleekView Charts for Edit Flow Pro

No. SleekView is read-only against the post table and Edit Flow Pro's taxonomies and meta. The plugin continues to own custom statuses, editorial metadata, User Groups and notifications; SleekView Charts just renders aggregations on top of the data the plugin already maintains.

 

Yes. Group by the Edit Flow status taxonomy on a Pie or Bar card to see how posts are distributed across Pitch, Assigned, In review, Approved and any custom statuses the team has added. Custom statuses are first-class chart dimensions.

 

Yes. Add a filter for User Group and the entire dashboard, including KPI, pie, bar and trend, narrows to the posts assigned to that team. Per-section dashboards run on the same data with different filter presets.

 

Yes. Promote the editor meta key into a named column and group by it on a Bar card to see load per editor. Combine with the status pie to see whether a particular editor is stuck in review or buried under new pitches.

 

Edit Flow's data structures are nearly identical to PublishPress Planner's, with the same taxonomy and meta naming. SleekView Charts reads both with minor configuration differences, so most dashboards built for Edit Flow Pro run on Planner installs without changes.

 

Yes. Group by post_date or by a custom editorial timestamp with an Area card and a Count aggregation to see new posts entering the pipeline per day or week. Useful for spotting whether intake is outpacing shipping over a quarter.

 

Yes. Any filtered set behind a chart card exports as CSV with the same columns the table view would show. Editorial retrospectives and content reviews get a real spreadsheet of posts with status, editor and metadata fields attached.

 

No. Edit Flow Pro continues to own pitching, assigning, status transitions and notifications. SleekView Charts is the cross-pipeline cockpit on top of that workflow, designed for the editorial leadership questions that the per-post surface was not built to answer.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView