Swap the homepage banner for a seasonal campaign

Paid versionAppearance & deployments

Your homepage campaign banner goes up and comes down on time, with the old one restored from a backup.

What it replaces: 1-2 h per campaign

What you write to Claude

„put an autumn sale banner on the homepage linking to /sale, image /img/cms/autumn-sale.jpg already uploaded. alt text in pl and en. put the old one back on 2026-11-03”

The problem

For the autumn sale I want a banner on the homepage linking to the sale category, and the old one back after the campaign.

What Claude does

  1. Claude finds where the homepage banner comes from.
  2. It prepares the new banner with its link and shows the change.
  3. After your yes it saves with a backup.
  4. After the campaign, it brings the old banner back from the backup.

What you get

The homepage shows the campaign banner and returns to the old one from the backup.

You stay in control

You see every change before it is saved, nothing happens without your yes, and you can undo it later. Changes to the shop's look use a separate, extra-protected connection, usually set up by whoever looks after your shop. Every file is backed up before it changes.

See pricing

Related use cases

For developers
Area
3 · Appearance & deployments
Connector
service connector
In the free Audit
no, paid version only
For
Marketer / SEO, Store owner
Tools
ps_list_theme_files, ps_read_theme_file, ps_write_theme_file, ps_list_file_backups, ps_restore_file_backup, ps_clear_cache

Step by step

  1. Finds where the homepage banner is rendered (theme template or a module like the image slider) with ps_list_theme_files and ps_read_theme_file.
  2. If it's in the theme, prepares the template change with link and alt text and calls ps_write_theme_file (preview with diff).
  3. After your approval, saves with a backup and clears the cache.
  4. After the campaign, restores the previous version with ps_list_file_backups and ps_restore_file_backup (also previewed).
  5. If the banner comes from a module, this becomes a module template override with ps_override_module_template, also in block 3.

Safety

Block 3 works only through the service connector: a separate token accepted only from allowlisted IP addresses, off after installation. Theme files are backed up automatically before every write and can be restored with ps_restore_file_backup. Limit: 20 theme file writes per hour. Uploading the image file itself is done in the back office or by FTP.

Last updated: 2026-10-05