Update documentation to align terminology, clarify project stages, and improve consistency; add RECOMMENDATIONS.md for project-specific guidance.
This commit is contained in:
@@ -12,7 +12,7 @@
|
||||
---
|
||||
|
||||
## 1. Tone & Clarity
|
||||
- Professional, concise, finance-friendly. Emphasize trust (audit log, reasoning traces, secure billing and webhooks).
|
||||
- Professional and concise. Emphasize trust (audit log, reasoning traces, secure billing and webhooks).
|
||||
- Avoid jargon without tooltips; show why a decision was made (rule hit, similarity, LLM reasoning).
|
||||
|
||||
## 2. Responsiveness
|
||||
@@ -34,14 +34,14 @@
|
||||
- Require confirmation when enabling a high-priority rule; surface last editor and timestamp.
|
||||
|
||||
### Onboarding & Integrations
|
||||
- Display connection status/health for QuickBooks/bank webhooks; guide recovery/retry.
|
||||
- Stripe plan selection and post-checkout status must be clear and recoverable.
|
||||
- Display connection status/health for external providers and their webhooks; guide recovery/retry.
|
||||
- Payment plan selection and post-checkout status must be clear and recoverable.
|
||||
|
||||
### Reports & Exports
|
||||
- Show date range, currency, timezone; indicate processing state and download links when ready.
|
||||
|
||||
## 5. Payments & Billing UX
|
||||
- Use provider trust markers (Stripe) and keep users on provider-hosted flows.
|
||||
- Use provider trust markers and keep users on provider-hosted flows.
|
||||
- Post-return states: success, pending, failed; include retry/contact support options.
|
||||
|
||||
## 6. Support & Errors
|
||||
|
||||
Reference in New Issue
Block a user