# What's new for users

Guideline content by [Lucas Vitti](https://lucas.mat.br), licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). See [scope and attribution](LICENSE.md).

This history explains practical changes for people reading and applying the development guidelines. It starts with 3.1.0; earlier editions remain documented in the [technical changelog](changelog.html). Dates identify the entries, and availability is recorded separately.

## 3.2.0 — 2026-10-25

**Availability:** Prepared on 2026-10-25; public availability is confirmed by the edition displayed at the live guidelines URL.

- **Reuse the guidelines:** You may share, translate, and adapt the covered guideline material, including commercially, under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
- **Give linked credit:** Please credit [Lucas Vitti](https://lucas.mat.br) and link to his site where reasonably practicable. Keep the guideline source and license links and say what you changed. The [License page](license.html) provides a ready-to-copy example.
- **Find the terms easily:** Choose **License** on the guidelines page, or **Scope and attribution** at the bottom of any current document. A Markdown copy is available for download.
- **Your applications stay separate:** The license applies to the guideline material. It does not change the license of your applications or require them to be open source.
- **Two ways to catch up:** This edition also includes the user and technical histories introduced in 3.1.0, so you can read practical changes or their full technical explanation.

## 3.1.0 — 2026-10-25

**Availability:** Local preview only; not published as of 2026-10-25.

- **Two release histories:** When you adopt this edition, each project version needs both a full technical record and a short account of what changed for its users. The short account explains new features, moved buttons, renamed or removed pages, fixes, and any action people need to take.
- **A simpler way to catch up:** Choose **What's new for users** on the guidelines page for this summary. Choose **Technical changelog** for the full account. The previous Changelog link is now labeled Technical changelog and still opens the same destination.
- **A template to help you write:** The new [user changelog template](user-changelog-template.html) shows how to describe practical changes in ordinary language. The existing [technical version journal template](version-journal-template.html) retains the full record.
- **Internal-only updates stay honest:** When a version has no visible effect on users, its user entry says "No user-visible changes in this version." It should not invent features or benefits.
- **What you need to do:** When adopting 3.1.0 for future work, keep both histories together in the project's documentation folder and check that their version and availability agree. Existing projects can begin at an agreed version and identify older gaps; reconstructing their entire history is not required.

This edition is available for local review. The website has not been updated by this release.
