توضیحات
Jamie’s Front-End Editor for Content Teams lets your team edit page and post content directly from the front end of your WordPress site. No need to open the block editor — click any text, link, button or image on the live page and change it in place.
Built on the WordPress Interactivity API with no build step required.
Give your team precise, bounded editing: let them fix the copy that should change, and lock down the parts that shouldn’t.
Features:
- Click any paragraph or heading to edit it inline, right on the live page
- Add, edit or remove links on your text without leaving the page
- Replace images from the media library, set alt text, or remove an image, all on the front end
- Edit button text and links from the front end too
- Block markup is fully preserved on save
- Lock a whole page from front-end editing with a single checkbox
- Lock individual blocks or whole sections, using the block’s own Lock option (padlock) or a CSS class. Locks cover everything nested inside and are enforced on save, not just hidden in the UI
- Edits are recorded as native WordPress block notes, so there’s an audit trail
- A central Site changes screen (Tools menu) lists every front-end edit across the whole site — what changed, where, by whom and when — with filters by user, page, block type and date, plus search and CSV export
- Admin settings to choose which block types are editable
- Option to restrict chosen roles to front-end-only editing (no wp-admin access)
- Secure — only users with edit permissions see the editing UI
نصب
- Upload the
jamies-front-end-editor-for-content-teamsfolder to/wp-content/plugins/, or install through the Plugins screen. - Activate the plugin through the Plugins menu.
- Go to Settings > Front-End Editor to configure editable blocks and restricted roles.
سوالات متداول
-
Does this work with any theme?
-
Yes. The plugin uses the
render_blockfilter and works with any block theme. -
Does it preserve block markup?
-
Yes. Edits are saved per-block via a custom REST endpoint that parses and serializes blocks server-side.
-
What blocks can be edited?
-
By default, paragraphs and headings. You can configure this in Settings > Front-End Editor.
-
Who can edit content on the front end?
-
Only logged-in users who already have permission to edit the post. The editing UI is never shown to visitors.
-
Can I stop my team editing certain content?
-
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.
نقد و بررسیها
13 جولای 2026
1 پاسخ
Very promising plugin, exactly the king of thing I am looking for for my next client.So far the only issue I have is that you can’t lock / prohibit editing of an entire page or the content inside a specific container of a page. More finesse in the editing scope would be awesome.
EDIT: Super fast update addressing my remarks, outstanding! Thank you Jamie!
10 جولای 2026
1 پاسخ
I really like the idea and I think this could someday be something fairly good. I can’t call this production ready today.
Within an hour of testing some basic functionality, I found 2 issues that would be a deal-breaker for the kind of client that would want this solution. I have posted them in the support thread, as a genuine attempt to help improve this plugin.
Outside of these issues, the UI/UX is currently too strict for the type of client that I can see wanting this. You can’t move items. You can only edit a select number of text-based blocks. You can’t add new blocks – even from that same selection. You can edit the text of a text-based link, but not the link. I understand why these things are they way they are. However, for the type of client that wants this functionality, these limitations will probably create more confusion than it is worth.
As of today, this plugin could be used for little more than copywriters fixing basic typos within a block of text.
If I want a client to be able to edit text within layouts, but lock the layout – Gutenberg already has a solution for that. If I want an editor-level user with an incredibly streamlined admin experience, WordPress already has solutions for that. This plugin feels like a solution in search of a problem.
I certainly see the potential and will keep an eye on this. I hope it improves and grows.
9 جولای 2026
1 پاسخ
Great idea, thank you so much! It works very well with Metabox custom post types as well as with regular WordPress posts. List items can also be edited. Depending on how a post was created, it may first need to be converted into blocks for the plugin to work.
9 جولای 2026
A simple and effective front-end editor for WordPress. Editing content directly on the live page is fast, intuitive, and saves time. Easy to use and works smoothly. Great job!
8 جولای 2026
1 پاسخ
I have only run a short test, and everything worked great in the Block (Gutenberg) Editor.
I really like the idea that this could separate the “Design” of a site to an admin, the allow a restricted user level to work on the text giving a clear distinction of role.
Great idea and will keep an eye out on where this develops.
8 جولای 2026
This is a great simplification and safety measure when letting clients edit pages. Super easy.
I hope it will get a few upgrades: support more blocks, support blocks of Gutenberg extensions (GenerateBlocks, e.g.), allow a bit of styling and linking.
Thank you!
توسعه دهندگان و همکاران
“Jamie's Front-End Editor for Content Teams” نرم افزار متن باز است. افراد زیر در این افزونه مشارکت کردهاند.
مشارکت کنندگان
“Jamie's Front-End Editor for Content Teams” به 1 زبان ترجمه شده است. با تشکر از مترجمین برای همکاری و کمکهایشان.
ترجمه “Jamie's Front-End Editor for Content Teams” به زبان شما.
علاقه مند به توسعه هستید؟
کد را مرور کنید، مخزن SVN را بررسی کنید، یا از طریق RSS در گزارش توسعه مشترک شوید.
گزارش تغییرات
0.8
- New: a central “Site changes” screen under the Tools menu that gathers every front-end edit across the whole site into one filterable, searchable list — what changed, where, by whom and when. Read-only, for editors and admins. Export the current view to CSV.
- Front-end edits now store structured data (page, block type, old/new text, user) so the new screen can filter and search them. Existing notes are backfilled once on upgrade.
- Fixed a brief flash of the editing toolbar and dialogs when a page first loads.
0.7.1
- Updated the plugin description to reflect that you can now edit text, links, buttons and images from the front end.
0.7
- Inline image editing. Click an image while editing and a small toolbar appears over it: Replace opens the WordPress media library and swaps the image in place, Alt text lets you set the image’s alt for accessibility, and Remove deletes the image block. Changes save straight into the block, and concurrent edits are still guarded.
- Button editing. Click a button to change its text and its link (and whether it opens in a new tab) in a small dialog, right on the front end.
- More reliable saves. Edits are now matched to blocks by content fingerprint, so removing or replacing an image no longer causes a later text save to report a false “changed by someone else” conflict.
0.6
- Inline link editing. Select some words while editing and a small link bubble appears — click it to add a link (set the URL and, if you like, open it in a new tab). Click an existing link and the bubble offers Edit and Remove. Links save into the block markup like any other edit, and they no longer navigate away while you are editing.
0.5
- A friendlier way to enable other block types. The Advanced setting is now a search-and-add field with removable chips instead of a long checklist: type to find a block, click to add it. Much easier on sites with lots of blocks.
0.4
- Fixed a bug where pressing Enter while editing could insert invalid markup and cause a “block validation” error in the block editor. Line breaks are now saved cleanly.
- Concurrent editing is now safe. Front-end editing takes WordPress’s native post lock, so two people (whether on the front end or in the block editor) can no longer edit the same page at the same time and silently overwrite each other. Anyone else who opens the page sees a read-only “So-and-so is currently editing this page” notice, and as a backstop the save is rejected if the content changed underneath the editor.
- Added an Advanced setting to enable front-end editing for other (non-core) block types on your site, such as blocks from your theme or other plugins. Tick the ones you want in Settings > Front-End Editor. This works best for blocks that show their text in a normal heading or paragraph tag; incompatible blocks simply do nothing, so nothing breaks.
- Documentation: the plugin description now covers the editing locks added in 0.3.
0.3
- Added editing locks for finer control over what your team can change. Lock a whole page with a checkbox in the “Front-End Editing” box, or lock a single block or section using the block’s own Lock option (padlock) or the CSS class “fie-no-edit” (locks that block and everything inside it). Locks are enforced on save, not just hidden in the UI.
0.2
- Added a live demo preview (WordPress Playground blueprint).
0.1
- Initial release.