Edit visible WordPress text directly on the frontend.
Frontend Text Edit lets authorized editors fix supported rendered text in place and save changes back to native Gutenberg block content.
Use it for small copy corrections where opening the backend editor adds friction.
No separate content layer.
Edits are written back into normal WordPress post content. If the plugin is disabled later, the copy changes remain.
Fix visible text in context. Frontend Text Edit is deliberately narrow: it edits supported rendered text and saves it back to native Gutenberg markup.
The Problem
Small corrections take too long
A typo found on the frontend often turns into opening wp-admin, finding the page, and locating the right block.
Context gets lost
Editors see the problem on the rendered page, but fix it in a different interface.
Frontend editors often add lock-in
Broad page builders and overlays can create a second content layer instead of updating WordPress content.
What It Does
Inline text edits
Logged-in editors with normal edit permission can turn on frontend text editing from the admin bar.
Native Gutenberg storage
Changes are saved back into post_content as normal block markup, not into a shadow content table.
Missing support reports
Unsupported visible text can be reported to Devenia from public pages so reproducible adapter gaps can shape future releases.
Current Support
- Core paragraph, heading, list item, and button text
- Text-node segments inside richer core block HTML
- Linked list-item text while preserving the existing link URL
- GenerateBlocks headline and button text
- Rank Math FAQ question and answer text
Current Release Status
- Latest release: 0.1.3
- Requires WordPress: 6.9+
- Requires PHP: 8.0+
- License: GPL v2 or later
Frequently Asked Questions
Is Frontend Text Edit a page builder?
No. It is a focused text correction tool. It does not edit layout, design settings, media, templates, or block structure.
Where are edits stored?
Edits are saved back into the original WordPress post content as normal Gutenberg block markup.
What happens if the plugin is disabled?
The text changes remain in WordPress content. Deactivating the plugin only removes the frontend editing interface.
Who can edit text?
Only logged-in users who can normally edit the current post through WordPress permissions can use the editor.
Does it edit every block?
No. It marks supported text surfaces where rendered text can be safely mapped back to stored block content.
What are missing support reports for?
They help Devenia identify reproducible block support gaps. Reports are sent only for publicly reachable pages and do not include logged-in user identity.