A visual page editor: change a live page's text and layout to make a variant, with no code

Abierto
  • ¿Algo no está bien?
#1,545 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
8/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
javascript
Área
frontend

Línea de trabajo

This is a planning issue with no files or tests named, so there is no code to start from. Read the linked split-URL testing issue (#393) and the browser SDK to see how variants are chosen today. The issue says it will be planned after launch through the full drafting and review process, with a security review, so do not start an implementation. Done here means maintainers have accepted a written plan.

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

Descripción

enhancement post-launch

A visual page editor: a person opens a live page of their own site, changes its text, images or layout in an overlay, and those changes become an experiment's variant, with no code.

Why

Today every variant is built in the application's code, and the app asks an SDK which variant each user gets. That suits engineering teams. A marketer who wants to test a headline or a button needs an engineer for each change. Split-URL testing (#393) is the first no-code path: two versions of a page at two URLs, with visitors split between them.

What it involves (to be planned)

  • An editor that overlays the live page and records changes (by element selector).
  • A stored model for those changes, attached to a variant.
  • A runtime in the browser SDK that applies them before the page paints, so visitors do not see a flicker.
  • URL targeting, and a preview of each variant.
  • A security review: the product would change pages it does not own, so how changes are stored, validated and applied matters (script injection, Content-Security-Policy).

Plan

Planned after launch through the full process (drafters, then review), with a security review.

Lenguaje dominante
Python
Estrellas
0
Forks
4
Merge medio
5 h 36 min
PR fusionados (30 d)
509

Preparar el entorno

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 Controlvar/controlvar

Todos los issues de Controlvar/controlvar

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.