frontman-ai

Watch Frontman in action:
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/-4GD1GYwH8Y?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
Learn more on the <a href="https://frontman.sh" rel="nofollow ugc">Frontman Website</a>.
Frontman puts an AI agent beside a live view of your site. Open <code>/frontman</code>, describe the change you want, and the agent takes action with built-in tools while you review the result in context.
Frontman is closer to an editor than a chatbot or content generator. It is built for real editing tasks: updating content, changing blocks, adjusting Elementor pages, managing menus, inspecting templates, changing safe site options, and working with WooCommerce data when WooCommerce is active.
No code editor. No terminal. Just an AI agent workflow alongside a live page preview.
What the agent can do:
<ul>
<li>Create, edit, and delete posts and pages</li>
<li>Insert, update, and rearrange Gutenberg blocks</li>
<li>Edit Elementor pages with Elementor-aware tools and versioning</li>
<li>Manage WooCommerce products, orders, customers, coupons, shipping, taxes, reports, settings, and store data when WooCommerce is active</li>
<li>Update navigation menus and menu items</li>
<li>Read and change safe site options such as title, tagline, permalinks, and homepage settings</li>
<li>Inspect and update Additional CSS for the active theme</li>
<li>Browse block templates, template parts, widgets, and theme settings</li>
</ul>
The important part is the feedback loop. The AI agent can change the site, then you can see the result in the same workflow instead of jumping between admin screens and browser tabs.
Who it’s for:
Developers who want faster iteration. Designers and content editors who want to make changes without opening an IDE. Store owners and site managers who would rather describe the task than dig through admin screens.
Open source:
The Frontman plugin is open source under GPLv2 or later. The code is available on <a href="https://github.com/frontman-ai/frontman" rel="nofollow ugc">GitHub</a>.
Early release – help us improve it:
This is an experimental release. It works, but it hasn’t been tested across every theme, page builder, and hosting setup. We’re looking for users to try it and share feedback. <a href="https://github.com/frontman-ai/frontman/issues" rel="nofollow ugc">Open an issue</a> or join the conversation on GitHub.
<h3>Third-Party Services</h3>
This plugin connects to external services provided by Frontman AI:
Frontman Client (app.frontman.sh) 
The chat interface is loaded from <code>https://app.frontman.sh</code>. This serves the JavaScript and CSS that power the in-browser UI.
<ul>
<li>Service URL: <a href="https://app.frontman.sh" rel="nofollow ugc">https://app.frontman.sh</a></li>
<li>Provider: Frontman AI</li>
<li>Privacy Policy: <a href="https://frontman.sh/terms" rel="nofollow ugc">https://frontman.sh/terms</a></li>
</ul>
Frontman API (api.frontman.sh) 
The plugin connects via WebSocket to <code>wss://api.frontman.sh</code> for AI agent communication, sending tool results and receiving agent responses. Your site content and, when you use WooCommerce tools, store data such as products, orders, customers, coupons, reports, and settings are sent to this service when the agent processes requests.
<ul>
<li>Service URL: <a href="https://api.frontman.sh" rel="nofollow ugc">https://api.frontman.sh</a></li>
<li>Provider: Frontman AI</li>
<li>Privacy Policy: <a href="https://frontman.sh/terms" rel="nofollow ugc">https://frontman.sh/terms</a></li>
</ul>
AI Model Providers 
The Frontman API routes requests to third-party AI model providers (such as Anthropic and OpenAI) to generate responses. Content from your site may be included in prompts sent to these providers.
Loading the Frontman UI requests hosted client assets. Your site content is not sent to the Frontman API or model providers until you actively use the chat interface and submit a message.

Frontman – Agentic AI Editor

AI agent that edits posts, blocks, Elementor pages, WooCommerce data, menus, templates, and site options beside a live preview.

Weston Ruter

In WordPress 4.5 the <a href="https://make.wordpress.org/core/2016/02/16/selective-refresh-in-the-customizer/" rel="nofollow ugc">selective refresh</a> framework was introduced in core. One of the key concepts in this framework is the “partial”, the region in a document which is selectively refreshed when a related setting is modified. This means that one or more settings are linked with a given element in the preview. When selective refresh was first was introduced it supported the ability for a user to “shift click” on a partial to jump to and focus on the related control in the pane. In WordPress 4.7 this was then enhanced with <a href="https://make.wordpress.org/core/2016/11/10/visible-edit-shortcuts-in-the-customizer-preview/" rel="nofollow ugc">visible edit shortcuts</a> so that users could click (touch even) on the icon to be able to reveal the control in the pane.
The Customize Inline Editing plugin builds on edit shortcuts by allowing the setting to be modified inline via direct manipulation in the preview without having focus removed and placed on the controls pane. This is particularly useful on mobile devices on small screens where a user cannot both see the controls and preview at the same time, as can be compared here:
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/w7WfSEtT8pc?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
Inline editing in this way is also helpful for accessibility since keyboard focus remains in the preview at the element being edited, as can be seen in this demonstration of inline editing on a desktop browser:
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/KesM3vo5WyE?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
This plugin provides one example implementation of inline editing this can be accomplished in the customizer. Version 0.1 of this plugin from 2014 was a precursor in some ways to selective refresh, specifically in regards to how CSS selectors are associated with customizer settings.
Themes can opt-in to support this plugin’s inline editing within the customizer by assigning the appropriate type to the registered partials:
<pre>
add_action( 'customize_register', function( $wp_customize ) {
 $opt_in_partials = array_filter( array(
 $wp_customize->selective_refresh->get_partial( 'blogname' ),
 $wp_customize->selective_refresh->get_partial( 'blogdescription' )
 ) );
 foreach ( $opt_in_partials as $partial ) {
 $partial->type = 'inline_editable';
 }
}, 100 );
</pre>
Click on the edit shortcut to begin editing the element, with keyboard focus then given to the editable element. If the value has a server-side rendered value (e.g. where PHP filters like <code>wptexturize</code> apply to improve typography), the raw value will be supplied when editing starts. Editing can be completed by clicking out of the editable element, tabbing out of the element (blurring it), or clicking the edit icon which then appears as a “done” checkmark icon. You may also shift-click on an element to edit it.
Currently only basic text fields can currently be edited; styling and any tags added to <code>contentEditable</code> areas will be stripped out. Eventually rich text formatting may be allowed, specifically for integrations with the Text widget (via <a href="https://github.com/xwp/wp-js-widgets" rel="nofollow ugc">JS Widgets</a>) or post content (via <a href="https://github.com/xwp/wp-customize-posts" rel="nofollow ugc">Customize Posts</a>).
The <a href="https://make.wordpress.org/core/2016/02/16/selective-refresh-in-the-customizer/" rel="nofollow ugc">selective refresh</a> writeup from 4.5 concludes with a section on a possible future for it and inline editing:
<blockquote>
If we can eliminate full-page refreshes from being the norm for the Customizer, we can start to introduce controls inline with the preview. If the entire preview does not reload, then the inline controls won’t get destroyed by the refresh with each change. For example, consider a widget control floating immediately next to the widget in the sidebar it is editing. With selective refresh, it will then also be possible to eliminate the Customizer altogether. The Customizer could be available to anyone who is logged in, with the controls being bootstrapped on demand when a user wants to edit a given element. There would be no need to navigate way from a page on the frontend to enter a unique Customizer state: the Customizer would come to the user. Any controls not relevant to being inline could remain in the Customizer pane, but it could slide in only as needed instead of appearing by default. That is to say, selective refresh makes the Customizer a much better framework for implementing frontend editing.
</blockquote>
Development of this plugin is done <a href="https://github.com/xwp/wp-customize-inline-editing" rel="nofollow ugc">on GitHub</a>. Pull requests welcome. Please see <a href="https://github.com/xwp/wp-customize-inline-editing/issues" rel="nofollow ugc">issues</a> reported there before going to the <a href="https://wordpress.org/support/plugin/customize-inline-editing" rel="ugc">plugin forum</a>.

Customize Inline Editing

Makes the whole text editing process smooth. From refresh to postMessage to inline editing awesome transition. Keep up the good work :)



Awesome

Demonstration of how inline editing can be implemented in the customizer.

Frontman – Agentic AI Editor vs Customize Inline Editing