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

Positioning: one value proposition across the site, a hero that names the audience, and an honest alpha status

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
nuxt, symfony
Domain
content, documentation

Research direction

Start by comparing content/index.yml:6, the Docs Introduction, llms.txt, and the docs banner against the proposed positioning and hero copy. Then review the home, about, and business pages, including /built-for-business, and check the commented hero links: block. Done means the site and docs use consistent audience-focused wording, the hero has the proposed calls to action and alpha badge, and the business FAQ explains project status and links to the changelog.

Written by the indexing model from the issue text.

Description

enhancement

From the 2026-10-08 positioning review.

The product is described three different ways.

  • Home (content/index.yml:6): "low-code solution … custom decoupled web apps including an intuitive website builder interface".
  • Docs Introduction: "a full-stack framework for building content-driven web applications with an inline CMS".
  • llms.txt: "A Symfony + Nuxt framework".

None of them names who it's for. "Low-code" sets the wrong expectation for the developers who decide whether to adopt it, because they write PHP and Vue for every component.

Proposed one-liner (to refine): "An open-source, self-hosted website platform for Symfony and Nuxt: your developers build the components, and your clients edit, draft and publish pages directly on the live site, which ships with the whole production stack."

Hero draft.

  • Headline: "Bespoke websites your clients can edit on the page."
  • Sub-head: "Open-source Symfony + Nuxt. Developers build the components; editors draft, schedule and publish in place, with no SaaS bill and no separate CMS."
  • CTAs: Try the live editor (preview.cwa.rocks), Get started, GitHub. The hero links: block is currently commented out, so the hero has no buttons.

Alpha status. Every docs page warns "alpha, not ready for production". The home, about and business pages never mention it, while claiming "Can CWA scale? Yes … impressive results". Add:

  • a small hero badge ("2.0 alpha: try it, build with it, give feedback");
  • a "Project status" FAQ on /built-for-business: what's stable, what may still change, the target for 2.0 stable, changelog links.

Make the docs banner use the same wording.

Audiences (positioning recommendation):

  1. agencies and freelancers building bespoke client sites without per-seat SaaS CMS bills;
  2. Symfony/API Platform teams that want a Nuxt front end with page building;
  3. organisations that need self-hosting and data ownership.
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.