This guide explains how to update the s:CMS framework in your site.

TL;DR

1
npm update @lad-sapienza/scms-core

That’s it. The framework layer (DataTb, Map, Gallery, ZoteroGeoViewer, Record, the Astro integrations, and the scms-add-collection/scms-add-content scaffolding commands) is an ordinary npm package, @lad-sapienza/scms-core. Updating it is exactly like updating any other dependency — there’s no custom script, no protected folder to worry about, and nothing in src/ is ever touched, because the framework was never part of this repository in the first place.

Checking What’s New

Before updating, see what version you’re on and what’s available:

1
npm outdated @lad-sapienza/scms-core

To see the package’s changelog/commit history, check lad-sapienza/scms-core on GitHub.

Picking a Version

By default, npm update respects the version range already in your package.json (e.g. ^0.1.0-alpha.0 allows any compatible 0.1.x release). To move to a specific version or a new range on purpose:

1
npm install @lad-sapienza/scms-core@<version>
2
# or, to track the latest alpha:
3
npm install @lad-sapienza/scms-core@alpha

After Updating

1
# Check the production build still succeeds
2
npm run build
3

4
# Test locally
5
npm run dev

Since @lad-sapienza/scms-core exposes its options (contentDir, pagesDir, galleriesDir, etc.) through the scms() integration in astro.config.mjs, a genuinely breaking framework release will show up as a build or type error at this point — the same way any other npm dependency’s breaking change would.

If Something Breaks

Roll back to your previous version:

1
npm install @lad-sapienza/scms-core@<previous-version>

Since the framework lives entirely in node_modules, this is a normal package.json/lockfile change — commit it or revert it with git like any other dependency bump.