== Background
As part of the work on donor ID and recognition, we want to run an experiment that will present donors with an on-wiki token of appreciation.
PRD: **[[ https://docs.google.com/document/d/1s9YRtV-zHMBSBrTembIodY_P3L86ryFXEkp8Wf60Txo/edit?tab=t.0 | Emotional Recognition: Post-Donation Experience (Lightweight badge interaction) ]]**
Experiment currently lays out a three bucket path (A/B/C) testing:
- A: Control. User donates but does not get a donor badge
- B: Plain. User donates and automatically gets a persistent donor badge. Tapping on it opens the plain thank-you message – similar to the first FR experiment.
- C: Delightful. User donates and automatically gets a persistent donor badge. Tapping on it triggers wiki-hearts plus a short acknowledgement message.
This task encompassed the **technical scoping **of this experiment. Technical scoping includes the following work:
- Reviewing designs for implementation feasibility.
- Structuring milestones or chunks of work (if needed)
- Writing the Phabricator tasks for this experiment
=== Design requirements
UI designs & workflows to be refined during this phase in collaboration with Design.
[[ https://www.figma.com/design/pkG9ssCFmdzKWp8aYQ8VRe/donor-recognition?node-id=105-19655&t=EhlOWdji724SRosY-4 | Figma Designs of A/B/C treatment ]]
=== Engineering requirements
- Clarifying where experiment is going to live
- What are pre-requisites:
-- Provide workflow diagram for all three buckets.
-- Setup TestKitchen experiment
- What are different requirements for groups:
-- A (Control): 0 engineering need.
-- B & C commonalities:
--- Take first FR experiment as orientation point.
--- Where does experiment code live
--- Clarify handling of sticker location (menu item, absolute positioned item)
---
-- B (Plain):
-- C (Delightful):
--- Provide animation (with randomization character, e.g. heart colors)
--- Hide this badge: Codex component or custom?
---
=== Acceptance criteria
- [] UI designs have been reviewed by an engineer
- [] Phabricator tasks for this experiment have been created (and ideally estimated).
- [] Workflow diagram can be handed to analyst in order to create an instrumentation plan.
//This task was created by Version 1.0.0 of the Reader Experience team task template using [[ https://phabulous.toolforge.org/ | phabulous ]].//