Frontman - AI Website Editor
| 开发者 | frontmanai |
|---|---|
| 更新时间 | 2026年8月18日 23:12 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0.2 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
Frontman is an AI editor for an existing WordPress site. Open Frontman from the WordPress admin menu, keep the page visible, and describe the result that you want. Frontman can inspect supported WordPress structures, make the change, and refresh the preview for your review.
Use Frontman for focused site updates without hunting through page builders, theme screens, menus, widgets, and settings.
安装:
- Download the Frontman plugin release ZIP or upload the
frontman-agentic-ai-editorfolder to/wp-content/plugins/ - Activate the plugin through the Plugins menu
- Open Frontman from the WordPress admin menu (you must be logged in as an admin)
- Sign in to Frontman at
api.frontman.shwith GitHub or Google when prompted - Reopen Frontman from the WordPress admin menu if Frontman does not redirect you back automatically
- Connect an AI provider with OAuth or add an API key
- Start describing WordPress edits beside the live preview
屏幕截图:
常见问题:
What do I need before my first task?
You need administrator access, a Frontman account, and a supported AI provider connected with OAuth or an API key. Frontman does not include model access. You do not need another server.
What can Frontman change?
Current tools support posts, pages, Gutenberg blocks, menus, templates, template parts, widgets, allowlisted settings, Additional CSS, Elementor content, and WooCommerce data.
Does Frontman work with every theme?
No. Support depends on the structure that controls the rendered page. Custom themes, plugins, hosting controls, and unsupported builders can require another workflow.
Can I use Frontman in production?
Frontman can run on production, but it is early-access software. Start on staging, keep a current backup, and review each change.
What data is sent to Frontman AI?
The hosted service processes your prompts, relevant site or store content, tool results, and task history. It sends request context to your selected AI provider. See Third-Party Services and the Privacy Policy below.
更新日志:
3.1.0
- Sync the Frontman plugin release with Frontman v3.1.0
- See the GitHub release notes for the full cross-product changelog
- Sync the Frontman plugin release with Frontman v3.0.0
- See the GitHub release notes for the full cross-product changelog
- Sync the Frontman plugin release with Frontman v2.0.0
- See the GitHub release notes for the full cross-product changelog
- Sync the Frontman plugin release with Frontman v1.4.0
- See the GitHub release notes for the full cross-product changelog
- Keep the WordPress plugin aligned with the Frontman v1.3.0 release train.
- Refresh WordPress.org listing metadata, including the tested WordPress version, to keep the plugin page current for new installers.
- Improve plugin-directory search copy around AI WordPress editing, live preview editing, Elementor editing, and WooCommerce store management.
- Add clearer FAQ entries for AI page editing, Elementor support, WooCommerce tools, and the live preview workflow.
- Improve screenshot captions so users can understand the AI editor, live preview, visual selection, and WooCommerce editing workflow before installing.
- Improve WordPress.org listing copy for non-developer WordPress teams.
- Position Frontman more clearly as an AI website editor for marketers, content teams, support teams, store operators, and agencies.
- Highlight practical editing workflows for pages, posts, Gutenberg blocks, Elementor pages, WooCommerce data, menus, templates, widgets, settings, and Additional CSS.
- Clarify the live preview workflow so users know they can review site changes beside the AI editor.
- Expand safety and third-party service details so administrators understand access controls, data flow, and recommended staging-site use before using AI editing on important sites.
- Update WordPress.org listing copy for non-developer WordPress teams
- Position Frontman as an AI website editor for marketers, content teams, support teams, store operators, and agencies
- Highlight live preview editing, visual selection, Elementor support, WooCommerce tools, safety controls, and third-party data handling
- Launch Frontman for WordPress as a self-contained AI editing plugin
- Add native tools for posts, pages, blocks, Elementor, WooCommerce, menus, templates, widgets, safe options, and Additional CSS
- Run WordPress, Elementor, and WooCommerce tools directly inside the PHP plugin
- Improve safety with admin-only access, nonces, sanitized inputs, allowlisted options, and safer CSS validation
- Strengthen WordPress source-of-truth guidance for Elementor and theme edits
- Fix WordPress admin menu icon alignment
- Improve Elementor mutation schemas so empty add-element, update-settings, full-page-data, and generated-child payloads are rejected before they reach Elementor
- Preserve existing WordPress page templates when saving or rolling back Elementor page data, and report any template side effect in Elementor tool responses
- Add WooCommerce tools for products, orders, customers, shipping, taxes, coupons, reports, settings, system status, and store data when WooCommerce is active
- Improve Elementor editing tool guidance and recovery errors for non-empty settings diffs and full-tree updates
- Align plugin metadata and release packaging for the next WordPress.org build
- Align plugin dependencies with the Frontman v0.17.0 maintenance release
- Keep WordPress package metadata current with the shared client and framework packages
- Fix image attachment uploads for WordPress media replacement workflows
- Strengthen Elementor rollback safety for precise widget and HTML-fragment edits
- Add Elementor selected-element context so Frontman can inspect and edit Elementor-backed selections more directly
- Add a WordPress media upload workflow that resolves user-provided images into Media Library attachments for posts and Elementor elements
- Preserve previous Elementor data as private rollback snapshots when updating, removing, or replacing Elementor content
- Fix WordPress page duplication so Elementor page metadata and post-backed navigation item metadata are preserved
- Run WordPress Elementor edits serially and route target metadata deterministically between settings edits and HTML-fragment edits
- Fix WordPress Playground relay requests so scoped tool calls and source-location POSTs keep the leading
/scope:...path prefix - Improve transient error handling in the shared Frontman UI with categorized errors, automatic retry, retry countdowns, and a manual retry button
- Keep WordPress editing sessions more reliable when network or relay requests fail temporarily
- Bump package versions for a maintenance release across the Frontman workspace
- Bump package versions for a maintenance release across the Frontman workspace
- Add production-ready WordPress support with PHP-native filesystem tools and plugin ZIP release packaging
- Add safer mutation history snapshots for WordPress editing tools
- Add richer WordPress editing tools for menus, blocks, templates, and cache workflows
- Require confirmation before destructive delete tools run
- Preserve freeform HTML during block mutations and limit widget mutations to supported safe widget types
- Remove the old standalone package and release flow from normal WordPress plugin operation
- Send the WordPress runtime nonce on plugin tool POST requests from the shared client
- Keep the WordPress plugin metadata aligned for the next release
- Remove the standalone package and remaining standalone references from the WordPress flow and release tooling
- Show a first-use caution warning reminding users to use backups and review experimental changes carefully
- Preserve freeform HTML while mutating blocks so block edits do not silently drop non-block content
- Restrict widget mutations to the supported safe widget types instead of generic direct option writes
- Add tests for the new menu, block, widget, template, and cache tools plus delete-confirm flows
- Add WordPress-native menu, block, widget, template, and cache tools that remove more admin tasks from the browser UI flow
- Require explicit confirmation for destructive WordPress delete tools before they run
- Capture pre-edit snapshots for the new mutating WordPress tools so tool history preserves the previous state
- Add
wp_create_menu_itemso the agent can add navigation links directly through WordPress tools - Include pre-edit snapshots in menu item creation and update flows
- Include the prior asset state in mutating WordPress tool results so edit history captures what changed
- Add PHP mutation snapshot tests for posts, blocks, menus, options, and widgets
- Remove the extra server dependency from the WordPress plugin and release ZIP
- Run all normal file tools entirely inside the PHP plugin runtime
- Clear PHP file-tracker state on deactivate and uninstall
- Move the core filesystem tools into the WordPress plugin itself and stop relying on the Bun standalone for normal file operations
- Add PHP tests for the local core tool implementations
- For Lighthouse bootstrap, prefer using the bundled standalone binary as the Bun CLI before falling back to system Bun or installing Bun
- Prepare Bun and Lighthouse runtime dependencies only when the
lighthousetool is called, with the WordPress plugin performing the bootstrap before proxying the audit
- Detach bundled standalone startup more cleanly with
setsid/stdin redirection to avoid tying the process to the originating web request
- Fix bundled standalone cleanup paths when Frontman classes are loaded during uninstall without bootstrap constants
- Install Bun on startup when needed and run
bun installfor standalone Lighthouse runtime dependencies
- Make
search_filesavoid Git fallback outside Git repositories and use plain filesystem search instead
- Improve plugin lifecycle cleanup during uninstall and deactivation
- Improve plugin deactivation cleanup
- Improve WordPress production tooling support
- Add plugin-side runtime logs for debugging tool execution
- Let
list_fileswork outside Git repositories for typical WordPress hosting setups
- Improve file tool behavior on restrictive WordPress hosting setups
- Improve release packaging for the WordPress plugin
- Initial release
- 19 WordPress tools: posts, blocks, menus, options, templates, widgets
- File tools for theme and site editing
- Admin-only access with cookie-based authentication
- Settings page for API configuration
- Dev mode for local development