Versions and updates
How templates are versioned, where to find what changed, and how to update your site.
Every template stack has its own version number, shown on the template's page and in its download, and a changelog listing what changed in each release.
What the numbers mean#
Versions follow semantic versioning:
| Change | Example | Meaning |
|---|---|---|
| Patch | 1.1.0 → 1.1.1 | Fixes and documentation that don't change how the template looks or is organised |
| Minor | 1.1.0 → 1.2.0 | New pages, sections or features that are safe to copy into your site |
| Major | 1.2.0 → 2.0.0 | Redesigns or restructured files; read the changelog before updating |
Each stack of a template (HTML, Next.js, Astro, WordPress) is versioned separately, so their numbers can differ.
Finding what changed#
- Each template page has a Changelog section for the selected stack.
- Every download includes
CHANGELOG.md, so you can see which version you started from. - The changelog page lists site releases and the latest update to every template.
- If you have an account, templates you've downloaded are listed under Downloads, ready to grab again after an update.
Updating your site#
Templates are starting points, not dependencies: once you've customised one, there's nothing to upgrade automatically. To bring in an improvement:
- Read the changelog entries since your version.
- Download the new version and compare the files you care about with a diff tool.
- Copy over the parts you want (a fixed function in
assets/js/main.js, a new section, an updated component), keeping your own content.