MJC Designs AI Design Assistant for Bricks Builder

No. It edits eligible pages and Bricks templates. It can configure supported Query Loops that display posts, but it does not edit posts.

An administrator configures a compatible provider under Settings > Connectors. Users choose from its compatible models. This plugin does not store provider credentials.

Costs, free tiers, and quotas depend on the provider and model. Check the provider's current terms before use.

The Main Workspace sends the prompt, selected Bricks document content, optional reference image, and metadata for selected Media Library images. When Style Manager is enabled, its colors, variables, scale settings, variable roles, and matching names found in Bricks global settings are also sent with Main Workspace and Content to Pages Workspace design requests. The HTML and CSS workspace sends the prompt and optional image; refinements also send the current draft. Selected Media Library image files are not sent. See Privacy below for storage and retention details.

Yes. Select the color drop button between Fullscreen and Alerts in any workspace. Choose Classic Purple, Ocean Blue, Forest Green, Strawberry Milk, or Saffron Yellow. The theme follows plugin screens and reloads in the current browser tab, then resets when the tab closes. Panel backgrounds, FAQ accordions, and modal surfaces follow the preset. It does not affect Bricks designs or Style Manager colors.

Yes. Paste one public HTTP or HTTPS page URL in the design prompt or Website Planner special instructions. WordPress retrieves the page's static HTML and, when available, up to two same-host stylesheets using its safe HTTP API; it does not run JavaScript. A compact summary of the page title, description, heading hierarchy, layout landmarks, and CSS design tokens is sent to the selected AI provider as untrusted visual guidance. The assistant does not copy the reference site's text, code, or assets. Main and Content to Pages use registered Bricks elements and controls only. HTML and CSS produces static code within its existing safety rules. Dynamic sites may provide limited reference details; attach a screenshot when you need stronger visual guidance.

Yes. Choose up to ten existing images and describe where to place them. The assistant uses suitable selected images first and can make labeled native Bricks placeholders for image slots without an available image. The provider receives selected image titles, alternative text, dimensions, and IDs, but not the image files. Review the proposed placement before applying.

Yes. Use the plus icon beside Bricks Document in Main Workspace or Content to Pages. Enter a page title and unique slug, then choose Create draft. The workspace loads the new draft. You can add a reviewed Bricks design, apply it to the draft, and use Publish page when your account has permission. Optional SEO details are saved through the supported SEO tool selected in the form. Unfinished form details stay in this browser tab; the plugin asks you to discard them or keep editing before switching pages or leaving. Resolve unfinished Page SEO edits before creating a new page.

Yes. In Main Workspace or Content to Pages, select a WordPress page, open Page SEO, then choose Move to Trash on the left side of the footer. The button appears only when your account can delete that page and WordPress Trash is enabled. The confirmation has a Cancel option; after you confirm, a loading panel appears while the page moves to Trash and the workspace loads another available document. A trashed page can be restored from WordPress Pages > Trash until the site empties its Trash. Unapplied Page SEO edits and design proposals for that page are discarded when you confirm. Bricks templates and the HTML and CSS workspace do not have this action.

Page SEO checks a changed slug against other saved WordPress pages, including published pages and drafts. A styled warning asks for a different slug before any SEO fields or the new slug are saved. This applies in Main Workspace and Content to Pages Workspace. Manual draft creation asks for a different slug before saving. Content to Pages can still generate drafts from uploaded copy with duplicate slugs, but Publish page in either workspace keeps a draft unpublished until its slug is unique. If a draft has no saved slug, publishing checks the slug WordPress would make from its title. The check excludes the selected page, temporary previews, and trashed pages; it applies across pages with different parents. Change the slug in Page SEO or the WordPress editor, then publish again.

No. Main Workspace and Content to Pages previews are private temporary drafts removed when you leave, replace them, or after one hour. HTML and CSS drafts appear in an isolated browser frame without creating preview posts. Ordinary draft pages remain in WordPress until you publish them, move them to Trash, or remove them through WordPress.

The Main Workspace and Content to Pages Workspace propose changes to registered native Bricks elements and controls. Both can place suitable site images explicitly selected from the Media Library; when no image is available for a needed slot, they can build labeled placeholders with native Bricks elements. Neither workspace can write Custom CSS or code controls, or manage global styles or the Media Library. The HTML and CSS workspace creates a draft for manual copying only. To reference another page's style, select the page to change and name one other editable page in your prompt, such as “Match this page's visual style to the About page.” The assistant reads a bounded summary of that page's native Bricks layout and visual settings. It does not copy the source page's text or images, change the source page, or inspect its full rendered appearance or global styles. Review the proposal before applying it.

Choose a model and class prefix, describe a layout, and optionally attach a reference image. Review the preview, refine it in the same chat, then copy the HTML and CSS into Bricks. Up to five chats remain in this browser tab. The chosen document is not sent or modified; add real images and review converted classes and styles in Bricks before saving.

Enable Style Manager in the Main Workspace or Content to Pages Workspace to share palette colors and variables for this browser tab. Import existing Bricks JSON or create styles in the editor, then export and import the JSON into Bricks. The assistant checks that the names exist in Bricks before requesting a design; it does not install global styles itself. Suitable names are used in registered controls, while explicit fixed values and color directions in your prompt or saved special instructions take priority. The HTML and CSS workspace does not use Style Manager. Turning Style Manager off clears its shared settings and restores the Website Planner brand-color controls.

Prepare final copy with a clear heading for each page, such as Page: Home, HP - Home, CP - Contact, or 2P - About, followed by that page's copy. A plain title immediately followed by two explicit SEO fields can also start a page. Long visual divider lines of dashes between pages are ignored as separators. You can include labeled SEO details within each page section, for example SEO title:, Meta Title:, Focus keyphrase:, Keywords:, Slug:, and Meta description:; they can appear after the page title or later in the section. These recognized lines are kept out of the design copy, suggested in the matching page's SEO editor, and saved with a newly created draft when one supported SEO tool is active. Include the brand name in the copy when it should appear in the design. Mark content headings H1: through H6:, [H1] through [H6], literal <h1> through <h6> tags, or Word heading styles to preserve their intended hierarchy. Review the detected page structure in the extracted-copy preview before creating drafts. Keywords: uses the existing focus keyphrase field; some SEO tools may treat a comma-separated list as one phrase. Optional labels such as Slogan:, Hero banner text:, and CTA Graphical Block: distinguish visible words from layout direction. Use DOCX when inline bold, italic, or hyperlinks matter; PDF extraction groups readable text into paragraphs but does not preserve those styles or links. In Website Planner, upload a DOCX or text-based PDF, review the extracted copy, set brand colors and instructions, then create drafts. Page count is not capped; the 50 MB document limit applies. If a page title already exists, confirm that it should be skipped; only missing pages become new drafts. Reset planner clears the current inputs and uploaded copy without deleting WordPress pages. Cancel restores the planner form, uploaded file, and extracted copy to how they were when the modal opened; X or Escape only closes it. Select a page, optionally choose existing Media Library images, generate its design, review and apply the proposal, and publish only when ready. You can also select an existing Bricks template, describe its design in a prompt, and name an existing page to use its design and matching uploaded copy as reference. Only the selected template receives proposed changes. The workspace does not create templates or set template conditions. Use Page SEO beside the selected page to review and edit supported SEO fields and its WordPress slug; templates have no Page SEO editor. Pages, templates, and applied designs persist in WordPress. Saved colors and special instructions remain in the current browser tab until it closes. The plugin does not save the uploaded copy file or extracted text to WordPress or browser session storage; re-upload and extract the file after a reload. A page without matching copy cannot be generated from that file. When Style Manager is enabled, Website Planner hides its brand-color controls and uses the saved palette instead. Turn Style Manager off to choose brand colors in Website Planner again. If saved planner settings, chat, or shared Style Manager settings are found when you return to this workspace, a dialog lets you continue or start new. Continuing keeps those settings, then you upload the copy again. Starting new clears the shared Style Manager settings as well as the planner and chat; it does not delete WordPress draft pages.

No. The PDF extractor reads supported text and groups paragraphs when possible, but it does not retain text formatting or links for design generation. Use a DOCX when those details matter. The extracted-copy preview is plain text for both file types.

No. It uses the WordPress Abilities API for page operations and does not load the external Bricks Skills package or WordPress MCP Adapter.