Description
We want to remove the current newsletter signup A/B branching from EmailSignUpWrapper so that the illustrated newsletter signup card is always rendered by default.
We should keep the AB testing infrastructure in place because we expect to add a new AB test soon for the preview-button experiment. The goal is to remove the current test’s branching and dead paths, not to strip out reusable AB plumbing.
Scope
- Remove
SecureSignup / EmailSignup branching from EmailSignUpWrapper
- Always render the illustrated newsletter signup card flow
- Remove
variantNewField handling from this wrapper
- Keep the AB testing infrastructure intact for future experiments
- Keep the
abTest prop plumbing in the child form so it can be used again next week
- Stop passing the current AB variant through the flow for this implementation
- Use stable component IDs for the current illustrated card flow, without removing AB support from the shared tracking system
- Update wrapper tests to reflect the always-on illustrated card behavior
What remains unchanged
- Shared AB infrastructure and helpers
- The ability to add a future AB test for the preview button
- Existing tracking utilities unless they are directly required for this wrapper cleanup
- Other components that still rely on AB plumbing
- Any broader tracking refactors that are not necessary for this specific wrapper change
Out of scope
- Removing or refactoring shared AB infrastructure
- Broad cleanup of newsletter tracking utilities
- Implementing the new preview-button AB test
- Large-scale refactors outside the newsletter signup flow unless needed for this cleanup
Acceptance criteria
EmailSignUpWrapper always renders the illustrated newsletter signup card
SecureSignup / EmailSignup branching is removed from this wrapper
variantNewField handling is removed from this wrapper
- AB testing infrastructure remains available for future experiments
- The child form still supports
abTest plumbing for future use
- The current AB variant is no longer used to decide the rendered signup UI
- Wrapper tests are updated to match the new default behavior
Notes
This change should be kept focused on the newsletter signup wrapper and its tests. The intention is to remove the current experiment’s branching while preserving the AB plumbing needed for upcoming work.
Description
We want to remove the current newsletter signup A/B branching from
EmailSignUpWrapperso that the illustrated newsletter signup card is always rendered by default.We should keep the AB testing infrastructure in place because we expect to add a new AB test soon for the preview-button experiment. The goal is to remove the current test’s branching and dead paths, not to strip out reusable AB plumbing.
Scope
SecureSignup/EmailSignupbranching fromEmailSignUpWrappervariantNewFieldhandling from this wrapperabTestprop plumbing in the child form so it can be used again next weekWhat remains unchanged
Out of scope
Acceptance criteria
EmailSignUpWrapperalways renders the illustrated newsletter signup cardSecureSignup/EmailSignupbranching is removed from this wrappervariantNewFieldhandling is removed from this wrapperabTestplumbing for future useNotes
This change should be kept focused on the newsletter signup wrapper and its tests. The intention is to remove the current experiment’s branching while preserving the AB plumbing needed for upcoming work.