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

Aperta
  • Qualcosa non va?
#1,545 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
frontend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
0
Fork
4
Merge medio
5h 36m
PR unite (30g)
509

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Controlvar/controlvar

Tutte le issue di Controlvar/controlvar

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.