Files
calendula/docs
Jean-Luc Makiola a9c67a5827 feat(about): add Ko-fi support link
Add an optional way for users to support development:

- About card: tonal "Support development" button opening ko-fi.com
  via ACTION_VIEW (no INTERNET permission), EN + DE strings
- F-Droid metadata: Donate field in self-hosted and official drafts
- README: short Support section with the Ko-fi link

No perks/rewards attached — kept as a plain donation link.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-25 12:39:49 +02:00
..

Documentation map

Where to look for what:

Document What it is
ARCHITECTURE.md Orientation tour: principles, layers, navigation, recurring-write / conflict / reminder pipelines, testing
../CHANGELOG.md Release history (Keep a Changelog, SemVer)
../.planning/ROADMAP.md Living roadmap: shipped milestones, current scope, idea backlog
../.planning/PROJECT.md What the project is, stack, naming, infrastructure
../.planning/REQUIREMENTS.md Requirement checklist per milestone
../.planning/STATE.md Snapshot of where development currently stands
superpowers/specs/ The original design spec (2026-06-08) — historical record, not updated
superpowers/plans/ Per-milestone implementation plans with task checklists — historical record of how each slice was built, including provider lessons learned
../fastlane/metadata/android/ Store metadata (single source of truth): descriptions, title, icon, screenshots (DE + EN). Harvested directly by the official F-Droid repo; transformed into the self-hosted repo layout at release time by ../scripts/fastlane_to_fdroid_localized.sh
../fdroid-metadata/ App-level F-Droid control file (*.yml: Categories, License, links) for the self-hosted repo's fdroid update
fdroid-official/ Draft recipe + notes for publishing to the official F-Droid repo (reproducible build + developer-signed binary)

Conventions: plans and specs under superpowers/ are point-in-time artifacts of the agentic workflow that built each milestone — they get status updates but are never rewritten. The .planning/ files are living documents and should stay current.