Updating The Theme

Skill level: Intermediate (uses git)

When a new version of Consultiz is released, CHANGELOG.md in the theme lists what changed. The version you have is in package.json ("version").

Keep Updates Easy

The way you customize decides how easy updates are:

Change content and config, not components. Updates mostly touch components and styles, so a site customized through src/content/, src/config/, src/i18n/, and a few color tokens in theme.css is the easiest to update.
Use page blocks instead of editing section components when you only need different content on one page.
Commit often with clear messages, so you know which changes are yours.

Apply An Update With Git

Commit all your work, so your project is clean.
Create a branch for the update:
Terminal window
```
git checkout -b theme-update
```
Unzip the new version. Copy the files from its consultiz/ folder over your project, except src/content/, src/config/, src/i18n/, src/assets/images/, and public/ files you replaced (images, videos, PDFs, favicons). Check CHANGELOG.md for new content files or config keys and add them by hand.

Copying also replaces files you may have customized: src/styles/theme.css (your colors), route files you edited in src/pages/[...lang]/, README.md, package.json and package-lock.json (re-add any dependency you installed yourself, such as wrangler), and netlify.toml, vercel.json, vercel.sh, or wrangler.toml. Restore your versions of those in the next step, or skip them while copying.
Review the changes in the Source Control panel. Where a file has both your changes and the theme’s, keep both.
Run the checks:
Terminal window
```
npm ci
npm run astro-check
npm run build
```
Look through the site, then merge the branch into your main branch.

Updating Dependencies

npm outdated lists newer versions of the theme’s tools. Major updates of Astro or Tailwind CSS can need code changes; wait for a Consultiz release that includes them unless you are comfortable fixing build errors.