Skip to main content

What you can do

Once connected, your agent can do five things with Fancy Bricks. Every change it makes is a setting you can see in Bricks and change by hand afterwards: the same ones How to adjust a template explains.

Find a template​

Describe what you need and your agent searches the library: "a FAQ with a list of topics that stays in view", "three pricing plans with a monthly and yearly switch". It gets the templates that fit best, why each one fits and a preview image, and can show you the options before inserting anything.

Each result comes with its page on fancybricks.co. If you'd rather paste templates yourself than let your agent write on your site, ask it for the links: each page has the copy button.

The library is written in English, so searches in English work best. Your agent translates for you if you ask in another language.

Learn how a template works​

Before changing a template, your agent can ask how it's built: where the content goes, which backgrounds it was tested with, which knobs it has, which components it uses and their properties, and the template author's notes. It's the same information as the template's page in these docs.

Insert a template​

"Insert the FAQ with a topic index after the hero." The template goes into the page you name, at the top, at the bottom, or before or after a section that's already there. It never replaces what's on the page.

It can also insert several templates at once, in order: "Build the page with the video hero, the team pricing and the contact form in steps." All of them are checked first; if one can't go in, none is inserted.

  • It arrives in your framework and approach, the same version you'd copy from fancybricks.co.
  • Its classes and components come with it. The ones your site already has are kept as they are, so a class you've adjusted isn't overwritten.
  • If someone has the page open in the Bricks builder, your agent stops and tells you: a change made now would be lost when they save.

The template is fetched with your site's license. Your agent never handles the template itself, which is why inserting one barely uses your subscription.

Look at a section​

"What's in the pricing section?" Your agent sees one section of a page without reading the whole page: each element, its texts, links and images, and the settings of its components. That's what it uses to know what to change.

Change a section​

Your agent changes templates the way the library is meant to be changed: from the lightest change that works to the heaviest. It never edits a class shared with other templates.

Background​

"Make this section dark." The section switches between light, soft, dark and brand, only among the backgrounds that template was tested with. Text, buttons and patterns adapt on their own.

By hand, it's the background class on the section, for example .fbk-section--dark. See Dark mode and preview.

Knobs​

"Make the strip move faster." Many templates have knobs: variables like --fbk-t-speed or --fbk-t-gap, listed on each template's page with their default and what they do. Your agent turns one on this section only, and can set it back to the template's value.

By hand, it's a line in the Custom CSS of the element with the template's class: %root% { --fbk-t-speed: 8s; }. See How to adjust a template.

Component properties​

"Hide the eyebrow", "Change the title to H3", "Make the first button ghost". Your agent sets a property of a Fancy Bricks component (text, a switch, an option from a menu or a style) by the name you see in its panel. When a component appears more than once in a section, it changes only the one you mean.

By hand, it's the component's properties panel in Bricks. See Components.

Check a section​

"Check the section you just edited." Your agent reviews it against the library's rules and tells you what's wrong, why it matters and how to fix it. It watches, among other things:

  • pieces shared with other templates that were edited;
  • fixed colors or sizes where the framework's variables belong;
  • components that were unlinked;
  • accessibility attributes that were removed;
  • pieces the template's scripts need that were removed or renamed.

If it can't check something, it says so instead of calling it fine. For example, when the section was pasted from an older version of the template, it suggests copying it again.

What it doesn't do​

  • Build a whole site from scratch. It works with the library's templates.
  • Edit your shared classes. That would change every template that uses them.
  • Anything outside Fancy Bricks. For other changes, your agent can use Bricks' own AI tools, which come with the same connection.