← Compare

Jamie's Front-End Editor for Content Teams vs Classic Editor

Head-to-head on the signals that matter, from the public WordPress.org data.

Classic Editor and Jamie's Front-End Editor for Content Teams are close on health (A · 88 vs A · 85). Classic Editor has the stronger rating quality.

Active-install trajectory

Classic Editor moved down one install band, 9M+ to 8M+. That's a single step across the whole window, so there's no trajectory to draw. The download trend below moves daily.

Metric	Jamie's Front-End Editor for Content Teams	Classic Editor
Active installs Modeled from the public "N+" band and recent downloads.	100–200	8M–9M ✓
Active installs, change over ~6 months Compares the public install bands. One band step shows as the band change, not a percentage.	Stable ✓	-11%
Overall health	A · 85	A · 88 ✓
Maintenance How recently the plugin was updated.	98/100 ✓	90/100
Rating quality Volume-adjusted review quality.	80/100	98/100 ✓
Support Share of forum threads marked resolved.	70/100	70/100
Rating (weighted for review count)	4.2★	4.9★ ✓
Reviews	8	1,251 ✓
Ranking optimization How well the listing is tuned to rank on wp.org.	89/100	97/100 ✓
Removal risk Maintenance signals that precede a wp.org closure. Not an official status.	Low	Low
Last updated	4mo ago ✓	5mo ago
Downloads, last 30d	281	801.2K ✓
Download momentum, last 30d vs prior 30d Dips that follow a release spike are normal: wp.org counts every update as a download, so the weeks after a release run lower.	+31%	+12%
Install conversion Active installs over lifetime downloads. Downloads include every update, so older and more frequently released plugins read lower.	2.7%	8.5% ✓
Category	Blocks	Blocks

✓ marks the stronger plugin on each row. Rows where they're level show no marker.

Release activity

Jamie's Front-End Editor for Content TeamsClassic Editor

7-day average daily downloads. Downloads spike for about a week after each release as the install base re-downloads, so read this as release cadence, not growth.