by jamiemarsland 4.6 (8 reviews)

Jamie's Front-End Editor for Content Teams

Name: Jamie's Front-End Editor for Content Teams
Rating: 4.6 (8 reviews)
Author: jamiemarsland

Let your content team edit text, links, buttons and images on the front end, and see every change across your site in one place.

Jamie's Front-End Editor for Content Teams ranks #13,403 among WordPress.org plugins with 100+ active installations, a 4.6/5 rating from 8 reviews, and was last updated Jul 21, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7.0.8 (Current: 7.1.4)

v0.8 Current Version v0.8

Updated 3 months ago Last Update on 21 Jul, 2026

Refreshed 1 week ago Last Refreshed on

Top 25% by installs Downloads -13.4% this week

View on WordPress.org

Rank

#13,403

— No change

Active Installs

100+

-47.1%

KW Avg Position

14.7

0.4 worse

Downloads

3.7K

+2 today

Support Resolved

— No change

Rating

92%

Review 4.6 out of 5

4.6 (8 reviews)

Next Milestone 200

Total Progress 83%

100+ 200+

729

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 17 more installs to reach 200+

Rank Changes

Current #13,403

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

4.6

8 reviews

Overall 92%

7 (88%)

0 (0%)

1 (13%)

0 (0%)

Support Threads Overview

Resolved

Unresolved

Total Threads

Resolved

Unresolved

Resolution Rate

Security History

Source: WPVulnerability

No known vulnerabilities on record for Jamie's Front-End Editor for Content Teams. Checked 3 months ago.

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 0.8
Last Updated: Jul 21, 2026
Requires WP: 6.5+
Tested Up To: 7.0.8
PHP Version: 8.0 or higher
Author: jamiemarsland

Support & Rating

Rating: ★ ★ ★ ★ ★ 4.6
Reviews: 8
Support Threads: 1
Resolved: 0%

Keywords

block-editor frontend editing inline editor interactivity api

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,015

TL;DR

AI summary of the plugin's readme

This plugin is for WordPress site owners who let content teams edit page and post text without using the block editor. It solves the problem of needing wp-admin access just to make simple text edits, by allowing direct inline editing on the live front end.

Inline editing of paragraphs and headings
Block markup preserved on save
Edits recorded as block notes
Admin settings for editable block types
Front-end-only editing role restriction
Editing UI limited to permitted users

Frequently Asked Questions

Common questions about Jamie's Front-End Editor for Content Teams

Yes. The plugin uses the render_block filter and works with any block theme.

Yes. Edits are saved per-block via a custom REST endpoint that parses and serializes blocks server-side.

By default, paragraphs and headings. You can configure this in Settings > Front-End Editor.

Only logged-in users who already have permission to edit the post. The editing UI is never shown to visitors.

Yes. You can lock a whole page (a checkbox in the "Front-End Editing" box when editing the page), or lock a single block/section using the block's own Lock option (the padlock in its Options menu) or by adding the CSS class "fie-no-edit" in its Advanced panel. A locked block, and everything nested inside it, becomes read-only on the front end. Locks are enforced when saving, so they can't be bypassed.

Jamie's Front-End Editor for Content Teams

Next Milestone 200

Unlock Exact Install Count

Rank Changes

Upgrade to Pro

Active Installs Growth

Downloads Growth

Upgrade to Pro

Reviews & Ratings

Support Threads Overview

Security History

Track This Plugin

Plugin Details

Support & Rating

Keywords

Upgrade to Pro

Similar Plugins

TL;DR

Frequently Asked Questions

Sign In / Register