4 Commits

Include renames

Author	SHA1	Message	Date
Jean-Luc Makiolaandmakiolaj	5f07adef2f	Release v2.22.0 (#355) ... Views: navigation, transitions and split-view behaviour. See CHANGELOG.md for the full list. Co-authored-by: Jean-Luc Makiola <business@jeanlucmakiola.de> Reviewed-on: https://codeberg.org/jlmakiola/calendula/pulls/355	2026-10-01 16:21:11 +02:00
Jean-Luc Makiolaandmakiolaj	a1ed010963	docs(privacy): point the controller contact at support@ (#307) ... The Controller section of `docs/PRIVACY.md` names the address a reader writes to in order to exercise their rights under Art. 15-21 GDPR. That is a different kind of mail from a project enquiry, so it now points at `support@jeanlucmakiola.de` instead of `business@jeanlucmakiola.de`. Same change is going into Agendula, and the website's own Datenschutzerklärung already names `support@` in its § 1. `business@` stays reachable — it is just no longer the published address anywhere. `updated:` bumped to 2026-09-15, since the published policy changes. Two notes for review: - **Target branch.** CONTRIBUTING says to target the release branch named by the issue's milestone. The open milestones (2.21.0 and later) have no branches yet, so per the same section this targets `main` and says so — retarget it if you would rather it waited for one. - **No changelog entry.** The entries in `CHANGELOG.md` describe what changed for the person using the app, and nothing about the app changed here. Happy to add one under a new `## [Unreleased]` if you want the contact change to show up in the release notes. `business@` needs to keep accepting mail until this is live on jeanlucmakiola.de/calendula/privacy and the Play Console listing has caught up. Co-authored-by: Jean-Luc Makiola <business@jeanlucmakiola.de> Reviewed-on: https://codeberg.org/jlmakiola/calendula/pulls/307	2026-09-15 16:10:29 +02:00
makiolaj	512bf8c746	docs: shape the policy as the content entry the site renders ... Frontmatter carries the title, description and date, the body starts at the first section rather than repeating the title as an h1, and the maintainer note is an HTML comment — a blockquote would have rendered "edit this in a PR" onto the published privacy page.	2026-09-09 16:14:42 +02:00
makiolaj	04257e8a66	docs: the privacy policy moves into the repo ... The policy lived only as prose inside the website's Astro page, so it was the one user-facing document with no review, no history here, and no way to change it alongside the code that makes it true. docs/PRIVACY.md is now that text, transcribed from the published page so the wording is unchanged, and it becomes the source: the site's build checks this repository out beside itself and renders this file through an Astro content collection rather than keeping its own copy. One copy of the policy exists anywhere, so the two cannot drift. The README links it from Documentation and gains a Privacy section beside License. Agendula is being set up the same way.	2026-09-09 16:13:42 +02:00