Choose where to customize
You can personalize the layouts after importing them into Bricks, or ask your assistant to make specific changes through a supported workflow.
| Workflow | Where to customize |
|---|---|
| Copy link | Edit the content in Bricks after copying and pasting the layouts. |
| JSON in chat | Request specific text changes before the assistant delivers the final JSON. |
| Direct import | Ask your assistant to make supported changes through the Bricks Builder MCP, with the destination and scope confirmed. |
Choosing a business type helps your assistant find suitable layouts. It does not automatically replace every piece of sample content.
Customize after using a copy link
The copy-link workflow is designed to deliver your selected layouts without bringing the full JSON into the conversation.
After pasting the layouts:
- Open the destination page in Bricks.
- Replace sample headings and paragraphs.
- Update button labels and their destinations.
- Replace images and review their alternative text.
- Check any remaining placeholder content.
- Review the page on desktop, tablet and mobile.
Keep text length in mind. A much longer heading or button label can change how a layout fits.
See Generate a copy link for the delivery steps.
Request text changes in JSON
When receiving JSON in the chat, identify the text you want to replace and provide the new wording.
The assistant should change the requested text while preserving unrelated layout data.
Example prompt
In the approved hero layout, replace the main heading with “Dental care for the whole family” and the main button label with “Book an appointment”. Keep the button destination, layout structure, classes, styles and interactions unchanged. Deliver the complete updated Bricks-compatible JSON.
For several changes, provide them together:
| Location | Replacement text |
|---|---|
| Hero heading | Dental care for the whole family |
| Hero paragraph | Friendly dental care for children and adults, with appointments that fit your schedule. |
| Main button label | Book an appointment |
Use wording that accurately describes your business.
Text changes have a defined scope. Changing a button label does not change its destination. Changing a form label does not configure where submissions are sent.
See Get JSON in chat for the full workflow.
Ask your assistant to draft the text
If you do not have final wording, ask for a draft before requesting the updated layout.
- Describe your business and audience.
- Provide the facts the text should communicate.
- Specify the tone and approximate length.
- Review the proposed wording.
- Approve the text before it is applied.
Example prompt
Draft a short hero heading, a supporting paragraph of no more than 30 words and a booking button label for a family dental clinic. Use a calm, welcoming tone. Do not invent prices, qualifications, awards or patient testimonials. Show me the text for approval before changing the layout.
Review factual claims before publishing. Supply your real contact details, services, prices and credentials where needed.
Customize through the Bricks Builder MCP
For direct imports, separate the layout selection from the content changes.
Tell your assistant which page and elements it may edit, and ask it to check that the required Bricks tools are available.
Example prompt
After importing the approved layouts into the confirmed draft page, use the Bricks Builder MCP to update the hero heading to “Dental care for the whole family” and the main button label to “Book an appointment”. Preserve the existing destination URL and unrelated content. Verify the saved text and do not publish the page.
If the assistant cannot identify the correct element or perform a requested change, it should explain the limitation before proceeding.
See Import directly into Bricks for destination confirmation and import requirements.
Be precise about what should change
Identify the section and the specific element.
Instead of:
“Change the buttons.”
Try:
In the hero section, change only the primary button label to “Book an appointment”. Keep the secondary button and both destination URLs unchanged.
If several elements have the same text, include the layout name or describe the element’s location.
Avoid broad find-and-replace requests when the same wording may appear in unrelated sections.
Review links, images and forms separately
These changes need more information than a text replacement.
| Element | What to specify |
|---|---|
| Button or text link | The element and its exact destination URL. |
| Image | The replacement image, where it belongs and appropriate alternative text. |
| Form | The fields, submission destination and required behavior. |
| Dynamic content | Whether to preserve the existing data connection or replace it with static content. |
Make these changes in Bricks, or ask your assistant to check whether the connected Bricks Builder MCP tools support them.
Do not assume that requesting a new button label, image description or form heading also changes the underlying behavior.
Keep content and styling changes separate
Content changes affect what visitors read. Styling changes affect appearance.
Examples of styling changes include:
- Colors
- Typography
- Spacing
- Column arrangements
- Responsive behavior
- Animations
Request these changes explicitly and review their effect on the rest of the site.
Shared styles can affect multiple elements. Before changing a global class or framework variable, confirm whether the change should apply elsewhere.
Moving custom CSS during direct import changes where the CSS is stored. It does not, by itself, redesign the layout.
Keep class renaming separate
BEM class names describe the layout’s structure in the editor and styles.
Changing a class name does not rewrite the visible text. Replacing a heading does not require renaming its class.
Confirm BEM names during layout preparation, and describe content changes separately.
Review before publishing
After applying your changes:
- Check the final wording for accuracy.
- Confirm that no unwanted sample content remains.
- Test buttons and links.
- Review images and alternative text.
- Test forms and other interactions.
- Check the page at different screen sizes.
- Publish only after reviewing the result.
If a change causes a layout problem, identify the affected section and describe what changed before asking for a correction.