Resource Packs

Resource Packs bundle supported Site resources and optional content into an installable package. They are useful for starter sites, themes, design systems and other reusable Site setups.

Installed packs show Installed; Host-owned packs are identified separately as managed by the Host.

Import The Pack

Open Design → Resource Packs and import the approved ZIP, or choose a pack already available to the Site. Importing adds it to the Resource Pack Library and does not change the live Site.

Install The Pack

Choose Install. Micro CMS compares the incoming pack with the current Site before changing anything. When there are no local-change conflicts, installation continues automatically. If a decision is required, Micro CMS opens the review instead of silently choosing for you.

Create A Resource Pack

Use Create Resource Pack when you want a reusable package made from selected Site resources. Give the pack a name, key, version and description, then select the resources that define the reusable feature or design.

Micro CMS automatically includes Resources required by the selected items. Required dependencies are part of a valid portable pack and do not need to be selected manually. Use search and Resource type filtering to work with larger Sites.

Include referenced Media adds public Media used by the selected composition. Include Site Composition is optional for a modular pack; when selected, Micro CMS also includes the Site defaults and route references needed by that composition.

Export Site Composition

Use Export Site Composition when the goal is to capture the current portable Site composition rather than create a focused reusable pack. It exports the Site's portable Resources, Content, referenced Media, defaults and route rules.

A Site Composition export is not a Full Site Backup. It does not contain Micro CMS Core, Applications, Extensions, private runtime state or backup data.

Conflicts And Local Changes

If the Site has changed a resource that the pack also wants to change or retire, choose the outcome deliberately. Keep Local keeps the Site's version. Use Pack accepts the reviewed pack version. Micro CMS does not silently replace locally changed resources.

Existing Pages At The Same Address

When a pack contains a Page at the same public address as an existing Site-owned Page, Micro CMS can reuse the existing Page instead of creating a duplicate route. If the content differs, that difference is presented for review.

Content Corrections From A Pack

A Resource Pack update can include a reviewed correction that fills a missing field on Content belonging to one of the pack's Collections. This is useful for limited data fixes, such as adding a missing catalogue identifier.

These corrections are intentionally cautious. Micro CMS only fills an empty field when the intended Content item and existing values match the update. It skips drafts, fields that already contain a value and anything that does not match, so local work is not overwritten. Routes and Media links are left unchanged.

Retired Resources

A pack can mark resources as retired. During an update, an unchanged resource can be retired automatically; a locally changed resource is shown for review.

Pending Installs

If installation is waiting for a conflict decision or you leave a review before continuing, resume it from Pending Installs. A pending install is not live until publication completes. Long operations continue automatically; return to the operation panel to see the current state or retry an interrupted operation.

Created In And Current Ownership

An imported resource can show both Created in and Current pack ownership. Created in is the pack version that introduced the resource; Current pack ownership is the installed pack/version that currently manages it.

Automatic Updates

On Solo or the Bridge Host, Resource Pack automatic updates follow the local update policy. On a managed Site, Host policy supplies the default and may optionally let the Site choose its preference. Local-change conflicts still stop for a decision.

Remove An Installed Pack

Use the pack's removal action where available and let removal finish before installing a replacement. If removal encounters a locally changed resource that needs a decision, Micro CMS asks before proceeding. If no optional Site pack remains, Micro CMS restores the built-in Core presentation.

Current Packs

If the installed version already matches and nothing needs to change or be resolved, the pack is shown as Current.