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 HTML and CSS workspace creates drafts for manual pasting into Bricks. Its Content to Pages Workspace 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 and is not affiliated with or endorsed by its developers. This alpha release is for evaluation: review each proposal and keep a backup before applying changes.

Visit the MJC Designs AI YouTube channel.

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.
• 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.
• Change only registered native Bricks controls. AI proposals cannot write code controls or Custom CSS.
• 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 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 the Content to Pages workspace to preview a DOCX or text-based PDF copy file up to 50 MB, set brand colors with WordPress’s color picker, create draft pages, and generate a separate reviewed Bricks design for each page. Generate Drafts detects existing page titles and skips them after confirmation. Page headings must use Page: Title or Word Heading 1. DOCX extraction retains common bold, italic, and safe external links for Bricks text proposals; the extracted-copy preview is plain text. PDF extraction groups readable text into paragraphs when possible but does not preserve styling or links; text-based PDFs with unsupported encodings and image-only scans may not extract correctly. Choose up to five existing Media Library images for a design, or reserve labeled placeholders for missing visuals. The server’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 saved planner settings and chat or start a new session. Starting new clears only this workspace’s browser-session settings and chat; WordPress pages remain. 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. This workspace does not create templates, set template conditions, or add SEO details such as meta titles and descriptions to pages or templates. Do those tasks separately in Bricks, WordPress, or an SEO tool. 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.
• 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 and Content to Pages workspaces 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: assets/app.js, assets/admin.css, assets/admin-notices.js, and assets/tab-notifications.js for the main interface; assets/structure-workspace.js and assets/structure-workspace.css for the HTML and CSS workspace; and assets/content-workspace.css for Content to Pages. 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 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. 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. 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 only saved brand colors and special instructions in this tab’s session storage. It reads an uploaded copy file from PHP’s temporary upload; the plugin does not save that file or extracted text to WordPress, the Media Library, or browser session storage. Draft pages made from the copy 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.

1. In WordPress, go to Plugins > Add New Plugin > Upload Plugin.
2. Upload and activate the MJC Designs AI Design Assistant for Bricks Builder ZIP file.
3. Install and configure a compatible AI provider under WordPress Settings > Connectors. Provider setup and credentials are managed by the site administrator.
4. In Bricks > AI > Abilities, enable get-page-elements, set-page-elements, and get-element-schema.
5. Open MJC Designs AI, choose a configured provider model, select a page or Bricks template, enter a design request, review the preview and proposed edits, then apply them when ready.

When upgrading, the plugin removes credentials left by earlier releases. If you previously added MJC_DESIGNS_AI_DESIGN_ASSISTANT_BRICKS_API_KEY to wp-config.php, remove that unused constant manually.

1. 

   MJC Designs AI workspace showing model selection, the design assistant, Bricks page elements, frontend preview, and change review.

2. 

   Expanded frontend preview with desktop, tablet, mobile, and custom viewport controls for reviewing a Bricks page at different screen sizes.

3. 

   Add a reference image by dragging it into the prompt area or using the upload button to guide the AI design suggestion.

4. 

   Configure an AI provider under Settings > Connectors to make models available for design suggestions.

5. 

   Inspect a Bricks page element’s saved settings, with object values formatted for easier reading.

1.1.7

• Content to Pages Workspace · Alpha · 2026-10-21 06:30:07 PHT
  1. Extract final copy, create draft pages, and prepare Bricks designs for review before saving or publishing.
  2. Improve planner controls, focus page requests, preserve DOCX formatting, and detect existing pages.
  3. Keep saved planner details in the browser tab until it closes; the plugin does not save uploaded copy files.
  4. Allow selected Media Library images in Content to Pages designs while retaining placeholders for missing visuals.
  5. Let refinements reshape a section or page while preserving planner guidance and final copy.
  6. Edit existing Bricks templates with optional planner guidance and a named page as design context; configure conditions and SEO details separately.
  7. Group readable PDF text into paragraphs without retaining formatting or links.
  8. Offer a continue-or-start-new choice for saved browser sessions; show Generate Drafts after planner settings are saved.
• Workspace improvements · Alpha · 2026-10-21 06:30:07 PHT
  1. Match HTML and CSS workspace tooltips, image-drop guidance, and Bricks document labels across workspaces.
  2. Align Generate and Refine buttons and keep main-workspace conversations for the browser session.
  3. Reserve labeled image placeholders with native Bricks elements when no site image is selected in the main workspace.
  4. Expand Change Review only when edits are proposed; show the HTML and CSS setup guide when no provider is connected.
  5. Open Quick Guide from every workspace header, and resize the HTML and CSS design request field vertically.
  6. Reduce Bricks schema data sent to AI, especially for new Content to Pages designs, while retaining full proposal validation.
  7. Allow more time for Bricks design proposals to return before the provider request times out.
  8. Use native Bricks color values, check complete copy and formatted DOCX labels, and report proposals with no edits accurately.
  9. Show completed requests in the tab title and offer optional browser alerts when a workspace is unattended.
  10. Let an editable page’s native Bricks layout and visual settings guide another page without changing the reference page.

Earlier release notes are included in changelog.txt and the dashboard’s Version History.