mirror of
https://github.com/Luchexx/wacrm.git
synced 2026-11-02 09:19:51 +00:00
e46844d527
Per Meta's brand-use guidance for third-party products, the registered
trademark symbol (®) should appear on the FIRST mention of "WhatsApp"
on each user-facing page. Subsequent mentions on the same page are
left plain.
Surfaces touched (one-per-page first mention):
- Landing hero badge ("Built on the official WhatsApp® Business API").
- src/lib/seo/site-config.ts: SITE_TAGLINE and SITE_DESCRIPTION
(rendered into <title> and <meta description> on every page).
- src/app/opengraph-image.tsx: hero text in social-share image.
- Settings, Inbox connection banner, Automations page subtitle.
- README.md tagline.
- All public docs pages (docs/README.md, docs/whatsapp-setup.md,
docs/getting-started.md, docs/supabase-setup.md,
docs/environment-variables.md, docs/deployment-hostinger.md,
docs/automations-and-cron.md, docs/architecture.md,
docs/troubleshooting.md).
Out of scope: SITE_KEYWORDS (the meta-keywords array isn't
user-rendered text — putting ® on every keyword would look broken in
the meta tag).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| architecture.md | ||
| automations-and-cron.md | ||
| deployment-hostinger.md | ||
| environment-variables.md | ||
| getting-started.md | ||
| README.md | ||
| supabase-setup.md | ||
| troubleshooting.md | ||
| whatsapp-setup.md | ||
WaCRM documentation
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
Setup
- Getting started — fork the repo, install, run locally.
- Supabase setup — create the database, run the migrations, grab the keys.
- WhatsApp setup — create a Meta app, connect a phone number, wire the webhook.
- Environment variables — the full reference.
Deploy
- Deploy on Hostinger — Managed Node.js Hosting walkthrough, the recommended way to ship the template.
- Automations cron — schedule the pending executions drain so waits and delays fire.
Reference
- Architecture — stack, folder layout, request lifecycle, where to change things.
- Troubleshooting — the usual suspects.
What you will need before starting
- A GitHub account (to fork the repo).
- A Supabase project on any paid or free tier.
- A Meta for Developers account with a WhatsApp Business app.
- A WhatsApp phone number that is not already tied to the regular WhatsApp or WhatsApp Business mobile apps.
- A Hostinger Managed Node.js Hosting plan (or any Node host that runs long-running Node.js 20+ processes).
Stack at a glance
- Frontend / API — Next.js 16 (App Router), React 19, Tailwind v4.
- Database + auth + storage — Supabase (Postgres + RLS).
- WhatsApp transport — Meta Cloud API (official WhatsApp Business API).
- Encryption — AES-256-GCM for per-user WhatsApp access + verify tokens at rest. Legacy CBC-encrypted rows self-heal on next use.
- Scheduler — cron (or any pinger) that hits
GET /api/automations/cron.
Getting help
If something is unclear or broken, open an issue against the source repo: https://github.com/ArnasDon/wacrm/issues.