Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado
  • ¿Algo no está bien?
#176 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
nuxt, symfony
Área
content, documentation

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Vue
Estrellas
0
Forks
0
Merge medio
1 h 20 min
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de components-web-app/docs

Todos los issues de components-web-app/docs

Issues similares

Más issues de Content

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.