Updates

How updates work

Every template has a CHANGELOG.md that lists what changed in each version. Updates are pushed to the same repository you received — pull them whenever you like.

Lifetime access, no subscription.

Your files are safe

These files are yours and are never overwritten by updates:

• src/lib/site.ts — your business info
• src/i18n/*.json — your translations
• src/content/ — your menu, FAQ, legal content
• src/styles/global.css — your :root theme block
• src/assets/images/ — your photos

Update flow (Git)

git stash                # save your local changes
git pull origin main     # pull the update
git stash pop            # re-apply your changes

If there are conflicts, they will only be in your 4 customization files — resolve them by keeping your values.

Update flow (Zip)

1. Download the new zip
2. Extract into a fresh folder (do not overwrite your working folder)
3. Copy your customization files from the old folder:
   • src/lib/site.ts
   • src/i18n/en.json (and any other locale files)
   • src/content/ (entire folder)
   • src/styles/global.css
   • src/assets/images/ (your photos)
4. Run npm install && npm run build to verify

Checking the changelog

Always read CHANGELOG.md before updating. It tells you:

• Added — new features or pages
• Fixed — bug fixes
• Changed — modifications to existing behavior
• Migration (major versions only) — steps you need to take manually

Version numbers

Templates follow SemVer:

Version bump	Meaning	Action needed
PATCH (0.1.1)	Bug fix	Pull and go
MINOR (0.2.0)	New feature, backward-compatible	Pull and go
MAJOR (1.0.0)	Breaking change	Read migration notes first