Repository navigation
Description
Improvement Summary
Redesign continuing programme /referrals/, DEV page 43457, supplied slug referrals-page, with GF5.
Final plan (updated 2026-10-23)
Post-launch. Moved out of the 27 October 2026 launch (milestone: Post-Launch Pages Complete). Not a launch blocker; the referral programme continues. The page stays published (no pages are unpublished), but links to it are removed before launch and restored after the rebuild.
Inbound links (checked on DEV 2026-10-23). The only link found is in the blog post /the-hard-thing-about-hard-things/; remove it before launch. No menu or page links to it. GF5 stays live at launch and its thank-you page (#144) is in launch scope.
Linked Stories/Tasks/PRs/Epic
Parent: LSA-166, hierarchy only; no epic PR association. Referral confirmation depends on approved programme terms/copy; coordinate #123. No extra native relationships.
Milestones & Timeline
Post-launch, not a launch blocker. Milestone: Post-Launch Pages Complete (no date).
Is your improvement related to a problem? Please describe
Overlapping buttons/logo strip, unstyled inputs, stock avatars and stray white bars. LIVE about 470 words, “Get 10% per referral”. Brief reports no DEV inbound links, while repo contact pattern contains /referrals/; deployed linking unverified.
Describe the improvement you'd like
Rebuild page/GF5 presentation. Confirm offer terms before publishing. Ask where it should be linked; inspect actual deployed links rather than infer menu placement from source patterns or brief. No invented endorsements/media replacements.
Designs / Mockups
Approved programme layout/media/offer wording remains an implementation dependency.
Accessibility Considerations
Readable offer/form copy, labels/focus, no control overlap, appropriate image alternatives and responsive flow.
Acceptance Criteria
-
/referrals/unchanged. - GF5 retains current fields and confirmation journey.
- Overlaps, white bars and unstyled inputs resolved.
- Owner confirms offer; reported 10% copy is not automatically approved.
- Actual inbound links checked; placement awaits owner decision.
- Confirmation copy/journey agrees with approved programme.
- All acceptance criteria met
- Documentation/changelog updated
- Tests added/updated
- PR uses correct branch prefix (feat/)
- PR description updated with relevant details
- Changelog entry prepared for PR (if applicable)
- Labels/types match org standards
Testing Requirements
Controlled GF5 validation/submission/redirect, approved-offer comparison, inbound links and mobile/keyboard/contrast; coordinate broader #123 audit.
Describe alternatives you've considered
Reuse forms/heroes/cards. Link location and historical retirement suggestions require separate human decisions.
Additional Context
LIVE https://lightspeedwp.agency/referrals/; DEV https://ls-agency.lightspeedwp.dev/referrals/. Dependencies: offer terms, media and inbound placement.
Branch instructions
Apply shared packet. Provisional WordPress page 43457 edit, reuse form/hero/general blocks with instance GF5. No shared navigation/source change established; exact branch/base withheld, develop integration verified. Stop before offer logic/menu/new source paths. Source-template wording retained unchanged; branch/PR requirements apply only to repository changes; database-only edits need no branch. Improvement feat/ wording is not branch selection. Verify owning-repository rules and resolve documented PR-template conflict before implementation. Do not mark contradictory requirements satisfied, auto-close on merge, automatically delete branches or close the parent epic.
Definition of Ready (DoR)
- Problem/opportunity defined
- Acceptance criteria written
- Designs attached (if relevant)
- Dependencies mapped
- Estimate added (if relevant)
Definition of Done (DoD)
- All AC met and demonstrated
- Documentation and changelog updated
- Tests added/updated
- Correct labels/types applied
- PR uses correct branch prefix (feat/)
- Branch deleted after merge
- Linked issue(s) updated with latest status and closed after merge,
- The related epic should not be closed, instead updated with a comment to reflect the closed issue
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
linear-code commentedon Oct 23, 2026
LSA-212