Doctor B
Compared Parent Category (/category/hub) and Child Category (/category/hub/online-store) against the Figma flow (Parent Category "Food & Drink" → Child Category "Restaurants," reached via node 1:4425). This pair surfaced the clearest confirmed dev bugs so far — not admin/content issues.
Confirmed bug: Child Category page doesn't render distinct content
Navigating to /category/hub/online-store correctly updates the URL and browser tab title to "Online store," but the on-page hero heading still reads "Hub" — it's pulling the parent category's name instead of the child's. Below that, every section (the subcategory card, "Trending" products, the product grid, the "Public Store / Sports / Drinks / Daily Essentials" filter chips) is byte-for-byte identical to the parent /category/hub page. Figma's Child Category template ("Restaurants," under Food & Drink) is clearly meant to show child-specific content — a row of dish photos (Stuffed Potato, Pancakes, Chicken Grilled), a dedicated sponsored ad, and its own trending set — none of which live implements. This reads like the child category route exists but isn't wired to pull or filter its own data; it's just re-rendering the parent template.
Confirmed structural gaps on Parent Category
Figma's Parent Category page places a related-category carousel (with pagination dots) directly under the hero — live's Hub page shows only a single static "Online store" card with no carousel chrome at all, even though it's a one-item case. Figma's Trending cards use a filled red heart for favorites; live's are an outline/hollow heart — a real style inconsistency, not content. The subcategory filter chips (Delivery/Dine-in/Home Chef equivalent) sit right under the H1 in Figma; on live, the equivalent chips ("Public Store," "Sports," etc.) appear much further down, after a full product grid — a layout ordering difference at the component level, not content.
Worth a dev look, not just content cleanup
One listing's description rendered literal raw markup: <p>rdter</p> showed up as visible text on the page rather than being parsed — that's a sanitization/rendering gap in whatever component displays that rich-text field, separate from the field just containing bad placeholder data. I'd flag that one specifically for engineering, since no amount of admin cleanup fixes a component that's not parsing HTML correctly.
Footer note: Figma's category-page footer is a shorter variant (Terms | Sitemap | Privacy | Your Privacy Choices, no accordion legal row), while live reuses the exact same full footer as the homepage. Given your steer on footer ordering being admin territory, I'm flagging this only as a template-choice difference worth confirming is intentional, not listing it as a bug.
Want me to check a second parent/child pair (e.g., Travel & Tourism or Property Buying & Rentals) to see if the "child page mirrors parent" bug is consistent across all categories, or isolated to Hub/Online store?
Fashion & ApparelFeatured Products Extension Part
0.0★
Daily Essentials 
What
Where
.jfif&w=3840&q=75)
.jfif&w=640&q=75)
.jfif&w=640&q=75)
.jfif&w=640&q=75)
.jpeg&w=640&q=75)
.jpeg&w=640&q=75)
.jpeg&w=640&q=75)
.jpeg&w=640&q=75)
.jfif&w=640&q=75)
_-_Zainab_Mazhar.jpeg&w=640&q=75)
_-_Zainab_Mazhar.jpeg&w=640&q=75)
.jfif&w=640&q=75)
.jpg&w=640&q=75)
.jpg&w=640&q=75)
