For developers
Install a pack. Keep every page current.
A theme pack is a set of section designs released together under one version number. From Design Library you install it on a website, preview its releases, bring saved pages up to date after a release, and check that every theme runs current, safe packages.
On this page
What a pack holds
A theme pack groups the section designs of a website’s theme, such as a hero, a price list and a footer. Every release has a version number and can carry release notes.
Open Content, then Design Library, and choose Packs. Packs lists the theme packs that belong to the website you have open.
Design Library
Packs
Salt & Stone Studio
The studio’s theme: a hero, session prices, a class schedule that reads a Content List, and the footer.
Salt & Stone Workshops
Pages for weekend workshops, with upcoming dates and a signup form.
- Site installed
- The release installed on the website you have open, or Not installed on this site.
- Designs available in your library
- How many of the pack’s designs this website can add to a page right now.
- Latest pack release
- The newest release of the pack.
- Manage pack
- Opens the pack with its overview and its designs. Every action in this guide starts there.
Install or uninstall a pack
- Open the pack. In Packs, choose Manage pack on a pack that shows Not installed on this site.
- Review installation. The button sits at the top right. The dialog names the latest release at the moment you opened it.
- Install latest release. The pack’s designs join Design Library, and Mirin shows Pack installed. Review affected pages before publishing.
Installing adds the pack’s design definitions. It does not publish pages. Install always installs the latest release, so previewing an older release does not choose it.
What uninstalling leaves behind
To uninstall, open More pack actions beside Page updates and choose Uninstall pack. Uninstalling removes the pack’s components that have not been customized.
- Customized components stay in your library and are marked as custom.
- Pages using removed components may need updates.
- You can install the pack again later.
Installing needs a paid plan
Installing and uninstalling a pack work on a website with a paid plan. On any other plan the change does not complete.
Preview a release
Preview release sits at the top of Manage pack. It lists Current site designs and each release. The newest release says Latest, and the one on this website says Installed.
- Current site designs
- Each design with its current bundle and version, including custom variants added later.
- An earlier release
- That release’s saved bundles with today’s default content. Historical fields are unavailable, so the inspector shows Details only. Return to current designs goes back.
- Release preview unavailable
- The release has no saved bundles to show, and Mirin never substitutes current ones. Preview current designs goes back.
Pack details shows the artwork, the description and the release notes. Its counts can differ from each other. Current site designs counts what the website has now, while Recorded at installation and Recorded in that release count saved records.
Bring pages up to date
A release can add settings to a design or remove them. Pages keep the content they already saved until you review page updates. In Manage pack, choose Page updates.
Salt & Stone Studio
Review page updates
Salt & Stone Studio
3 pages have component fields that can be updated. Review the changes and choose which pages to update.
Components with changes (2)
- Session Prices · 3 pages
- Studio Footer · 3 pages
- Read what changed. Components with changes counts the pages each design is on. On a page, Review field changes lists Fields to remove and Fields to add.
- Choose pages. Every affected page starts selected. Select all and Deselect all change the whole list.
- Choose options. Remove unused fields and Add missing fields with defaults start on. Republish updated pages starts off.
- Update. The button counts the pages you selected. If some pages cannot be updated, Mirin says how many were, and keeps only the failed pages selected so you can try again.
- Remove unused fields
- Removes props that no longer exist in the component schema.
- Add missing fields with defaults
- Adds new props from the schema with their default values.
- Republish updated pages
- Republishes the updated pages that are already published.
Republishing makes the changes live
With Republish updated pages on, pages that are already published go live with the updates straight away. Leave it off to check each page in the editor and publish it yourself.
When nothing needs changing, the dialog says All pages are up to date. Developers can read how a schema change becomes these field changes in Component basics.
Check theme health
Theme health tells you whether each theme on your website runs current, safe packages. It sits at the top of Packs in Design Library, and Manage pack shows it for that pack once it is installed.
Theme health
Older themes keep working. We recommend upgrades and never apply them without you. How this works
- Up to date
- The theme runs the newest React that Mirin supports, and none of its packages has a known security issue.
- Update recommended
- The theme was built with an older React. It keeps working exactly as it does today. Theme health lists each package that is behind and the newest version.
- Security warning
- A package the theme uses has a published security advisory. Theme health names the package, says which version fixes it, and links to the advisory.
- Not checked yet
- Mirin has no record of which packages the theme was built with, usually because it was built a long time ago. It keeps working as before.
Nothing changes on its own
Older themes keep working. Mirin recommends an upgrade when a theme falls behind or a package has a security warning, and you decide when it happens.
When security warnings cannot be checked
If the advisory database cannot be reached, theme health says We couldn’t check for security warnings right now. The version checks are still accurate. Open the page again later to check once more.
Upgrade a theme
An upgrade brings a theme up to date for you. Nothing on your website changes until you choose Publish.
- Choose Upgrade. It appears on a theme that shows Update recommended or Security warning. The panel lists what changes, such as react moving from 19.2.4 to 19.3.0, and why.
- Start upgrade. Mirin moves the theme to the new packages. Upgrading your theme takes a few minutes. If a file needs changing to work with them, Mirin's AI repairs it and tells you.
- Review. Mirin draws every section before and after and tells you how many look the same. Open a section that looks different to compare the two side by side.
- Publish or Not now. Publish asks you to confirm, then puts the upgraded theme live. Not now throws the upgrade away and leaves your site as it is.
- What it costs
- Mirin made starter themes upgrade free. Other themes use AI credits, and the Upgrade button shows the price. If the upgrade does not work, your credits are not used.
- Undo upgrade
- After you publish, Undo upgrade puts the theme back the way it was, live on your website, after you confirm.
- Will an outdated theme break my site?
- No. Each theme keeps running the packages it was built with, so an older theme looks and works the same as it did the day it was installed.
- Does checking theme health change anything?
- No. Theme health only reads what each theme was built with. Mirin recommends upgrades and never applies one without you.
- Where do the security warnings come from?
- From OSV, the open database of published security advisories. Mirin checks each package a theme uses against it and keeps the answer for a day before checking again.