feat: replace Supporter checkbox with Endorser field (v1.0.6) - #381
Merged
Conversation
…anch) Replace the outdated path-config model and 'staging branch unused' note with the verified per-site GitHub Integration settings (Include/Delete toggles), the main->prod / staging->staging branch mapping, a hard warning never to enable the 'Delete files not in repository' toggles (repo only contains bd4d), the mu-plugins-not-deployed caveat, and the feature->staging->main workflow. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Snapshot of the current auto-reply copy per case (pre-Endorser) as a reference doc. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Form: Supporter checkbox -> new Endorser checkbox, mapped to the new Airtable field 'Endorser?'. The Supporter field ('CotW-Opted In?') is no longer written but retained in Airtable for historical opt-ins.
- Auto-reply email: refreshed copy for all cases (endorser welcome + confirmations, updated Adoption copy) and new subject 'Welcome to a Better Deal for Data'.
- On-page success message: '...the BD4D Standard, and the movement...'.
- Require an email when any opt-in checkbox is ticked, surfaced via the browser's native validation popup on the email field (matching the required first/last name fields); checkboxes are no longer disabled.
- Bump version to 1.0.6.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Reflect the v1.0.6 auto-reply copy: Endorser replaces Supporter, refreshed Adoption (Case D) copy, and the new subject line. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Summary
Replaces the Supporter checkbox on the contact form with a new Endorser checkbox, tracking Endorser opt-ins in a new, separate Airtable field (
Endorser?). The Supporter field (CotW-Opted In?) is retained in Airtable for historical opt-ins but is no longer written by the form.Changes
Endorser?). Checkboxes stay enabled; an email is required when any opt-in is ticked, surfaced via the browser's native validation popup on the email field (same UX as the required first/last name fields).Welcome to a Better Deal for Data.Endorser?written;CotW-Opted In?no longer sent (field/history preserved).EMAILCASES.md(email cases reference) + deployment-workflow README update.Airtable
The
Endorser?Checkbox column already exists in the base, so deploys write cleanly (no 422).Test plan
Endorser? = checked;debug.logshowsAirtable API responded HTTP 200.🤖 Generated with Claude Code