Getting updates

Your license includes ongoing template updates. Updates are delivered through the template repository — you pull them into your fork with plain git. This page is the workflow.

One-time setup

After cloning your delivery snapshot into your own private repository, add the template repository as a second remote:

git remote add template <template-repo-url>
git fetch template

Keep origin pointing at your own repository; template is read-only.

Pulling an update

git fetch template
git log --oneline HEAD..template/main   # review what changed
git merge template/main                 # bring it in

Conflicts happen where you customized the same files the update touches — usually pages you rebranded. Resolve them keeping your copy for content and taking the template's copy for logic, then rebuild:

pnpm install
pnpm --filter @repo/database build   # regenerate the Prisma client
pnpm --filter web typecheck
pnpm --filter web build

If a release note mentions a schema change, push it to your database before deploying:

npx prisma db push --schema=packages/database/prisma/schema.prisma

Minimizing conflicts

• Keep your identity in Site settings (/admin/settings) and environment variables, never hardcoded in components — that is what they are for, and it keeps your diff against the template close to zero.
• Add new pages and components in new files rather than heavily rewriting template files.
• Commit your own work before merging an update, so a bad merge is always one git merge --abort away from safety.

Release notes

Every update lands with a conventional-commit history (feat(...), fix(...)), so git log template/main doubles as the changelog. Breaking changes and required migration steps are called out in the commit body.