內容簡介
MJC Designs AI Design Assistant for Bricks Builder 是一款專為 Bricks Builder 設計的 WordPress 外掛，利用 AI 提供頁面修改建議，讓使用者在應用變更前進行審核。它提供獨立的 HTML 和 CSS 工作區，方便用戶進行草稿編輯和預覽。
【主要功能】
• 列出可編輯的 WordPress 頁面和 Bricks 模板
• 支援多種 AI 提供者模型選擇
• 使用 JPG、PNG 或 WebP 參考圖片
• 生成靜態 HTML 和 CSS 草稿
• 提供即時的前端預覽功能
外掛標籤
開發者團隊
② 後台搜尋「MJC Designs AI Design Assistant for Bricks Builder」→ 直接安裝（推薦）
原文外掛簡介
MJC Designs AI uses the WordPress AI Client and configured provider models to propose Bricks page changes for your review before applying them. Its optional Style Manager guides designs in the Main Workspace and Content to Pages Workspace with browser-session colors and variables. On selected WordPress pages, an optional Page SEO editor can save supported Yoast SEO or AIOSEO fields and the WordPress slug after explicit review, or move an eligible page to recoverable WordPress Trash after confirmation. Main and Content to Pages can create a draft page manually. The HTML and CSS workspace creates drafts for manual pasting into Bricks. Content to Pages also extracts final copy from DOCX or text-based PDF files, creates WordPress draft pages, prepares separate Bricks designs for review, and can edit existing Bricks templates. The plugin is independent of Bricks Builder, Yoast SEO, and AIOSEO; it is not affiliated with or endorsed by their developers. This alpha release is for evaluation: review each proposal and keep a backup before applying changes.
Visit the MJC Designs AI YouTube channel. The About subpage also links to video tutorials and updates. YouTube content is not loaded in the plugin page.
Requirements
WordPress 7.0 or later with the WordPress AI Client.
A compatible AI provider integration installed and configured under Settings > Connectors.
Bricks 2.4 or later, with get-page-elements, set-page-elements, and get-element-schema abilities enabled under Bricks > AI > Abilities.
PHP 7.4 or later.
PHP Zip and XML extensions for DOCX extraction, and zlib for compressed PDF text in Content to Pages.
Features
List editable WordPress pages and Bricks templates, including pages without existing Bricks elements. Blog posts are not available for editing.
Use the plus icon beside Bricks Document in Main Workspace or Content to Pages to create one ordinary WordPress draft page with a title, unique slug, and optional supported SEO details. The new draft is selected automatically. Unfinished form details stay in this browser tab, and a styled prompt appears before changing pages or leaving. The Main Workspace can apply reviewed designs to drafts and publish saved designs with a separate confirmation. Content to Pages still needs matching uploaded copy before generating a design.
Select among compatible AI provider models configured through WordPress Connectors; the user’s model preference is saved to their account.
Use compatible vision models with optional JPG, PNG, or WebP reference images up to 5 MB.
Choose up to five existing WordPress Media Library images for placement in proposed Bricks designs, or reserve image placeholder blocks when none are selected. Selected image titles, alternative text, dimensions, and IDs are sent to the chosen AI provider; image files are not sent by this feature.
Read the selected page’s element tree and propose focused edits. Validate setting names and choices against the live Bricks control schema before preview or apply. For registered gradient controls, the angle is stored as a unitless numeric string from 0 to 360 (for example “90”, not “90deg”).
Change only registered native Bricks controls. AI proposals cannot write code controls or Custom CSS.
Choose one of five plugin interface color themes from the header in any workspace. The choice lasts only in the current browser tab and does not change Bricks page colors or Style Manager palettes.
Keep the Main Workspace conversation for each selected Bricks document in the current browser tab until it closes. Use the same Generate Design and Refine Design action styling across the three workspaces. Each workspace header has a Quick Guide button; the guide also appears automatically when no compatible provider is connected.
Name one other editable page in a Main Workspace or Content to Pages prompt, such as “match this page to the About page”, to use a compact summary of its native Bricks layout and style settings as a reference. Only the selected page can receive proposed changes; its copy stays its own.
When an unattended workspace finishes or fails a design request, mark its browser tab title with an unread count. Enable optional desktop alerts from the workspace header; they require browser permission and a secure connection. The tab must stay open until the request ends.
Generate and refine static HTML and CSS drafts in up to five browser-session chats. Use code tabs, line wrapping, responsive previews, fullscreen controls, an adjustable conversation area, and a vertically resizable design request field. Copy drafts into Bricks manually; this workspace does not save a page or execute generated scripts.
Use optional Style Manager in the Main Workspace and Content to Pages Workspace to guide designs with shared colors, variables, and fluid scales for this browser tab. Import or export Bricks palette and variable JSON, then import the exported styles into Bricks before generating. The assistant checks that saved names exist in Bricks and pauses with an import reminder when they are missing. It uses compatible names in registered controls where suitable, while explicit fixed values and color directions take priority. Style Manager does not write global Bricks settings and does not apply to the HTML and CSS workspace.
Use Content to Pages to extract a DOCX or text-based PDF copy file up to 50 MB, set brand colors, create draft pages, and review a separate native Bricks design for each page. Use Page: Title or Word Heading 1 to identify pages. DOCX extraction retains common bold, italic, and safe links for design proposals; the extracted-copy preview is plain text. PDF extraction groups readable text where possible but does not preserve styling or links; image-only scans and unsupported encodings may require another export. The planner can skip existing page titles after confirmation, use up to five selected Media Library images, or reserve labeled image placeholders. The site’s PHP upload limit may be lower than 50 MB.
When returning to Content to Pages in the same browser tab, choose whether to continue any saved planner settings, chat, or enabled Style Manager settings, or start a new session. Starting new clears those browser-session settings, including Style Manager, but leaves WordPress pages unchanged. Re-upload the copy file to continue, because the plugin does not save the file or extracted text. Generate Drafts appears after planner settings are saved and stays unavailable until copy is extracted.
Refine a selected section or the overall Content to Pages layout through a reviewed Bricks proposal. The AI can regroup native elements while preserving the planner rules and final page copy.
Select an editable page or existing Bricks template in Content to Pages. Page drafts remain drafts after design changes, and publishing a page requires a separate confirmation and permission. Templates use the user’s prompt and saved planner settings when available; naming an existing page in the prompt can supply its Bricks layout and matching uploaded copy as reference without editing that page. Use Page SEO to review and apply supported Yoast SEO or AIOSEO page details; the editor does not change Bricks templates or template conditions. Saved colors and instructions stay in the current browser tab until it closes. The plugin does not save uploaded copy files or extracted text as a WordPress project or in browser session storage; re-upload the copy after leaving or reloading the workspace.
Use Page SEO on selected WordPress pages in Main Workspace or Content to Pages to review supported Yoast SEO or AIOSEO fields and the WordPress slug. Closing with X or Escape keeps unsaved inputs. Cancel discards them and restores the saved page values. The editor asks before switching pages or leaving. It displays fields supported by the active tool and account, with a preview whose length bars are estimates. Changing a published slug requires confirmation and may need a redirect. Content to Pages can suggest labeled SEO details from uploaded copy and save them to one active supported SEO tool on a newly generated draft; later edits require Apply. Page SEO warns when both SEO tools are active. If you can delete the selected page, Move to Trash asks for confirmation and shows a loading panel before refreshing the workspace. WordPress Trash must be enabled; the page can be restored until Trash is emptied. This action is unavailable for Bricks templates and the HTML and CSS workspace.
Page SEO rejects a changed slug already used by another saved page, including a draft. Content to Pages can still generate drafts with imported slugs; Publish page in either workspace blocks a duplicate and opens a styled prompt to edit the slug before publishing.
Add registered Bricks elements, including supported nested elements; move and remove elements while preserving IDs and child data.
Review temporary frontend previews at the site’s Bricks breakpoints, expand the preview, or open it in a new tab before applying.
Expand Change Review in the Main Workspace and Content to Pages Workspace when a proposal contains edits, to inspect them in a larger dialog before applying.
Open the selected page in Bricks Builder and undo the most recent assistant change.
Provide About, Settings, Capabilities, FAQ, Version History, terms, and privacy guidance in WordPress admin.
Provider access, costs, quotas, and data handling vary; administrators should review current terms. Bricks validates final data and permissions. Some responsive-only changes may not create a native Bricks revision; use the assistant’s Undo action to reverse them.
Source Code
The plugin ships human-readable JavaScript and CSS source loaded directly without a build step. The native Bricks workspaces use assets/app.js, assets/admin.css, assets/admin-notices.js, assets/tab-notifications.js, assets/style-manager.js, and assets/style-manager.css. The HTML and CSS workspace uses assets/structure-workspace.js and assets/structure-workspace.css. Content to Pages uses assets/content-workspace.css. The Page SEO editor uses assets/seo-editor.js and assets/seo-editor.css. Single draft creation uses assets/new-page.js and assets/new-page.css. Interface themes use assets/theme-presets.js and assets/theme-presets.css. Interface images and code are packaged locally, not loaded from a remote asset host. Browser alerts use built-in browser APIs without an external notification service or library.
Privacy
The Main Workspace sends the prompt, selected Bricks document content, optional reference image, and selected Media Library image metadata (IDs, titles, alternative text, and dimensions) through the WordPress AI Client to the chosen provider. Content to Pages can send the same metadata for images you select, along with the selected page’s extracted copy, brand colors, special instructions, prompt, and current Bricks document elements. When Style Manager is enabled, its colors, variables, scale settings, variable roles, and matching names found in Bricks global settings are sent with Main Workspace and Content to Pages Workspace design requests. When you name another editable page as a design reference, a bounded summary of its native Bricks layout and visual settings is also sent. When you name an existing page as a template reference, its Bricks elements and matching uploaded copy may also be sent to the selected provider. Selected Media Library image files are not sent. The HTML and CSS workspace sends the prompt and optional reference image; refinements also send the current HTML and CSS. When a public website URL is included in a design prompt or Website Planner instructions, the WordPress server requests that URL and up to two same-host stylesheets without running JavaScript. The URL and a compact extracted design summary are sent to the selected AI provider with the design request. The referenced website may receive the request from the WordPress server. Provider terms govern data handling and costs; review them before submitting sensitive information.
The plugin does not save chats to WordPress, store reference image files in browser session storage, upload them to the Media Library, or send telemetry to its author. The selected plugin interface theme is stored only in the current tab’s session storage. It is cleared when the tab closes and is not sent to an AI provider or saved in WordPress. Main Workspace chats are stored per selected Bricks document; HTML and CSS chats and Content to Pages chat messages also remain in the current tab’s session storage until the tab is closed. Content to Pages keeps saved brand colors and special instructions in this tab’s session storage. Unfinished title, slug, and optional SEO details in the single draft page form also stay in this tab session until the draft is created or the form is discarded; the form does not send them to an AI provider. Enabled Style Manager colors, variables, and scale settings are shared by the Main Workspace and Content to Pages Workspace in the same tab and are cleared when disabled or when a new Content to Pages session starts. Unfinished Style Manager edits are also kept in this tab so they can be restored after closing the modal or changing pages. Only saved, enabled settings are sent with design requests; discarding the edits or ending the tab session clears the unfinished draft. They are not written to Bricks global settings. The plugin reads an uploaded copy file from PHP’s temporary upload; it does not save that file or extracted text to WordPress, the Media Library, or browser session storage. Draft pages made from the copy, their explicitly labeled SEO details when one supported SEO tool is active, and applied designs do remain in WordPress. Private temporary previews are removed when replaced, when leaving the workspace, or after one hour. Site backups and logs follow the site’s policies. Administrators configure providers under Settings > Connectors and should review the suggested privacy text in Settings > Privacy.
An unread count in the workspace tab title appears only when a design request ends while the tab is unattended. Optional desktop alerts require a click on the Alerts button and browser permission. The on/off choice is kept only in that tab’s session storage. Alert text is generic and includes no prompt, copy, page title, or image. The plugin sends no notification data to an outside service.
