Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Positioning: retarget "Built for Business" at named audiences, make the commercial offer visible, and drop speculative claims

Aperta
  • Qualcosa non va?
#179 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
55/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
content, documentation

Direzione di ricerca

Start by locating the "Built for Business" positioning page and its FAQ; the issue does not name file paths. Update the audience profiles, make the paid offer and contact route visible, and remove or qualify unsupported claims. Done means the page reflects the requested audiences and real product capabilities, with the PHP, Vue and Docker/Kubernetes requirements stated plainly.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

From the 2026-10-08 positioning review.

  • Named audiences. "Designed for businesses of all sizes" dilutes the message. Replace businessSizes with three named profiles:
    • Agencies: one component library reused across clients; no per-seat CMS fees to pass on.
    • Symfony / API Platform teams: "your API stays Symfony; get a Nuxt front end with page building". Sulu markets to agencies as a Symfony CMS (sulu.io/for-agencies) but has no Vue path.
    • Teams that must self-host: data residency, no lock-in, MIT.
  • Say the cost plainly. Remove "Small businesses: admins with no code knowledge … create, edit and extend any CWA website". A small business needs a developer or agency, so frame it as the agency's client. Add an FAQ that says plainly the stack needs PHP + Vue + Docker/Kubernetes, and the payoff: create-cwa and the template already do the Kubernetes/CI setup.
  • Commercial offer. The paid path is buried in FAQ answers with mismatched links. Add a visible "Need it built, migrated or supported?" block: Silverback Web Apps, the maintainers, offers builds, support and hosting setup, with a contact CTA. Rewrite "What guarantees are given?" so it names the support routes. Open-source competitors pair MIT code with a clear paid path (Payload Enterprise, Statamic Pro, Directus commercial).
  • Speculative claims. "Automate AI content" (auto-creating blog entries on a schedule), "A/B testing" and "Unified brand visibility" describe things the product doesn't provide. Show the real mechanism (e.g. "any service can create draft components through the REST API; editors review and publish") or cut them.
Lingua principale
Vue
Stelle
0
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di components-web-app/docs

Tutte le issue di components-web-app/docs

Issue simili

Altre issue su Content

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.