Edit supported blocks on the live page

FrontEdit Pro is the paid edition of FrontEdit, a frontend editor for existing Gutenberg content. Logged-in visitors who have permission to edit a page can select supported blocks where they appear, make changes in context, and save. FrontEdit updates block content and attributes while preserving the block structure, styling, options, and standard WordPress serialization.

Supported blocks include Paragraph, Heading, List, Code, Details, Preformatted, Pullquote, Table, Verse, Image, Audio, Cover, File, Media & Text, Video, Button, Icon, and Accordion Heading. Editing options vary by block. FrontEdit also supports publicly viewable custom post types that use the block editor and shop editable blocks in standard post content. It does not edit every block or arbitrary page content, including custom-field values, flexible-content layouts, block-bound post meta, or third-party page-builder layouts.

Review and coordinate team edits

Teams can route proposed changes through pending drafts and approval workflows. Administrators can set editing permissions for clients and contributors, then select per user whether they may edit several blocks in one session or must work on one block at a time. Batch editing is available in FrontEdit to users with editing access; Pro includes the per-user controls.

• Drafts and approvals: Review proposed changes before treating them as completed content updates.
• Content requests: FrontEdit Base sends block-linked requests to the administrator by email. Pro adds a centralized workflow to track, respond to, close, and search those requests.
• Content Catalog: Review editable components across the site from one content management area.
• Block history: Review earlier changes and use the available revert workflow when needed.
• Dashboard and notifications: Bring open requests and pending drafts together for editorial follow-up.

Developer integrations

FrontEdit provides public JavaScript and PHP APIs for integrations with its editing, draft, rendering, and operation workflows. The JavaScript API documents supported editor operations, inputs, events, runtime behavior, and versioning. A schema-driven custom block handler system can extend front-end editing to compatible custom Gutenberg blocks without changing the add-on core.

Custom handler support is experimental and has not been tested with every block library or implementation. A third-party block is compatible only when its provider registers the block's client-side attributes and save implementation on the editable frontend page. Editor-only provider bundles are not compatible.