Idea: per-release refresher modules

Idea from 2026-06-17, recorded so it is not lost: per-release refresher modules.

Nextcloud app development changes every release — APIs get deprecated, @nextcloud/vue has breaking changes, the test suite shifts. A course written once is stale within two releases, and the content already carries version-specific notes (NC34 specifics, "jQuery and old globals are gone", Vite replacing Webpack in 2025).

The idea

A short module per release covering what changed for app developers, sourced from:

• the Nextcloud developer documentation changelog
• @nextcloud/vue changelogs
• test suite release notes

Open questions

• Does this scale, or does it become a maintenance burden that outlives the motivation to write it?
• Is it better served by a "what changed" section in each release's docs rather than course modules?
• Who owns it — this is a recurring commitment, unlike every other issue here

Not scoped further. Worth a decision before it is worth work.

Review the Nextcloud developer documentation changelog, @nextcloud/vue changelogs, and test suite release notes to assess the proposed sources. First resolve whether recurring modules or per-release documentation sections are sustainable, then define ownership and a repeatable scope; done means an agreed format, responsibility, and initial release plan.