Positioning: retarget "Built for Business" at named audiences, make the commercial offer visible, and drop speculative claims
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 55/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- content, documentation
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
From the 2026-10-08 positioning review.
- Named audiences. "Designed for businesses of all sizes" dilutes the message. Replace
businessSizeswith 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-cwaand 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.
- 主要语言
- Vue
- 星标
- 0
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
components-web-app/docs 的其他 Issue
-
Website: the docs site's own service worker can't install (navigateFallback "/" isn't precached)未关闭bug
难度 2/5 1-3 小时 新手友好度 70/100
components-web-app/docs#173 ·
-
bug
难度 2/5 1-3 小时 新手友好度 82/100
components-web-app/docs#169 ·
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
components-web-app/docs#152 ·
-
难度 3/5 1-2 天 新手友好度 58/100
components-web-app/docs#180 · 1 条评论 ·
-
enhancement
难度 4/5 3-5 天 新手友好度 48/100
components-web-app/docs#178 ·
查看 components-web-app/docs 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 68/100
cline/mcp-marketplace#2881 ·
-
[Project]: Tale未关闭
难度 2/5 1-3 小时 新手友好度 75/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
难度 1/5 1 小时以内 新手友好度 85/100
lingdojo/kana-dojo#31936 · 1 条评论 · 5 个 reaction ·
维护者通常 1 天内回复
-
[Tool]: Tale未关闭
难度 1/5 1-3 小时 新手友好度 82/100
withkarann/aifoxx#392 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 76/100