Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
  • Is something wrong?
#179 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
content, documentation

Research direction

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.

Written by the indexing model from the issue text.

Description

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.
Dominant language
Vue
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from components-web-app/docs

All issues in components-web-app/docs

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.