Newsletter entry points: "Get updates" nav item + homepage box -> /join - #1031
Draft
RisingOrange wants to merge 5 commits into
Draft
Newsletter entry points: "Get updates" nav item + homepage box -> /join#1031RisingOrange wants to merge 5 commits into
RisingOrange wants to merge 5 commits into
Conversation
Adds a "Get updates" nav item (mail icon) between "Get involved" and Donate, pointing at /join for now. Rendered leading-icon on desktop (WideNavbar) and trailing-icon on mobile (NarrowNavbar) so the label lines up with the other items. Also centers the nav row (align-items) so the taller item does not push the others up.
…ent signup The homepage newsletter box posted straight to Substack, which is a different thing from the CRM movement newsletter. Adds a joinHandoff mode to NewsletterSignup that instead sends the visitor to /join with the email prefilled (?subscribe-email=...), wiring OnboardingFlow to consume the previously-no-op initialEmail. Collage/learn keep the Substack behaviour.
✅ Deploy Preview for pauseai ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Now that the box leads to the signup form, "Subscribe to our newsletter" + "Subscribe" over-promised a one-click action. Heading -> "Get updates" (matches the nav), button -> "Sign up" (signals it continues to a form). Scoped to the homepage instance; Substack uses keep their copy.
Points "Get updates" (nav) and the homepage box at a new /subscribe post instead of /join. It reuses the same OnboardingFlow but with a newsletter title/subtitle and reads ?subscribe-email to prefill. Fixes the two /join-inheritance issues: wrong hero copy, and the nav highlighting "Get involved". Also gives "Get updates" its own active-state highlight. NewsletterSignup.joinHandoff -> handoffHref (destination configurable).
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.
Draft / proposal, not for merge as-is. Stages the first, low-risk pieces of the newsletter entry-points work for discussion (broader picture: the Step 2 onboarding proposal in #1014).
What this adds
1. A "Get updates" nav entry. A newsletter/updates item in the header, between "Get involved" and Donate, pointing at a new
/subscribepage (see 3). Leading mail icon on desktop; on mobile the icon trails the label so it lines up with the other items.Desktop
Mobile (menu open)
2. The homepage subscribe box now leads to the signup form. It used to subscribe you to Substack only. Now it hands off to the
/subscribepage with the email prefilled (?subscribe-email=...), so from the homepage you reach the full signup, the movement newsletter and more, rather than just Substack. The collage campaign and/learnkeep their Substack behaviour.3. A
/subscribelanding. Both entry points now land on a new/subscribepage instead of/join. It renders the same signup form, but with newsletter-appropriate framing (title "Get PauseAI updates") and reads?subscribe-emailto prefill. This fixes two things a shared/joincouldn't: the hero copy (/joinsays "Find the highest-impact way to help", off-target for a newsletter-seeker) and the nav highlight (on/jointhe header lit up "Get involved"; now "Get updates" highlights on its own page)./join (current signup page):
/subscribe (new):
The model, and a possible follow-up
/subscribereuses the same signup form, so a subscriber gives name / country / city and, through the keep-informed opt-in, becomes a local-chapter contact, exactly like anyone who signs up today. That is what this proposes. A lighter, genuinely newsletter-only tier (email only, no location, not shared with a chapter) is a possible follow-up, not part of this PR.Notes
?subscribe-emailquery param;/subscribereads it to prefillOnboardingFlow(wiring its previously-no-opinitialEmail)./subscribe?subscribe-email=…prefills the email; the nav item and homepage box both land there.Related: #1014 (onboarding Step 2 proposal), PauseAI/pauseai-civicrm#460 (self-service "change later").