FrontEdit - Live Frontend Block Editor

Why FrontEdit? Most websites don't need a new page builder. They need a faster way to edit the blocks that already make up their pages. FrontEdit lets trusted users click directly on headings, paragraphs, images, buttons, lists, tables, and other supported content where it appears on the live page, make their changes in context, and save them through a focused frontend editing experience. For site owners and marketing teams, that means faster everyday updates with less WordPress training. For agencies and freelancers, it means fewer routine support requests and a safer way to hand content ownership to clients. FrontEdit works with native Gutenberg blocks rather than replacing them or editing only the rendered HTML. It updates supported block content and attributes while preserving the original block structure, styling, settings, and standard WordPress serialization. 🎮 Try the interactive demo 🔓 Explore FrontEdit Pro At a glance

• ✏️ Edit Gutenberg blocks where they appear on the live page
• ⚡ Make routine text, image, button, list, table, and media updates faster
• 🛡️ Preserve Gutenberg block markup, styling, and block-specific settings
• 👥 Give clients and team members a simpler alternative to navigating wp-admin
• 📉 Reduce routine support requests and accidental layout changes
• 🔌 Build custom integrations with the Public JavaScript API and extend block compatibility through custom handlers
• 🚀 Add drafts, approvals, permissions, batch editing, and more with FrontEdit Pro

Developer Friendly

• Build on top of FrontEdit. A stable Public JavaScript API lets plugins, custom tools, and AI assistants discover editor capabilities and safely perform the same block editing operations used by FrontEdit itself.
• Extend block compatibility. A schema-driven custom block handler system makes it possible to add frontend editing support for custom Gutenberg blocks and third-party block libraries without modifying the plugin core.

FrontEdit brings content editing to the place it belongs: the frontend. WordPress is powerful, but for everyday content updates it often asks too much of the people actually doing the work. Clients get lost in wp-admin. Teams bounce between the page preview and the editor. Small copy changes turn into support requests. Agencies spend valuable time handling edits their clients should be able to make themselves. FrontEdit changes that. Instead of sending users into the dashboard to hunt through blocks, sidebars, and settings panels, FrontEdit lets trusted users click directly on the content they want to change and edit it right on the page. Headlines, paragraphs, lists, buttons, media, and more become part of a guided frontend workflow that feels natural, lightweight, and immediate. FrontEdit complements Gutenberg by bringing block editing directly to the frontend. Whether you manage your own website, run content updates for a business, or maintain dozens of client sites, FrontEdit creates a new kind of WordPress workflow: faster, clearer, and dramatically easier to delegate. Why It Matters Most content edits are simple. They are not redesigns. They are not full page rebuilds. They are things like:

• Updating a headline after a campaign changes
• Rewriting a paragraph on a service page
• Swapping an image or fixing a button label
• Refreshing lists, pricing copy, FAQs, and promotions
• Letting a client suggest or submit changes without risking layout damage

These edits happen constantly, but traditional WordPress workflows make them slower than they should be. FrontEdit removes the friction. Your content can be updated in context, on the live page, with far less training and far less back-and-forth. Every edit preserves the original WordPress block markup and block-specific settings. FrontEdit updates only the content you change, allowing supported blocks to retain their existing configuration, styling, and behavior. ✨ Key Features

• Edit WordPress blocks directly on the frontend
• Click content exactly where it appears on the page
• Preserve block markup, styling, and block-specific settings
• Supports text, images, tables, buttons, media, and more
• Built for Gutenberg's normal block serialization
• Lightweight editing experience designed for trusted users
• Includes content request workflows for editorial collaboration
• Public JavaScript API for custom integrations and AI workflows
• Extensible custom block handler system for third-party blocks

👥 A Better Workflow For Real Teams FrontEdit is ideal for:

• Business and site owners who want to make quick updates themselves
• Marketing teams that need to keep landing pages, service pages, and calls to action current
• Internal staff who should be able to edit content without learning WordPress admin
• Freelancers and agencies that want to give clients safe, straightforward content ownership
• Maintenance teams that are tired of spending time on small text and image changes

For agencies, the value is especially clear. Instead of fielding routine requests like "change this sentence," "swap this image," or "update this CTA," you can give clients a workflow they can actually use with confidence. That means fewer support tickets, fewer admin walkthroughs, fewer accidental layout changes, and more time spent on higher-value work. How It Works

1. Install and activate FrontEdit.
2. Open a page on the frontend while logged in.
3. Click supported content directly on the page.
4. Edit in place and save using a workflow designed to respect WordPress block content.

The result is a familiar page view combined with a purpose-built editing layer that keeps the experience simple for the person making the change. FrontEdit focuses on the block types people edit every day, with support continuing to expand over time. Developers can also extend compatibility using the included custom block handler system. Supported Blocks FrontEdit currently supports a growing set of WordPress blocks. WordPress Core Text blocks

• Paragraph (core/paragraph)
• Heading (core/heading)
• List (core/list)
• Code (core/code)
• Details (core/details)
• Preformatted (core/preformatted)
• Pullquote (core/pullquote)
• Table (core/table)
• Verse (core/verse)
• Accordion Heading (core/accordion-heading)

Media blocks

• Image (core/image)
• Audio (core/audio)
• Cover (core/cover)
• File (core/file)
• Media & Text (core/media-text)
• Video (core/video)
• Icon (core/icon)

Design blocks

• Button (core/button)

Experimental: Custom Block Handlers FrontEdit includes an experimental custom handler system that allows developers to add frontend editing support for their own custom blocks and third-party block libraries. This feature is intended for developers who want to extend the plugin beyond the blocks officially supported out of the box. Using the provided documentation and handler templates, it may be possible to add support for many custom block types without modifying the core plugin. Important: Custom handler support is currently experimental. While the underlying system is designed to be flexible, it has not been tested against every block library or custom block implementation. Some blocks may work immediately, some may require additional configuration, and others may expose limitations that have not yet been identified. Before creating custom handlers, please review the included templates/frontedit-live-block-editor-custom-handlers/README.md documentation carefully. It contains implementation requirements, supported capabilities, limitations, and important guidance for building compatible handlers. Community feedback is highly encouraged. If you successfully add support for a block, or if you encounter a block that follows the documented schema requirements but still does not behave correctly, please let us know. Real-world testing helps improve the schema system and expand compatibility over time. If you've built a reliable handler for a popular third-party block library, you're welcome to submit it for consideration. After internal testing and validation, compatible handlers may be included in future releases as officially supported integrations. Built For Gutenberg, Not Against It FrontEdit is designed to work with block content while preserving the standard save behavior WordPress expects. It keeps the normal block serialization flow intact so supported content can be edited predictably and safely. That means the plugin is not trying to bypass WordPress. It is using WordPress more intelligently for the kinds of edits people make every day. 🛡️ Safety That Protects Real Work Frontend editing has to be convenient, but it also has to be safe. FrontEdit helps protect editors from two of the most common content workflow problems:

• Post-lock protection: When another user is actively editing a post, FrontEdit identifies the owner before live changes can be applied, and requires an explicit takeover before continuing.
• Unsaved changes warnings: It is easy to accidentally click away, reload, or navigate to another page in the middle of an edit. FrontEdit warns you before you lose unsaved work.
• Overwrite protection: If another user updates the page after you started editing, FrontEdit can warn you before you save over newer changes.

These details matter because they build confidence. Editors can work faster when they know the plugin is helping protect their changes. Extensible By Design One of the long-term strengths of FrontEdit is that it is being built to grow with the modern block ecosystem. Developers can write their own handlers for custom blocks and third-party blocks, making it possible to extend frontend editing support beyond the blocks included out of the box. That opens the door for deeper compatibility with block collections and custom site builds while keeping the editing experience consistent for end users. The goal is simple: make it easier to bring more of WordPress into a frontend editing workflow without forcing every site into the same setup. 🧩 Developer API FrontEdit includes a stable JavaScript Public API for developers who want to integrate with or extend the frontend editing experience. The versioned Public API provides documented runtime contracts for interacting with the editor, inspecting supported blocks, applying schema-backed content and attribute updates, working with media and list operations, responding to editor lifecycle events, and building integrations designed for long-term compatibility. Whether you're building custom editing tools, AI-powered workflows, or integrations with your own plugins, the Public API is the recommended way to interact with FrontEdit at runtime. The complete API reference is included with the plugin in docs/frontend-runtime-extension-contract.md, which documents the available methods, events, supported runtime behavior, versioning guarantees, and integration guidelines for developers. 🔓 Pro Features When You Need More FrontEdit works great on its own, but some teams need more than direct frontend editing. When your workflow grows, FrontEdit Pro expands the experience into a more complete editorial system. With Pro, you can unlock advanced features such as:

• Pending drafts and content approval workflows
• Batch editing for faster multi-block updates
• Per-user editing permissions for more controlled client access
• Content request ticketing and dashboard tools to track and respond to user submitted change requests
• Truly centralized content management with a Content Catalog for reviewing editable elements across the site
• Block-level edit history and revert workflows
• Notification tools for more collaborative editorial operations
• A dashboard to see open content requests and pending drafts in one place

👉 See everything included in FrontEdit Pro 🚧 Roadmap The FrontEdit experience is only getting bigger. Planned future enhancements include more advanced page editing behavior such as moving blocks, deleting blocks, adding new blocks, and working toward fuller page editing workflows directly from the frontend. These more advanced editing controls are planned as Pro features, giving Pro users an even more powerful way to manage page content without dropping into the admin editor. 🤖 Coming Soon: ABE, Your Personal WordPress Assistant AI is changing the way people work, but most AI tools still feel disconnected from WordPress. They generate text in a chat window and leave you to figure out where it goes, how it should be formatted, and how to safely apply it. That is where ABE comes in. ABE, the AI Assisted Block Editor, is being built specifically for WordPress and FrontEdit. It is not meant to be a generic chatbot. It is designed as your personal WordPress assistant: one that understands editable page content, works with FrontEdit-owned blocks, and helps rewrite, generate, and update content live on the page in front of you. The vision is simple: describe what you want, review the result in context, and watch WordPress content update in a workflow that feels native instead of bolted on. 🚀 ABE will be included with the Pro subscription at no additional cost, making Pro not just a workflow upgrade, but a forward-looking investment in how WordPress editing is about to change. Join the ABE waitlist here to get updates and be notified when ABE launches: Sign up here

1.0.10

• Adds support for WordPress Icon blocks.
• Opens the live editor immediately while post-lock verification continues safely in the background.

1.0.05

• Improved multi-element action-bar positioning for directly hovered nested and overlapping blocks.
• Fix action bar hover transfer across overlapping blocks.
• Added authorized AI discovery for editable blocks and read-only block content, plus public live-page block enumeration for browser integrations.

1.0.02

• Added Base previews for the Pro Content Requests and Content Catalog admin screens.
• Added WordPress-native post locking for live editing, including an active-editor notice and optional takeover flow.

1.0.0

• Initial public 1.0.0 release for the WordPress plugin repository.