FrontEdit Pro: Team Workflows for Gutenberg Editing

Team processes for live Gutenberg editing

FrontEdit Pro adds editorial tools to FrontEdit, which lets users with permission edit supported Gutenberg content directly on a live WordPress page. They can update headings, paragraphs, pictures, buttons, lists, tables, and other supported blocks in context. FrontEdit changes supported block content and attributes while preserving the block structure, styling, options, and standard WordPress serialization.

Batch editing is available in FrontEdit to users with editing access. With Pro, an administrator can set which users may edit several blocks in one session and which must work on one block at a time.

Review and coordinate content changes

Pro brings requests and proposed edits into team workflows. Pending drafts can go through review and approval before changes are treated as completed updates. Administrators can set editing permissions for clients and other contributors.

• Content request ticketing to track, respond to, close, and search user-submitted requests. In FrontEdit Base, block-linked requests go to the administrator by email.
• A Content Catalog for reviewing editable components across the site.
• Block-level edit history and revert workflows.
• Notifications and a central dashboard for open requests and pending drafts.

Supported content and its limits

Supported WordPress blocks include Paragraph, Heading, List, Code, Details, Preformatted, Pullquote, Table, Verse, Image, Audio, Cover, File, Media & Text, Video, Button, Icon, and Accordion Heading. Available editing operations depend on the block. FrontEdit does not edit every block or arbitrary page content.

Eligible publicly viewable custom post types are supported when they use the WordPress block editor and shop editable blocks in standard post content. Editing applies to that main content area. FrontEdit does not edit custom-field values, flexible-content layouts, block-bound post meta, or third-party page-builder layouts.

Editing safeguards and integrations

Each block keeps its own active editing session and undo history, so users can move between blocks while retaining edits in progress. FrontEdit also offers post-lock protection, warns before users leave with unsaved changes, and can warn when another user has updated the page since editing began.

Developers can use the public JavaScript and PHP APIs to create integrations with authorized editor capabilities and supported editing operations. A schema-driven handler system can extend editing to compatible custom Gutenberg blocks without changing the plugin core. Custom handler support is experimental; a block provider must register the block’s client-side attributes and save implementation on the editable front end. Editor-only provider bundles are not compatible.