Feature #7
open[A-01] Build the customer-facing surface using the data pipeline that already exists (no backend rework needed): an occasion index/landing page, named deep links (e.g. a Wedding page, a Festive page), and a homepage or nav entry point. Also fix the leg...
0%
Description
Module: Add To Occasion
Current State:
The occasion-tagging pipeline (admin/seller tags a product → syncs to Algolia) works correctly end to end. The gap is entirely customer-facing: an occasion tag is only visible as one buried filter checkbox inside the product directory — confirmed via a full-repo search, there is zero dedicated landing page and zero homepage entry point today.
Task:
Build the customer-facing surface using the data pipeline that already exists (no backend rework needed): an occasion index/landing page, named deep links (e.g. a Wedding page, a Festive page), and a homepage or nav entry point. Also fix the legacy "ocassions" vs "occasions" duplicate Algolia attribute before it causes filter drift.
Why It Matters:
Nykaa Fashion (a direct ethnic-wear competitor) has exactly this as real navigation (Wedding, Festive, Haldi, Mehendi, Cocktail, Eid pages). Flagged independently by Codex as the clearest low-effort, high-visibility revenue experiment available — the hard part is already built.
Target Week: Week 1-2
Excel Owner: Aman
Excel Priority: P0 - Critical
Excel Status: In Progress
Sprint Plan ID: A-01
No data to display