Decide on mechanism by which we will trigger headless VE
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Esanders
	Jul 6 2026, 5:27 PM

Project Tags

Referenced Files

None

Subscribers

Description

At a high level we need to decided whether this will be triggered by page reads or page edits.
Also to decide are how/if we back fill data, and more detailed implementation details on how the actual job is run.

Related Objects
Search...

Status	Subtype	Assigned	Task
Open		None	T360489 [EPIC] Offer edit suggestions as a service
Open		None	T416531 [EPIC] Surface Edit Suggestions outside of VE
Open		None	T431076 [EPIC] Surface specific edit suggestions within articles (Phase 2)
Open		ppelberg	T428816 [EPIC] Surface edit suggestion counts to logged-in editors on articles (Phase 1)
Open		ppelberg	T430712 [EPIC] Launch controlled experiment of surfacing suggestion counts on articles to logged-in editors
Open		None	T426778 [EPIC] Streamline the suggestion browsing and publishing experiences
Resolved		Esanders	T425597 Suggestion Mode feedback toasts block me from advancing to next suggestion
Open		dchan	T423465 [SPIKE] Investigate creating a top-level model class for Edit Check
Open		GGoncalves-WMF	T428814 [EPIC] Ready server-side suggestions PoC for use in production
Open		ppelberg	T432266 [SPIKE] Define scale requirements for suggestion count controlled experiment (logged-in users)
Open		ppelberg	T432272 Add instrumentation to log suggestion counts shown in read and edit modes
Open		None	T432274 [Suggestion Counts on articles] Report on leading indicators
Open		None	T432288 [SPIKE] Determine cache invalidation approach for on-wiki config changes
Open		ppelberg	T432427 Publish experiment plan: read mode suggestion counts (logged-in)
Resolved		Ottomata	T432733 Server Side Edit Suggestions - Linked Artifacts Cache precompute job
Open		medelius	T432622 Prompt people to publish after completing first suggestion
Declined		None	T432759 Conduct usability testing of new post-Suggestion publishing prompt
Open		bmartinezcalvo	T412389 Suggestion Mode discoverability: Conduct moderated usability testing to understand how users discover suggestions in the article
Resolved	BUG REPORT	medelius	T413280 Suggestion mode - Don't expand any cards until clicked
Duplicate		None	T438909 Test holistically suggestion mode
Open		None	T428193 Suggestion Mode: Implement read mode entry point(s)
Resolved		cjming	T431493 [DE 1.1.9] An instrument that produces edit_survived events
Open		None	T433530 Backfill Edit Suggestion Counts in Linked Artifacts Cache for technical pilot
Open		None	T432286 [MILESTONE] Run technical pilot to evaluate Headless VE resource requirements
Open		Esanders	T428811 [EPIC] Deploy headless VE
Open		Esanders	T428491 [EPIC] Build a headless mode for EditCheck that scrapes suggestions and outputs them via an API
Resolved		Esanders	T431326 Decide on mechanism by which we will trigger headless VE
Open		None	T431320 Resolve tension between prominence of 'Help' and 'Suggestion Mode'
Resolved		dchan	T434960 Decide how Suggestion Counts and caching pageviews for logged-in users will work with one another
Resolved		mpopov	T437654 Constructive Activation metric in GrowthBook
Open		None	T437414 editSaved generic instrumentation doesn't handle edits made through other editors

Event Timeline

Esanders created this task.Jul 6 2026, 5:27 PM

For phase 1 we have decided this will be an MW JobQueue triggered by article edits.

Esanders closed this task as Resolved.Jul 20 2026, 5:59 PM

VPuffetMichel edited projects, added: OKR-Work; removed: Editing-team (FY2026-27 Q1 sprint 1), VisualEditor.Mon, Oct 5, 2:56 PM

VPuffetMichel added projects: Editing-team (FY2026-27 Q1 sprint 1), VisualEditor.Tue, Oct 6, 3:55 PM

Decide on mechanism by which we will trigger headless VEClosed, ResolvedPublicActions

Description

Related ObjectsSearch...

Event Timeline

Decide on mechanism by which we will trigger headless VE
Closed, ResolvedPublic
Actions

Related Objects
Search...