alumni_lookup

Phase 17: Champions Landing Page & Legacy Signup Retirement

Status: Complete (17.1, 17.2, 17.3, 17.4)
Priority: High
Estimated Sub-Phases: 4

---

Overview

Create a publicly accessible landing page at belmontalum.com/champions (the redirect target for alumnichampions.com) that educates visitors about the Alumni Champions program and encourages them to create an account. Simultaneously retire the legacy champion signup flow (/signups/*) and ensure the ChampionSignup data conversion pipeline is preserved and documented.

Context

• alumnichampions.com will DNS-redirect to belmontalum.com/champions — it is NOT currently an accepted host domain (blocked from displaying anything)
• Existing /champion-info page (Phase 13.7) already has warm, well-written Champions education content — but it’s behind authentication (before_action :authenticate_cp_champion!). This is the prime candidate to adapt into a public page.
• Legacy signup flow at /signups/new (8-step quiz → ChampionSignup model) is obsolete — the modern flow is Devise registration (/signup) → email confirmation → profile wizard → onboarding
• The role quiz is NOT part of the wizard steps — it’s a separate optional action accessible from the profile wizard and roles pages. Champion role selection happens during onboarding, not during signup.
• ChampionSignup data IS actively used — Cp::ConfirmationsController has a conversion pipeline (find_legacy_signup_for → apply_legacy_signup_data) that pre-fills Cp::Champion profiles from old signup data during email confirmation. This must be preserved.
• ChampionSignup staff management is historical — will be used when marketing the new Alumni Network to convert old signups and reference their data during the signup process.

Goals

1. Educate & Convert (Champions): When someone already asking “how can I get more involved?” visits alumnichampions.com, they land on a page that shows them the impact they can make and how the Champions program solves what they’re trying to achieve
2. Clarify the Generic Landing Page: The existing / landing page needs to clearly articulate the two tiers — joining the Alumni Network, and then becoming an Alumni Champion — so visitors understand what they’re signing up for and what’s inside
3. Repurpose Existing Content: Adapt the existing /champion-info page (Phase 13.7) as the public-facing /champions page
4. Clean Architecture: Remove the legacy public signup flow while preserving the data conversion pipeline
5. Preserve Historical Data: Keep staff management tools and conversion pipeline for marketing push

---

Sub-Phase Plan

Phase 17.1: Public Champions Landing Page

Goal: Create a publicly accessible page at /champions (the redirect target for alumnichampions.com) that educates visitors about the Alumni Champions program and encourages signup.

Approach: Repurpose /champion-info

The existing /champion-info page (Phase 13.7, Cp::ChampionInfoController) already has excellent content:

• “What is an Alumni Champion?” section
• Three engagement tiers (Member, Champion, Community Leader)
• “What Changes When You Opt In?” benefits section
• Warm, zero-pressure, celebratory tone aligned with source docs

Plan: Create a new public version of this content at /champions that:

1. Is publicly accessible (no auth required)
2. Adapts the authenticated page’s content for an anonymous audience
3. Adds signup/login CTAs instead of role-management CTAs
4. Includes social proof (champion count, top cities — from existing LandingController pattern)
5. Includes a “How It Works” section mapping to the actual signup flow

Audience & Positioning

The /champions page targets people in the “second tier” of interest — alumni who are already asking:

• “How can I get more involved?”
• “How can I serve other alumni or current students?”
• “What can I do to help?”

These aren’t cold prospects. They’ve heard about the program (word of mouth, event, email, social) and are looking for the answer to “what does this actually look like?” The page must show them that the Champions program is the vehicle for the impact they want to make.

Tone: Purpose-driven, impact-focused, warm. Not recruitment. Not “join our numbers.” More: “Here’s how alumni like you are already making a difference — and here’s how you can too.”

Content Sections

1. Hero — Impact-focused, not program-focused
   • Lead with the outcome, not the label: what Champions actually do and the difference it makes
   • Speak to their motivation: serving, connecting, giving back
   • Primary CTA: Create an account / Get started
2. The Impact — What Champions actually do
   • Real examples of impact: a coffee meetup that turned into a job lead, a mentoring conversation, an alumni event in their city
   • Adapted from existing /champion-info content but reframed for an external audience who hasn’t seen it before
   • Show that “being a Champion” isn’t a title — it’s showing up intentionally
3. Four Ways to Serve — Champion roles framed as impact paths
   • Community Builder, Connection Advisor, Digital Ambassador, Giving Advocate
   • Frame as: “Here’s how alumni like you are already contributing” — not “pick your role”
   • Each role shows the impact it creates, not just the description
   • Pull from ChampionRoleService + ALUMNI_CHAMPIONS__ROLES_FRAMEWORK.md
4. How It Works — Simple 3-step visual
   • Create your account → Complete your profile → Find your community
   • Maps to: /signup → profile wizard → communities
   • Low-friction messaging: “It takes 2 minutes to get started”
5. Social Proof — Champion count + top cities (reuse LandingController pattern)
   • Frame as: “X alumni in Y cities are already doing this”
6. Both Served and Serving — What being in the network looks like
   • Brief mention that Champions don’t just give — they get: connections, community, daily ideas, recognition
   • This addresses the implicit question: “Is it worth my time?”

7. CTA — Primary: /signup. Secondary: /login

8. FAQ (lightweight, optional)
   • “Is this only for recent graduates?” → No
   • “Do I have to be active?” → Show up however works for you
   • “What does it cost?” → Free, always
   • “What if I’m not sure which role fits me?” → You’ll discover that during onboarding

Technical Notes

• Route: GET /champions → Cp::ChampionsLandingController#show (or adapt existing controller)
• Layout: public layout (same as existing anonymous landing page)
• No authentication required — skip authenticate_cp_champion!
• Domain: alumnichampions.com DNS-redirects to belmontalum.com/champions
• DNS/Heroku: May need alumnichampions.com added to Heroku custom domains if direct routing is wanted later (currently it’s a redirect, not a constraint match)
• Mobile-first, follows DESIGN-GUIDELINES.md
• Open Graph meta tags for social sharing

Deliverables

• New controller (public, no auth) — Cp::ChampionsLandingController < ApplicationController
• New view template (adapted from /champion-info content)
• Route at /champions (public scope, near policy routes)
• Social proof data (champion count, city count)
• Mobile-responsive design (Tailwind, mobile-first)
• Open Graph meta tags (set_meta_tags helper)
• Tests (10 tests, 26 assertions, 0 failures)

What Was Implemented

Controller: app/controllers/cp/champions_landing_controller.rb

• Extends ApplicationController (NOT Cp::BaseController) — matches PoliciesController pattern for public pages
• layout "champions" — uses champion portal layout with footer
• Redirects signed-in champions to /champion-info (authenticated version)
• Loads social proof: @champion_count, @city_count from Cp::Champion.verified filtered by primary_role present (true Champions with a role selected, not just verified portal members)
• Loads @roles from ChampionRoleService.all_roles

View: app/views/cp/champions_landing/show.html.erb

• Hero section with Belmont logo, “Alumni Champions” headline, signup/signin CTAs
• “What is an Alumni Champion?” — adapted from /champion-info
• “Three Ways Alumni Engage” — Member, Champion, Community Leader tiers
• “Four Ways to Serve” — Role cards (informational only, NO links)
• “What Changes When You Opt In?” — Benefits list
• “Bruins Already Showing Up” — Social proof stats
• “How It Works” — 3-step visual (Create account → Explore role → Start showing up)
• Bottom CTA — Signup/signin on branded background

• OG meta: “Alumni Champions

  Belmont University”

Route: GET /champions → cp/champions_landing#show (as: :cp_champions_landing)

• Placed in public scope inside champion portal domain constraint
• Between policy routes and authenticated routes

Tests: test/controllers/cp/champions_landing_controller_test.rb

• Anonymous access: landing page renders, all sections present, signup/signin links, OG meta
• Authenticated redirect: signed-in champion → /champion-info

Interview Decisions Recorded

1. Controller pattern: ApplicationController (PoliciesController pattern), layout "champions"
2. Route: /champions on belmontalum.com domain, directly accessible
3. Signed-in redirect: → /champion-info (authenticated version of same content)
4. Role cards: Informational only, NO links (anonymous user can’t access role pages)
5. Social proof: True Champions (verified + primary_role present) count + city count

6. OG meta: Title “Alumni Champions

   Belmont University”, Description “Discover how Belmont alumni are making an impact…”

7. Footer: Champions layout footer automatically included (legal links, social media)

---

Phase 17.2: Generic Landing Page Refresh

Goal: Update the existing landing page at / (Cp::LandingController#show) to clearly articulate the two-tier value proposition: joining the Alumni Network, and then becoming an Alumni Champion.

Current State

The existing landing page (Phase 5.1a) has:

• Hero: “Your people are waiting”
• Three pillars: Belong, Gather, Inspire
• Social proof: Champion count + top cities
• CTAs: “You’re Invited — Come On In” (signup) + “I Already Have an Account” (login)

It’s warm and inviting, but it doesn’t explain what the app actually is, what you’ll find inside, or why it’s worth creating an account. It also doesn’t distinguish between the two tiers of engagement.

What Needs to Change

The refreshed landing page should clearly communicate:

1. What this is — An alumni network for Belmont Bruins
   • What you’ll find inside: directory, communities, events, connections, messaging
   • Why it’s worth signing up (what’s behind the door)
2. Tier 1: Join the Network — For every Belmont alum
   • Reconnect with classmates, find Bruins in your city, stay in the loop
   • Low bar, high value: “Your people are already here”
3. Tier 2: Become a Champion — For alumni who want to do more
   • Brief tease of what Champions do (link to /champions for full story)
   • “Already asking how you can serve? Learn about Alumni Champions.”
   • This is the bridge to the /champions page
4. Both served and serving — What life in the network looks like
   • You get connected. You get community. You get ideas.
   • And when you’re ready, you help others find the same.

Technical Notes

• Same controller: Cp::LandingController#show
• Same layout: public
• View update: app/views/cp/landing/show.html.erb
• May add a link to /champions from the landing page
• Keep social proof section (champion count, top cities)

Deliverables

• Updated landing page copy (two-tier messaging)
• Updated view template
• Link to /champions for tier-2 teaser
• Mobile-responsive (Tailwind responsive classes throughout)
• Tests updated (10 tests, 22 assertions)

What Was Implemented

View: app/views/cp/landing/show.html.erb

• Hero: Kept bell tower visual treatment + “Your people are waiting” headline. Updated subheadline to position as alumni network.
• Replaced “What is a Champion?” + abstract pillars (Belong/Gather/Inspire) with “What You’ll Find Inside” — 4 concrete feature cards: Alumni Directory, Communities, Events, Conversations
• Added “For Alumni Who Want to Do More” Champions teaser section with arrow link to /champions
• Kept social proof (full alumni count + top cities) and final CTA unchanged
• Removed inline footer (layout footer handles it)

Tests: test/controllers/cp/landing_controller_test.rb

• Updated assertions for new headings and 4 feature cards
• Added test for Champions teaser link to /champions
• 10 tests, 22 assertions, 0 failures

Controller: No changes needed — same stats queries.

---

Phase 17.3: Legacy Signup Flow Retirement

Goal: Remove the old /signups/* public champion signup flow and clean up associated code, while preserving the data conversion pipeline.

What Gets Removed

Routes:

• resources :signups, controller: 'champion_signups', only: [:new, :create, :show] (belmontalum.com scope, line ~329 of routes.rb)

Controllers:

• app/controllers/champions/champion_signups_controller.rb (public-facing signup flow only)

Views:

• app/views/champions/champion_signups/ (entire directory)
  • new.html.erb, show.html.erb
  • _header.html.erb, _progress_bar.html.erb
  • steps/_welcome.html.erb, _info.html.erb, _question.html.erb, _results.html.erb, _role.html.erb, _details.html.erb, _interests.html.erb
  • _score_bar.html.erb, _score_chart.html.erb
  • SVG partials: _seal.svg.erb, _icon.svg.erb, _alumni_champions.svg.erb, _logo_primary.svg.erb

Mailer:

• ChampionSignupMailer — No longer needed (no new ChampionSignup records will be created)
• app/mailers/champion_signup_mailer.rb
• app/views/champion_signup_mailer/ (email templates)

Helper:

• app/helpers/champion_signups_helper.rb (public signup helper — evaluate if staff UI still needs it)

Initializer:

• config/initializers/champion_signup.rb (admin email config — evaluate if staff flow still needs it)

What Gets PRESERVED

Critical — Data Conversion Pipeline:

• Cp::ConfirmationsController#find_legacy_signup_for(champion) — Searches ChampionSignup.active by email
• Cp::ConfirmationsController#apply_legacy_signup_data(champion, signup) — Pre-fills Cp::Champion from signup.to_champion_attributes
• Cp::ConfirmationsController#legacy_prefilled_fields(signup) — Lists pre-filled fields
• ChampionSignup#to_champion_attributes method on the model
• This pipeline is used when marketing drives old signups to create new accounts — their legacy data auto-populates their profile.

Staff Management (Phase 17.3 decision):

• app/controllers/champion_signups_controller.rb (staff interface on alumnilookup.com)
• app/views/champion_signups/ (staff views)

Model & Services (still needed):

• ChampionSignup model — needed for conversion pipeline and staff management
• ChampionSignupMerger — needed for staff duplicate management
• Csv::ChampionSignupExporter — needed for staff CSV export
• ChampionQuizService — used by profile wizard quiz (NOT just old signup)
• ChampionRoleService — used widely across the portal

Redirect Strategy

• /signups/new → 301 redirect to /champions (new public landing page)
• /signups/:id → 301 redirect to /champions
• Only external source is alumnichampions.com (which will redirect to /champions at DNS level)

Deliverables

• Add 301 redirects for old signup URLs → /champions
• Remove legacy public signup routes
• Remove Champions::ChampionSignupsController (public flow)
• Remove app/views/champions/champion_signups/ directory (kept SVG partials used by staff views)
• Remove ChampionSignupMailer and email templates
• Audit and remove unused helpers/initializers (removed initializer, kept helper used by alumni_helper)
• Verify data conversion pipeline still works (test with existing ChampionSignup records)
• Update any internal links to old signup flow
• Tests for redirects (2 tests)
• Run full test suite — verify nothing breaks (4219 runs, 0 failures)

What Was Implemented

Removed:

• app/controllers/champions/champion_signups_controller.rb — 154-line multi-step wizard controller
• app/views/champions/champion_signups/ — new.html.erb, show.html.erb, _header.html.erb, _progress_bar.html.erb, all step partials, _score_bar.html.erb, _score_chart.html.erb, _alumni_champions.svg.erb, _logo_primary.svg.erb
• app/mailers/champion_signup_mailer.rb — welcome and admin notification emails
• app/views/champion_signup_mailer/ — 4 email templates (HTML + text)
• config/initializers/champion_signup.rb — admin email config (only used by deleted mailer)
• lib/tasks/champion_signup_emails.rake — test email rake task
• test/controllers/champion_signups_controller_test.rb — public flow tests
• test/mailers/champion_signup_mailer_test.rb + preview

Preserved:

• _seal.svg.erb and _icon.svg.erb at original path — still used by staff views and alumni_helper.rb
• ChampionSignupsHelper — still used by alumni_helper.rb and rake task
• ChampionSignup model, ChampionSignupMerger, Csv::ChampionSignupExporter
• Staff controller and views at /champion_signups
• Conversion pipeline in Cp::ConfirmationsController

Routes:

• Replaced resources :signups with 301 redirects: /signups/new → /champions, /signups/:id → /champions

Tests: 2 new redirect tests, full suite 4219 runs, 0 failures

---

Phase 17.4: Staff Management & Data Catalog

Goal: Keep the internal ChampionSignup staff management interface, document the data pipeline, and catalog how legacy data is used.

Context

Staff management at /champion_signups on alumnilookup.com provides:

• List/filter/sort/export all legacy signups
• View individual signup details
• BUID assignment (link signup to alumni record)
• Duplicate detection and merging
• CSV export

This data will be actively used when marketing the new Alumni Network — staff will reference legacy signups to identify prospects and the conversion pipeline will use it to pre-fill new accounts.

Decision: Keep Read-Only + Conversion Pipeline

No new ChampionSignup records will be created after removing the legacy public flow. Keep the staff interface for:

• Historical reference and export
• BUID assignment (linking signups to alumni for conversion pipeline)
• Duplicate merging (data cleanup of existing records)

Data Usage Catalog

Document how ChampionSignup data flows through the system:

Flow	Source	Destination	Mechanism
Profile Pre-fill	ChampionSignup (by email match)	Cp::Champion profile	ConfirmationsController#apply_legacy_signup_data calls signup.to_champion_attributes during email confirmation
Staff Reference	ChampionSignup records	Staff dashboard at /champion_signups	ChampionSignupsController (index, show, export)
CRM Export	ChampionSignup data	Engagement stats CSV	EngagementStatsController includes champion_signup_status, champion_signup_role, champion_signup_date
Engagement Metrics	ChampionSignup.completed.count	Overview dashboard	EngagementStats::OverviewService counts unique completed BUIDs
Alumni Association	ChampionSignup.buid → Alumni.buid	Alumni record view	Alumni has_many :champion_signups (FK via buid)

Fields Mapped by to_champion_attributes

(Needs verification — read ChampionSignup#to_champion_attributes to confirm exact mapping)

Expected: first_name, last_name, maiden_name, graduation_year, email, phone, street, city, state, zip_code, selected_role/result_role, lifestage_interest, belonging_categories, vocation

Deliverables

• Document data usage catalog (this section, verified)
• Verify to_champion_attributes field mapping
• Add note to staff management UI that no new records will be created
• Update docs/features/CHAMPION_SIGNUP_SYSTEM.md to reflect retired status
• Update CHANGELOG

What Was Implemented

• Verified to_champion_attributes maps 9 fields: first_name, last_name, college_last_name, zip_code, city, state, street_address, phone, primary_role (all compact_blank)
• Added legacy data notice banner to staff signups index page
• Updated CHAMPION_SIGNUP_SYSTEM.md: renamed to “Legacy”, added retirement notice with field mapping table, marked historical sections
• Data usage catalog in this spec verified against actual code

---

Dependencies

• Source documents: docs/planning/champion-portal/source/ALUMNI_CHAMPIONS__*.md
• Design: docs/planning/champion-portal/development/DESIGN-GUIDELINES.md
• Language: docs/planning/champion-portal/development/LANGUAGE_STYLE_GUIDE.md
• Existing content: app/views/cp/champion_info/show.html.erb (Phase 13.7)
• ChampionRoleService for role metadata
• Existing landing page pattern: app/controllers/cp/landing_controller.rb
• Data conversion: Cp::ConfirmationsController legacy signup pipeline

Risk Assessment

• Low risk: New public landing page is additive; doesn’t change existing flows
• Low risk: Legacy signup removal — only inbound URL is alumnichampions.com (DNS redirect handles it)
• Low risk: Staff management unchanged — just documenting what exists
• Medium risk: Must verify conversion pipeline still works after removing the public creation flow

Sequencing Notes

Phases 17.1 and 17.2 can be built in either order or in parallel — they’re independent pages. However, the generic landing page (17.2) will link to /champions (17.1), so 17.1 should be deployed first or simultaneously.

Phase 17.3 (legacy retirement) should come after 17.1 is live, so the /signups/new redirect has a destination.

Phase 17.4 (data catalog) can happen anytime.

DNS / Heroku Notes

• alumnichampions.com should DNS-redirect (301) to belmontalum.com/champions
• No need to add alumnichampions.com as a Heroku custom domain if using DNS redirect
• Existing route constraint includes alumnichampions (line 10, routes.rb) — can be removed once DNS redirect is confirmed working

---

What Was Implemented

(To be updated as sub-phases are completed)