mirror of
https://github.com/Luchexx/wacrm.git
synced 2026-11-02 17:29:45 +00:00
faee4eea44
Drops the "WaCRM" branded name across user-facing surfaces in favour
of a descriptive name. Branded names that imply WhatsApp ownership or
sponsorship are a trademark fair-use risk; a relationship-based name
("CRM Template for WhatsApp") sidesteps that.
Scope:
- Brand text in nav, sidebar, footer, docs shell, mock window chrome.
- SITE_NAME / SITE_DESCRIPTION / legalName in src/lib/seo/site-config.ts.
- README, CONTRIBUTING, docs/, .github/ templates and policies.
- package.json description.
- Auth pages, settings copy, FAQ, code comments.
Out of scope (intentionally — these are infra renames the project
owner should drive separately so links and the package lockfile stay
consistent):
- The github.com/ArnasDon/wacrm repo URL.
- The wacrm.tech domain / homepage field.
- The package.json "name" field.
- The Hostinger application name and Meta system-user name in deploy
docs (existing-deployment instructions).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
43 lines
1.3 KiB
Markdown
43 lines
1.3 KiB
Markdown
<!--
|
|
Heads up: this is a template, not a collaborative product. Most
|
|
changes belong in your fork. See CONTRIBUTING.md for which kinds of
|
|
upstream PRs tend to land (security, correctness, docs) vs. which
|
|
belong in a fork (new features, stack swaps, opinionated refactors).
|
|
If you haven't opened an issue yet for a non-trivial change, consider
|
|
doing that first to check alignment.
|
|
|
|
Keep this short and specific. The commit message is where the "why"
|
|
lives; this is where the reviewer gets the "what" and "how to try it".
|
|
-->
|
|
|
|
## Summary
|
|
|
|
<!-- One or two sentences. What does this PR do? -->
|
|
|
|
## What changed
|
|
|
|
<!-- Bullet list of the actual changes. Link file paths when useful. -->
|
|
|
|
## Test plan
|
|
|
|
<!--
|
|
How did you verify this works? How should the reviewer verify it?
|
|
Tick the boxes as you go.
|
|
-->
|
|
|
|
- [ ] `npm run typecheck` clean.
|
|
- [ ] `npm run lint` — no new errors beyond the pre-existing backlog.
|
|
- [ ] `npm run build` succeeds.
|
|
- [ ] Feature / fix manually exercised in the browser (or the reason it can't be).
|
|
|
|
## Related
|
|
|
|
<!-- Link the issue this closes, or "Part of #N" for multi-PR work. -->
|
|
|
|
<!--
|
|
Heads up:
|
|
- Security issues: do not disclose here; see .github/SECURITY.md.
|
|
- New deps: please justify briefly in the commit message or PR body.
|
|
- Runtime behaviour changes affecting forkers: update docs/*.
|
|
-->
|