Added behavior journal, adjusted layout, and added some colors
Deploy / deploy-prod (push) Skipped
Deploy / deploy-dev (push) Successful in 4m18s

This commit is contained in:
Corey Blais committed 2026-10-05 15:20:00 -04:00
1 parent b1b89ad334
commit 3237cd7601
31 files changed
+2135 -275

No files matched your search

+7
View File
@@ -272,3 +272,10 @@ This starter now includes the account and flock foundation for monetization, plu
Stripe billing should be attached to `workspaces`, not `users`. Each flock has its own billing plan, subscription status, Stripe customer ID, and Stripe subscription ID, which lets one person own multiple household flocks with separate subscriptions while rescue flocks can stay on the free rescue path.
For account design, `standard` vs `rescue` is best treated as a flock type, not as a user role. If paid plans are added later, a separate `admin account mode` is usually less flexible than flock roles such as `owner`, `assistant`, `caregiver`, and `viewer`. That lets the same underlying account system work for both households and rescues without splitting product logic into unrelated account classes.
## Customer API documentation
Open `/api/docs/` on your FlockPal instance for the interactive integration API reference,
or download `/api/openapi.json`. Locally, use `http://localhost:5000/api/docs/`.
Create a token in Settings → Integration tokens and use **Authorize** to try requests.
See [the API reference](docs/API_REFERENCE.md) for details.