Jean-Luc Makiola
2e47271904
Record core-reminders (multi-value) and the new components in CHANGELOG, README module table and the ROADMAP extracted list; clarify that only the reminder *scheduler* stays app-local. Also removes a leftover '>>>>>>> origin/main' merge-conflict marker committed in README by an earlier merge. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
floret-kit — documentation
floret-kit is the shared Material 3 Expressive design system + plumbing for
the Floret family of Android apps
(Calendula,
Agendula, and future
siblings). It is consumed from source as a git submodule + Gradle composite
build. See the top-level ../README.md for the pitch.
Index
| Doc | What it covers |
|---|---|
ARCHITECTURE.md |
How the kit is built and consumed — the module layering, JVM vs Android-library modules, the submodule + composite-build model, and the reproducibility rules. Start here. |
ROADMAP.md |
What's extracted, what's deferred, and what's deliberately not shared — the module status and the divergence decisions from the cross-app survey. |
../CONTRIBUTING.md |
The practical how — adding a module, the no-app-coupling rules, build/test, and how an app adopts the kit. |
../CHANGELOG.md |
Keep a Changelog; what each module added. |
The one principle
Share the mechanics, keep the look per-app.
Theme machinery, plumbing, and component primitives are shared; seed colours, palettes, identity chips, and app-specific wording stay in each app. This is what lets the family read as one design language without homogenising apps that are meant to have distinct personalities.