Prototype: untangle Step 2 of the signup form (opt-ins vs intent) - #1014
Draft
RisingOrange wants to merge 15 commits into
Draft
Prototype: untangle Step 2 of the signup form (opt-ins vs intent)#1014RisingOrange wants to merge 15 commits into
RisingOrange wants to merge 15 commits into
Conversation
Reworks Step 2 of the signup form into the two-axis model for the onboarding design meeting (suggestion only, not intended to merge as-is): - 'Keep me informed' becomes an honest INFORMATIONAL opt-in (global + local chapter updates), replacing the 'connect me with my local chapter' wording that gated nothing. - Involvement tier (Act now / Volunteer / Lead) gates active chapter contact; Volunteer/Lead auto-include the informational opt-in (shown, not asked). - Critical-alert floor notice shown under the opt-ins. - Drops the 'at least one tick' requirement so a critical-alerts-only signup (privacy box only) is reachable, which the notice's premise assumes.
The auto-checked, locked 'Keep me informed' for the Volunteer/Lead tiers was a forced marketing-consent, which can't be freely given (worse than a pre-tick: the user can't refuse). The informational opt-in is now a genuine, uncheckable opt-in for everyone; operational volunteer comms would ride legitimate interest separately rather than a forced newsletter tick. Keeps the honest informational wording, the critical-alert floor notice, and the no-mandatory-one submit.
Reuse the shipping notice string from PR #1010 ('...even if you don't opt into any of these...') instead of a bespoke variant, so the prototype and the in-flight notice read the same. The wording fits V2 even better than the current form, since V2 drops the tick-at-least-one rule that made 'opt into nothing' impossible.
✅ Deploy Preview for pauseai ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…ree-to-share Matches the policy's actual mechanism (chapter sharing disclosed on a legitimate-interest basis = notice, not consent). Model-agnostic: acknowledgement works under joint controllership too. The 'shared with a separate entity' framing is left for the joint-controllership / privacy-policy V3 pass.
RisingOrange
changed the title
RisingOrange
changed the title
…owse page and confirmations
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For reviewers: the two things worth signing off on are (1) the reworked page-2 copy, in the "after" screenshot below, and (2) the "What each choice results in" table (which emails each choice leads to). To try the form live: open the preview (the reworked step is page 2).
What it changes (Step 2)
Mostly it untangles the current intent step rather than redesigning it. Two different kinds of choice are jumbled together there today:
The proposal cleans up the specifics:
What each choice results in
🔔 "Keep me informed" is an opt-in, independent of the intent choice. Ticking it adds the global newsletter (everyone) and chapter updates (for non-volunteers). None + 🔔 off = critical-alerts only; None + 🔔 on = the "keep me informed" signup. Act now gets the same treatment as None here — it's a signup-experience distinction (they see the action cards), not a contact tier.
‡ legitimate interest: Volunteers/Leads signed up to volunteer, so we can contact them about it without a 🔔 tick (the bell gates only their global newsletter; list-scoped unsubscribe still applies). Local CTAs, personal outreach, and chapter updates all rest on that basis without a 🔔 tick, which is why the Volunteer and Lead options now say chapter updates are included.
✓ yes · — no · "if 🔔" = only if Keep me informed is ticked · 📰 Substack is a separate-platform opt-in.
Chapter-scope note: the "None + no 🔔" cohort (opted into nothing → critical-alerts-only) is kept out of chapter scope entirely — a chapter never sees or contacts them; they receive only Global's critical alerts. So chapter scope = people who opted in or picked an intent (Act now / Volunteer / Lead), never the pure critical-only cohort. (A decided direction for the still-open #139 chapter-scope question.)
Open questions about the table
Draft / design proposal for the redesign discussion, not intended to merge as-is; it exists so the reworked step can be clicked through. The preview is safe to open: the form performs no Airtable write without an API key configured.