improve: website-packages - Redesign website package presentation #156

Improvement Summary

Rebuild /website-packages/ from verified LIVE copy/approved package details. DEV page 43507; supplied slug website-packages-page.

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 page stays published (no pages are unpublished), but links to it are removed before launch so users cannot reach the broken page, and restored after the rebuild once a menu home is decided.

Links to remove before launch (found on DEV 2026-10-23). Header/footer navigation (the Pricing mega menu), /contact/, /free-consultation/, and the blog post /tour-operators-efficient-pricing-increased-revenue/.

Linked Stories/Tasks/PRs/Epic

Parent: LSA-166, hierarchy only; no epic PR association. Preserve /contact///free-consultation/ inbound links. Pricing-menu removal creates navigation dependency; historical consolidation is not retirement permission. 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

Reported logos/Get Started buttons without visible package text and large empty bordered boxes. LIVE about 635 words; Pricing mega-menu home being removed.

Describe the improvement you'd like

Rebuild readable package cards using verified existing copy. Confirm package details/prices with owner before publishing. Raise new menu home as dependency; do not select or edit navigation without a separately approved decision.

Designs / Mockups

Reuse package/card treatments; approved layout/content remains an implementation dependency.

Accessibility Considerations

Visible descriptions/comparisons/CTAs, meaningful links, focus and mobile card order.

Acceptance Criteria

• /website-packages/ unchanged; inbound links removed before launch and restored after the rebuild once a menu home is decided.
• Package descriptions/details visible; broken/empty blocks resolved.
• Copy sourced from verified LIVE content, not invented.
• Owner confirms package details/prices before publication.
• Navigation home remains an explicit dependency until approved, with no guessed menu placement.
• 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

Compare approved package baseline; test CTAs/inbound links, empty-block resolution and responsive/keyboard/contrast. Navigation completion follows owner decision.

Describe alternatives you've considered

Reuse package cards; destination/navigation choices remain a separate decision, not inferred from design.

Additional Context

LIVE https://lightspeedwp.agency/website-packages/; DEV https://ls-agency.lightspeedwp.dev/website-packages/. Owner decisions: details/prices and navigation home.

Branch instructions

Apply shared packet. Provisional WordPress page 43507 edit; reuse card-package section style/homepage-where-to-fit as inputs only. No shared pricing/navigation source changes. Exact branch/base withheld; develop integration verified. Revised plan required for demonstrated reusable gap. 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