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>
69 lines
2.3 KiB
YAML
69 lines
2.3 KiB
YAML
name: Feature request
|
|
description: Propose a new feature or a meaningful enhancement.
|
|
title: "[feat] "
|
|
labels: ["enhancement", "triage"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for the idea — but read this first.
|
|
|
|
This is a **template**, not a collaborative product. The
|
|
upstream scope is intentionally narrow, so most feature
|
|
requests end up as *"build this in your fork"* rather than
|
|
landing here. That's the point of a template.
|
|
|
|
When an upstream feature request *is* useful:
|
|
|
|
- It fixes a correctness problem in the template.
|
|
- It makes the template cleaner for the next forker (reducing
|
|
friction, removing footguns).
|
|
- It's in scope for "a generic WhatsApp CRM template" rather
|
|
than a bet on your specific workflow.
|
|
|
|
If the feature is really for your own deployment, fork and
|
|
build it there — see
|
|
[CONTRIBUTING.md](https://github.com/ArnasDon/wacrm/blob/main/CONTRIBUTING.md).
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: What's the problem?
|
|
description: What are you trying to do today that the template makes harder than it should?
|
|
placeholder: |
|
|
When a broadcast ends I have no way to see which recipients
|
|
didn't reply so I can follow up manually.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: proposal
|
|
attributes:
|
|
label: What would you like to see?
|
|
description: Describe the feature from the user's perspective, not the implementation.
|
|
placeholder: |
|
|
On the broadcast detail page, a "No reply" filter that lists
|
|
recipients who received but didn't reply within 24 hours.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Alternatives you considered
|
|
description: Things that kinda work today, workarounds, related features in other tools.
|
|
validations:
|
|
required: false
|
|
|
|
- type: dropdown
|
|
id: scope
|
|
attributes:
|
|
label: Scope
|
|
description: Your guess — we'll re-scope if needed.
|
|
options:
|
|
- Small (a couple of hours)
|
|
- Medium (a couple of days)
|
|
- Large (a couple of weeks, probably breaks into multiple PRs)
|
|
validations:
|
|
required: false
|