Skip to main content

Affiliate Share Gateway Hero Reconciliation

Status: published preview plan

Live preview:

Source-of-truth planning file:

Execution backlog:

Product Rule​

Ordinary event-link clicks should render like event profiles first.

Share-to-earn mechanics should appear only after explicit promoter intent:

  • user clicks Promote & Earn
  • user opens a promote-mode URL such as ?mode=promote, ?promote=1, or #remix

Default buyer-first pages should not show reward, payout, remix, or attribution mechanics as the primary state.

Published Preview Behavior​

The event-profile integration and affiliate share gateway preview now support two modes:

Event Mode​

Default mode for ordinary event links.

Expected behavior:

  • event hero renders full screen on mobile
  • page context says Event Details
  • event strip shows Starts instead of Pending reward
  • Get Ticket is the active primary event action
  • remix gateway and attribution panels are hidden

Promote Mode​

Entered only after Promote & Earn or a promote-mode URL.

Expected behavior:

  • remix gateway appears
  • attribution context appears
  • page context changes to Checkout Context
  • event strip changes to Pending reward
  • Promote & Earn becomes the active action

Hero Reconciliation Direction​

The affiliate preview provides the preferred mobile hero direction for Mi Gente event-style pages:

  • edge-to-edge background image
  • minimal top chrome
  • overlayed Mi Gente logo
  • top-right login/profile affordance
  • bottom-weighted identity block
  • event date/time card
  • scroll cue
  • bottom mobile CTA bar

This should become a shared Mi Gente hero shell instead of remaining affiliate-specific.

Shared Hero Pattern​

Create a shared MiGenteImmersiveHero pattern, or equivalent, with slots for:

  • background media
  • brand/logo
  • login/profile status
  • primary identity block
  • optional date/time card
  • optional profile avatar and verification
  • optional mobile CTA bar
  • optional scroll cue

Supported variants:

  • event
  • profile
  • affiliate-promote-entry

Event Page Reconciliation​

Use the shared hero for event detail pages first.

Acceptance:

  • mobile event pages use the full-screen immersive hero
  • event pages keep buyer-first behavior by default
  • Promote & Earn remains an explicit action
  • desktop event detail behavior remains conservative unless separately approved

Premium Profile Reconciliation​

Use the shared hero for premium profile pages after the event page pass.

Acceptance:

  • mobile profile pages use immersive background treatment
  • avatar, verification, profile summary, and follow/contact actions remain profile-specific
  • heavy contact panels, facts, social grids, bookings, and related events move below the first viewport
  • profile pages do not become affiliate dashboards unless a promoter-specific link was opened

Backlog Tickets​

Goal: make ordinary affiliate/event link clicks render like an event profile first, with share-to-earn controls visible only after explicit promoter intent.

Acceptance:

  • default clicked-link state shows event profile details, ticket CTA, event schedule/context, and normal event identity
  • Promote & Earn opens the remix gateway and attribution context
  • direct promote links can open the promoter flow directly
  • reward, attribution, remix, and payout language is hidden from ordinary buyer-first event views
  • event-first and promote modes are covered by rendered desktop/mobile QA before publication

AFF-SHARE-012: Mi Gente immersive hero reconciliation​

Goal: reconcile the stronger affiliate preview hero with existing Mi Gente event and premium profile pages through a shared, mobile-first hero system.

Acceptance:

  • shared hero pattern supports event, profile, and affiliate-promote-entry variants
  • event pages use the shared hero with date/time card, event metadata, title, ticket CTA, and optional promote CTA
  • premium profile pages use the shared hero with avatar, verification, profile summary, contact/follow CTA, and profile-specific actions below the fold
  • desktop event/profile layouts remain conservative unless separately approved
  • visual QA covers mobile above fold, mobile below fold, desktop event, and desktop profile pages