docs: record newsletter signup architecture decision - #51
Merged
Conversation
…tup steps Evaluated 'CRM + backend', 'API -> Google Form', and 'browser -> Google Form directly' against the existing Mailchimp direct-POST scaffold in NewsletterSignup.tsx. Recommendation: keep the direct-post pattern (no new server), matching the /contact recommendation in BACKLOG section 10.6 for the same static-export/no-server constraint. Documents that this is now purely an account/config task, and adds a step-by-step for pulling the action URL and hidden field name out of Mailchimp's embedded-form generator into site.ts. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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.
Evaluates the CRM+backend / API-to-Google-Form / direct-to-Google-Form / Mailchimp options raised for newsletter signup against the site's static-export, no-server constraint.
Decision: keep the existing Mailchimp direct-POST scaffold in \NewsletterSignup.tsx\ — no new backend, consistent with the /contact recommendation already in \BACKLOG.md\ section 10.6. This is now purely an account/config task (someone with Mailchimp access pastes two strings into \site.ts), not an engineering one.
Changes:
Docs-only; no source/snapshot changes, so no static-site regeneration needed. \check:content\ passes.
Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com