FrontEdit Pro: Team Workflows for Gutenberg Editing
Edit supported content on the live page
FrontEdit Pro extends FrontEdit, a frontend editor for existing Gutenberg content. Users with permission to edit a page can click supported blocks where they appear and make changes in context. FrontEdit updates block content and attributes while preserving the block structure, styling, settings, and standard WordPress serialization.
Common edits include headings, paragraphs, images, buttons, lists, and tables. Other supported blocks include selected media and design blocks. Each block keeps its own editing session and undo history, so users can move between blocks while retaining edits in progress. Batch editing is available to users with editing access; Pro lets administrators choose which users can edit several blocks in a session and which must work on one block at a time.
Route changes through review
Pending drafts and approval workflows let teams review proposed changes before treating them as completed updates. Editing permissions provide more control over access for clients and other contributors.
- Drafts and approvals: review proposed content changes before completion.
- Per-user editing controls: set who can edit one block or several blocks in a session.
- Content requests: track and respond to user-submitted change requests through a ticketing workflow. The base plugin sends block-linked requests to the administrator by email; Pro adds tools to track, respond to, close, and search them.
- Content Catalog: review editable elements across the site from a centralized area.
- History and reverts: review block-level changes and use the available revert process when needed.
- Dashboard and notifications: bring open requests and pending drafts into a central view for editorial work.
Keep editing access controlled
FrontEdit is for users authorized to edit the page in WordPress. Its safeguards include post-lock notices when another user is editing, an explicit takeover step before applying live changes, warnings about leaving with unsaved changes, and a warning if newer edits may be overwritten.
FrontEdit supports publicly viewable custom post types that use the block editor and store editable blocks in standard post content. It edits supported blocks in that content area; it does not edit custom-field values, flexible-content layouts, block-bound post metadata, or third-party page-builder layouts.
Extend editing with developer tools
FrontEdit includes a versioned Public JavaScript API for plugins, custom tools, and AI assistants. Integrations can inspect supported editing capabilities, stage schema-backed content and attribute changes, work with media and list operations, and respond to editor lifecycle events.
A schema-driven custom block handler system can add frontend editing support for compatible custom Gutenberg blocks without changing the plugin core. Custom handler support is experimental and has not been tested with every block library or implementation. A block provider must register its client-side attributes and save implementation on the editable frontend page; editor-only provider bundles are not compatible.
Set up the team workflow
Install FrontEdit Pro on the WordPress site where supported Gutenberg content is managed. Review user permissions and editing controls, then decide how the team will handle drafts, approvals, requests, history, and the Content Catalog. Developers can use the included runtime extension documentation for API methods, events, supported behavior, versioning, and integration guidance.