✨ 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

Edit Flow stores custom statuses as a taxonomy and editorial metadata in _ef_editorial_meta_* postmeta. SleekView Charts rolls them into pipeline dashboards with status donuts, editor workload bars, and publication trends.

♾️ Lifetime License available

SleekView Charts dashboard for Edit Flow

Editorial telemetry from the same metadata

Edit Flow stores custom editorial statuses (Pitch, Assigned, In review, Approved) as a taxonomy backing the post-status dropdown, and editorial metadata (due date, word count, channel, brief) in postmeta under keys prefixed _ef_editorial_meta_. The Story Budget and Calendar give a calendar-style overview, but neither answers 'how many pieces are stuck in review' or 'what is our weekly publication rate'.

SleekView Charts reads the post table joined with the Edit Flow status taxonomy, pivots editorial-meta keys, and aggregates. Total drafts in flight, pipeline distribution as a donut, editor workload as a bar, and posts published per week as an area chart turn the same data the Story Budget summarises into a dashboard a managing editor can scan in seconds.

Charts share the same data layer as the SleekView editorial table, so a filter applied on the table (status equals In review, due in the next 7 days) reshapes every chart card. The downstream PublishPress Planner fork uses the same data structures, so a dashboard built for Edit Flow ports across with minor configuration. The plugin still owns notifications and the editorial workflow; the charts add the reporting layer the Story Budget hints at but does not fully deliver.

Workflow

From custom statuses to a pipeline dashboard

1

Read posts with custom statuses

Join wp_posts with the Edit Flow status taxonomy so each post's editorial status becomes a chartable dimension. Pitch, Assigned, In review, and Approved are all groupable.
2

Pivot editorial-meta keys

Promote _ef_editorial_meta_* postmeta into named, chartable columns. Due date, word-count target, channel, and brief each become groupable or aggregatable.
3

Pick pipeline KPIs

Total drafts in flight as a Number, pipeline distribution as a donut, editor workload as a horizontal bar. Three cards already replace the daily Story Budget tour.
4

Trend publication velocity

Posts published per week as an area chart shows editorial velocity. Retros open with a real number; planning calibrates against observed pace.

Sample dashboard

Charts you can build from Edit Flow data

An editorial dashboard built on posts joined with Edit Flow custom statuses and _ef_editorial_meta_* postmeta pivoted into named columns.
Number · Default

Drafts in flight

Top-line count of every post in any pre-publication status. The number managing editors check before standup.
Count
Pie · Donut

Pipeline by status

Distribution across Pitch, Assigned, In review, and Approved. The shape tells you whether the bottleneck is writing or reviewing this week.
Count group by ef_status
Bar · Horizontal

Workload by editor

Open pieces per editor across the pipeline, joined to wp_users. Reassignment decisions surface before they cost a deadline.
Count group by post_author
Area · Gradient

Posts published per week

Editorial velocity trend. Retros open with the curve; planning calibrates against observed pace instead of optimistic targets.
Count group by post_date

Comparison

Default Edit Flow reporting vs SleekView Charts

Default Edit Flow

  • Story Budget and Calendar are overviews, not aggregated KPIs
  • Status distribution is not visualised anywhere
  • Editor workload across the pipeline requires manual counting
  • Weekly publication trends need external spreadsheet work
  • Editorial-meta fields are not surfaced in any chart

SleekView Charts

  • Drafts-in-flight Number card across every status
  • Pipeline donut for at-a-glance bottleneck detection
  • Editor workload bar with joined names
  • Publication velocity area chart per week
  • Average days-in-status from editorial-meta timestamps

Features

What SleekView Charts gives you for Edit Flow

Pipeline bottleneck donut

Distribution across Pitch, Assigned, In review, and Approved in one shape. The donut surfaces whether writing or reviewing is the bottleneck this week.

Editor workload

A horizontal bar of open posts per editor, joined to wp_users for readable labels. Reassignment decisions become data-driven instead of memory-driven.

Publication velocity

An area chart of posts published per week turns editorial pace into a number. Retros and planning meetings open with the curve, not a vibes check.

Audience

Who builds Edit Flow charts dashboards with SleekView

Managing editors

A daily dashboard with pipeline donut and workload bar. Standups open with three numbers instead of a Story Budget tour and a per-status drill-down.

Newsroom teams

Per-team dashboards scoped via Edit Flow User Groups, with handoff-rate charts and review-load bars. Cross-team capacity becomes a saved view.

Editorial leads

Weekly publication trend and average days-in-status charts as the opening slides of every retro. Editorial pace gets a real number; bottlenecks get a name.

The bigger picture

Editorial workflow needs aggregate signals

Editorial workflow plugins fail in a specific way: they ship a calendar and a budget board, both of which are visual overviews, and they treat the per-post editor as the place where actual work happens. The middle layer (the standup queue, the 'what is blocking us' question, the 'are we shipping enough' question) requires aggregates. Edit Flow already stores the data: custom statuses, due dates, assigned editors, word counts.

The default surfaces summarise it as a calendar grid, which is great for date scanning and useless for status-distribution questions or velocity trends. Aggregate charts close that gap. A donut of pipeline status shows whether the bottleneck is writing or reviewing in a glance.

A bar of editor workload surfaces capacity issues before they cost a deadline. An area chart of posts published per week turns editorial pace into a number. SleekView Charts reads the same postmeta and taxonomies Edit Flow writes to, so dashboards stay in sync with the canonical data.

The plugin keeps owning the workflow; the charts add the visibility the Story Budget never quite delivered.

Questions

Common questions about SleekView Charts for Edit Flow

Custom statuses from the Edit Flow taxonomy, editorial metadata from _ef_editorial_meta_* postmeta, post authors from wp_posts, and User Group assignments from usermeta. Each becomes a chartable dimension after the join.

 

Yes. Pivot specific _ef_editorial_meta_* keys into named columns first (deadline, channel, brief link), then chart them. A bar of average word-count target per channel or a donut of pieces by channel is two clicks to build.

 

Yes. Planner is the modern fork and preserves Edit Flow's taxonomy and meta naming. SleekView Charts reads both with minor configuration differences, so dashboards built on Edit Flow port to Planner without rebuilding.

 

Yes. Edit Flow stores User Groups in a taxonomy with usermeta linkage. Charts can scope to a group so each team opens to its own pipeline view. Cross-team dashboards stay available for managing editors.

 

If your install records status-change timestamps (Edit Flow can be configured to log them as editorial-meta), charts compute average days-in-status as a chartable metric. A bar of average days per status surfaces the bottleneck column quantitatively.

 

Yes. Charts and Tables share the same data layer. A filter on the SleekView editorial table (status equals In review, due in the next 7 days) reshapes every chart card on the dashboard.

 

Yes. Edit Flow can apply its statuses and metadata to any post type. SleekView Charts reads whichever post types Edit Flow is active on, so a custom 'newsletter' or 'video' CPT charts the same way standard posts do.

 

Yes. Each card exports as PNG and as CSV. Weekly velocity charts and quarterly bottleneck rankings come out of the dashboard ready for editorial board presentations.

 

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