diff --git a/README.md b/README.md index 3ca0d5d..45dcc2e 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # WaCRM -> Self-hostable WhatsApp CRM template — shared inbox, contacts, sales +> Self-hostable WhatsApp® CRM template — shared inbox, contacts, sales > pipelines, broadcasts, and no-code automations. Fork it, brand it, > host it. diff --git a/docs/README.md b/docs/README.md index b7e03bb..ba9b925 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,6 +1,6 @@ # WaCRM documentation -WaCRM is a self-hostable WhatsApp CRM built on Next.js and Supabase. These +WaCRM is a self-hostable WhatsApp® CRM built on Next.js and Supabase. These docs walk you from a freshly forked repo to a production deploy. ## Reading order diff --git a/docs/architecture.md b/docs/architecture.md index c6f0ee3..215b8fe 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -10,7 +10,7 @@ want to change something in your fork. | Rendering | **Next.js 16** (App Router) | Server components for data-fetch pages; client components where interactivity's needed. React 19. | | UI | **Tailwind v4** + **shadcn/base-ui** primitives | Tailwind's zero-runtime styling, shadcn patterns for composable, dark-theme-first components. | | Data + Auth | **Supabase** | Postgres with Row-Level Security, built-in email/password auth, Storage for avatars, Realtime for the inbox. | -| WhatsApp | **Meta Cloud API** | Official Business API. No third-party gateway. | +| WhatsApp® | **Meta Cloud API** | Official Business API. No third-party gateway. | | Encryption | `node:crypto` AES-256-GCM | Per-user WhatsApp access + verify tokens at rest. | | Scheduler | External HTTP pinger | Hits `GET /api/automations/cron` to drain Wait-step executions. | diff --git a/docs/automations-and-cron.md b/docs/automations-and-cron.md index e269f0d..27c8366 100644 --- a/docs/automations-and-cron.md +++ b/docs/automations-and-cron.md @@ -1,6 +1,6 @@ # Automations cron -WaCRM's **Automations** module lets you build flows that react to WhatsApp +WaCRM's **Automations** module lets you build flows that react to WhatsApp® events (new message, new contact, keyword match, schedule, etc.). Most steps run inline — the exception is the **Wait** step, which parks the execution in `automation_pending_executions` until its due time. diff --git a/docs/deployment-hostinger.md b/docs/deployment-hostinger.md index 351ef21..c57da27 100644 --- a/docs/deployment-hostinger.md +++ b/docs/deployment-hostinger.md @@ -101,7 +101,7 @@ plain-HTTP version. ## 7. Update the Meta webhook -Back in **Meta for Developers → WhatsApp → Configuration**, change the +Back in **Meta for Developers → WhatsApp® → Configuration**, change the callback URL to `https:///api/whatsapp/webhook` and re-verify. ## 8. Schedule the automations cron diff --git a/docs/environment-variables.md b/docs/environment-variables.md index 4e5be78..19b5ab5 100644 --- a/docs/environment-variables.md +++ b/docs/environment-variables.md @@ -56,7 +56,7 @@ AUTOMATION_CRON_SECRET=generate-a-long-random-string - Rotate `SUPABASE_SERVICE_ROLE_KEY` if it leaks — Supabase lets you regenerate it under Project Settings → API. - Treat `ENCRYPTION_KEY` like a database master key. Losing it means - connected WhatsApp accounts must reconnect; rotating it means the same. + connected WhatsApp® accounts must reconnect; rotating it means the same. ## Next step diff --git a/docs/getting-started.md b/docs/getting-started.md index ac83cfe..aa51252 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -30,7 +30,7 @@ cp .env.local.example .env.local You cannot run `npm run dev` until **at least** `NEXT_PUBLIC_SUPABASE_URL` and `NEXT_PUBLIC_SUPABASE_ANON_KEY` are set. You need the full Supabase -setup before WhatsApp features will work, so do that next. +setup before WhatsApp® features will work, so do that next. ## 4. Set up Supabase diff --git a/docs/supabase-setup.md b/docs/supabase-setup.md index 85bbd73..019fd52 100644 --- a/docs/supabase-setup.md +++ b/docs/supabase-setup.md @@ -75,7 +75,7 @@ emails link back correctly. ## 6. (Optional) Storage -WaCRM downloads WhatsApp media through Meta's `/download` endpoint and +WaCRM downloads WhatsApp® media through Meta's `/download` endpoint and currently relays it on demand rather than caching it in Supabase Storage. No bucket setup is required for a default install. diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index b5c6283..ca06348 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -41,7 +41,7 @@ In Supabase → **Authentication → Providers → Email**, either: Set `NEXT_PUBLIC_SITE_URL` **and** add the same origin to Supabase → **Authentication → URL Configuration → Redirect URLs**. -## WhatsApp +## WhatsApp® ### Webhook verification fails in Meta diff --git a/docs/whatsapp-setup.md b/docs/whatsapp-setup.md index 94afeb1..3f1ac8c 100644 --- a/docs/whatsapp-setup.md +++ b/docs/whatsapp-setup.md @@ -1,6 +1,6 @@ # WhatsApp setup -WaCRM talks to the official **WhatsApp Business Cloud API** (Meta). Each +WaCRM talks to the official **WhatsApp® Business Cloud API** (Meta). Each account stores its own `phone_number_id`, `waba_id`, and encrypted `access_token` — there is no shared app-level token. This page walks through getting those values and wiring the webhook. diff --git a/src/app/(dashboard)/automations/page.tsx b/src/app/(dashboard)/automations/page.tsx index 021ae6e..9780853 100644 --- a/src/app/(dashboard)/automations/page.tsx +++ b/src/app/(dashboard)/automations/page.tsx @@ -159,7 +159,7 @@ export default function AutomationsPage() {

Automations

- Build workflows that react to WhatsApp events automatically. + Build workflows that react to WhatsApp® events automatically.