Change your footer once, and it changes everywhere

What a component change actually changes

Every other AI edit in Mirin changes a page. This one changes the thing your pages are made of, so it is worth knowing how it differs before you spend on it.

A header, a navigation bar or a footer usually sits on every published page at once. Those shared sections are the ones a rewrite will not touch, and for them the panel offers to change the component instead. And if what you want is a new switch, a new picture slot or a row that repeats, a rewrite cannot give it to you at any price, because it changes the values inside your settings rather than which settings exist.

The change outlives the panel

Every other AI edit ends when its panel closes, because what it proposes is painted on the page in front of you. This one is held on your site until someone decides.

Nothing changes until a person publishes it

The build runs, the result is rendered and the credits are settled, and your live site keeps serving exactly what it served before.

It is a real rebuild, not a description of one

Mirin reads the component as your site has it today, rewrites its source, builds it, and renders the result with the settings your pages actually carry.

You can close the builder, open it on another computer, and the change is still waiting. So can a colleague. The change becomes real when somebody presses Publish, and not a moment earlier, and if it does not build there is nothing to publish and nothing is charged.

How to ask for one

There is one AI button on every section, and the panel works out whether you meant the words or the component.

1. 1
   Select the section on the page. Its toolbar carries one AI button, Rewrite section with AI. It is the same button for words and for the component, so you never have to know which one you need before you ask.
2. 2
   Let the panel tell you which it is. On a shared section, such as a footer on every page, the panel explains that AI does not rewrite shared wording and offers Change the component instead straight away. On any other section, say what you want. If rewriting the words can do it, you get a rewrite for up to 0.1 credits on Standard. If it cannot, the panel says “Those credits were not used” and offers the same button.
3. 3
   Read what it will touch. The component panel names the component and how far it reaches: “Footer is on 20 pages. All 20 change together, and it cannot be changed back one page at a time.” Under that it lists the pages by name, so the number is something you can check.
4. 4
   Say what should change about it. The box asks “What should change about it?” Write it the way you would say it out loud, for example “Add icons below the title, and let me toggle them in the settings.” The price sits above the box, with the cheaper rewrite named beside it.
5. 5
   Press the button with the number on it. It reads Change it on 20 pages, because that is the fact worth reading twice. On a component used once, or on none yet, it says Change it. The last line under it is the promise: “Mirin rewrites it, rebuilds it and shows you the result. Nothing on Salt & Stone Pilates changes until you publish it.”

While it builds, you can close the panel

The panel names the step the build is on, read from the build itself rather than from a timer.

There is no Stop button, and the panel says why: “Nothing on your site changes while this runs. A build cannot be stopped part way, and if it fails the credits go back.” Once the build has started it adds “This runs on our build servers, so you can close this and come back. Select the section again to review the change.”

Only one change waits on a component at a time. While one is waiting, the section’s panel offers that change rather than a second one, so two answers about the same component never race each other.

Reviewing the change before it goes live

You reach the review from Review at the top of the Build panel, or from the section’s own panel. Either way it opens on the two facts that matter: “Footer would change on 20 pages.” and “Nothing on your site has changed. Your 20 pages are still showing the version you have now.” Everything under them is evidence for a decision you have not made yet.

  <p className="footer-tagline">{tagline}</p>
- <p className="footer-note">{newsletterNote}</p>
+ {showSocialLinks && socialLinks.length > 0 && (
+   <ul className="footer-social">
+     {socialLinks.map((link) => (
+       <li key={link.url}><a href={link.url}>{link.label}</a></li>
+     ))}
+   </ul>
+ )}

The two pictures

Two pictures, Now and After

The change is rendered twice, once as your site has it today and once as it would be, using the settings one of your real pages carries.

A note when the two come out the same

If the change makes no visible difference with those settings, the review says so rather than letting you approve two identical frames.

Your section at laptop width, shrunk

Both frames render your section at the width a visitor on a laptop sees, then shrink it to fit side by side, so you compare the layout your visitors actually get.

The caption names whose settings they were rendered with: “Rendered with the settings from your Home page.” Look at them side by side, or switch to After only when you want the room. It says how much is in view too, for example “each one holds the top 853 pixels of it”. Press Taller for more room, or scroll inside either frame. Both frames always get the same size and the same scale. When the change makes no visible difference the note is plain about it: “Now and After came out as the same picture, byte for byte. With the settings this was rendered from, the change makes no difference to what a visitor sees.”

What changes in the settings

What changes in the settings

Under the pictures is the list of settings the change adds, retypes or removes, because no picture can show you that. A new setting is the ordinary outcome and needs nothing from you.

A removed setting stops the flow

Removing a setting is the one change that asks you to slow down, because anything typed into it stops showing on every page that holds a value. To go ahead, type the component’s name.

A new library, if there is one

If the rewritten component loads something your theme was not loading, the review names it and says that publishing adds it to every page of the theme, not only to the pages using this component.

A removal says exactly what it costs before you can confirm it: “This removes the Newsletter note setting. Anything entered against it on 20 pages stops showing.”

The rest of the evidence

• The code, if you want it. See what changed in the code opens the source changes. Nobody has to read it. It is there because a change you cannot inspect is a change you are taking on faith.
• Who asked, in their words. The reviewer may not be the person who asked. The review says when it was asked and, where it can name a person, by whom, with the request shown back word for word underneath.
• A component that only shows up in a browser. A few components render nothing until a browser runs them, such as a cookie banner or a cart drawer. Those arrive without pictures and say why: “This component only renders in the browser, so there is no picture to show. The change built cleanly; you are approving the code.”

Publishing it, and taking it back

Three buttons, and only one of them changes anything.

• Publish to 20 pages. Pressing it is the whole act, and the change is on those pages straight away.
• Decide later. Closes the review and leaves the change waiting under Review. The line under the buttons says how long: “It stays under Review for 14 days.”
• Discard. Throws the change away, and your site is untouched because it always was. The credits do not come back.

There is no Save step

On a page, an AI answer is kept, saved into your draft, and made live with Publish changes. A component has no draft to sit in.

The count is checked again as you publish

A colleague can add the component to another page while it waits, so Mirin counts again. If the number has moved, the review says what it moved to and asks again.

It becomes a numbered version

The panel says “Footer is live on 20 pages.”, then “Kept as version 3, so you can put version 2 back.”, then “The credits for this change are used.”

Put it back

A button on that same panel returns every page to the version you had. It costs no credits and needs no new build, because the version you came from was kept.

The review quotes the missing Save step while you are deciding: “There is no Save step for a component. Publishing puts this on those 20 pages straight away.” So the button says Publish to 20 pages. That number was counted when the change was asked for, and Mirin counts again as you publish rather than quietly changing more pages than the button offered.

Open a change you left under Review on a later day and it tells you what is left, for example “It stays under Review for 11 more days.” Discarding says why the credits stay spent while the button is still under your cursor: “Nothing on your site changed. The credits paid for writing the change and proving it renders, not for publishing it.”

What it costs, and when it is free

The initial schedule prices a component change at 0.7 on Standard or 3.5 on Best. The panel shows the current quote and your balance before you start. A completed change uses that accepted price; a failed change returns its hold. See choosing Standard or Best.

It costs more than a rewrite because it is more work. A rewrite writes words. A component change writes a component, builds it, and renders and checks the result before you see it. The credits come from the same allowance every AI edit draws from. It belongs to the website rather than to you, and it refills on a rolling 30 day window. See how the limit works.

When it is free

A change that could not be built

If the rewritten component does not build, there is nothing to publish and the credits go straight back: “That change could not be built, so nothing on your site moved. Your credits were not used.”

A change that was already there

If the assistant reads the component and decides it already does what you asked, it says so and your credits are not used. That is not a fault. Ask for something different rather than asking again.

A build that never reported back

If a build stops without finishing, Mirin closes it out and returns the credits rather than leaving the component stuck behind a change nobody can decide about.

Publishing, and putting it back

Neither costs anything. The credits paid for writing the change and proving it renders.

When the change is not offered

When the change cannot be asked for, the panel says which of these it is and what still works. None of them stop you editing the section by hand.

Does my plan include changing a component?

Changing how a component is built is included on the paid plans. If yours does not, the panel says so and links to billing. Every other part of the page editor keeps working.

What happens if I do not have enough credits left?

The panel says how many you have, when the next ones unlock, and names the cheaper option: “Rewriting the words in this section costs up to 0.1 credits and changes this page only.” Switching to Standard also lowers the price.

Why does it say Mirin does not hold the source for that theme?

A component can only be rebuilt from the source of the theme it came from. If Mirin does not hold it, the panel names the theme and the one thing that fixes it: publish that theme once. Its words still rewrite and its pictures still fill.

Why does it say the theme has no folder for that component?

The theme is held, but this component is not in it. Republishing that theme brings the source back into line. The component keeps working, and only rebuilding is off.

What if the component is not in my component list?

A page can carry a component from a theme that has since been removed. There is nothing to rebuild, so the panel says that instead of failing later. Its words still rewrite and its pictures still fill.

Why is the AI button off on this page?

You are looking at a page you cannot change. Viewing an old version, or any screen that will not take an edit, turns the AI button off with the reason beside it.

The rest of the AI edits

Rewriting a field or a whole section, describing a new section, planning a page, having a new component built and finding a picture are all in AI page edits, with what each one costs.