This document tracks the status of Wardrobe V2, a ground-up rewrite of the outfit editor using Rails + Turbo, replacing the React + GraphQL system embedded from Impress 2020.
## Goal
Replace the complex React outfit editor (`app/javascript/wardrobe-2020/`) with a simpler Rails/Turbo implementation that:
- Eliminates dependency on Impress 2020's GraphQL API
- Uses progressive enhancement (works without JavaScript)
- Leverages Web Components for interactive features
- Reduces frontend complexity and maintenance burden
- Eventually enables full deprecation of the Impress 2020 service
**Wardrobe V2 is in active development** on the `feature/wardrobe-v2` branch. It's accessible at `/wardrobe/v2` but is not yet linked from the main UI.
- **Species/color/pose/style selection**: Full picker UI with visual pose thumbnails, availability indicators, canonical fallback, and alt style picker with tabbed UI
- **Item search**: Text search with auto-filtering by pet compatibility, pagination, add/remove items
- **Item display**: Grouped by zone with multi-zone simplification, incompatible items section, NC/NP badges
- **Outfit rendering**: Uses the shared `<outfit-viewer>` web component
- **Progressive enhancement**: Everything works without JS; web components add auto-submit and smoother interactions
- **Smooth navigation**: Idiomorph DOM morphing reuses `<outfit-viewer>` layers across full-page navigations
Code lives in `app/controllers/wardrobe_controller.rb`, `app/views/wardrobe/`, `app/helpers/wardrobe_helper.rb`, and `app/assets/{stylesheets,javascripts}/wardrobe/`.
**Simplicity over polish**: Unlike many webapps, we value the simplicity of the codebase very highly, even at the expense of an ideal user experience. Start with simple solutions, even if the UX is clunky; then we'll iterate up as needed.
**URL as single source of truth**: All outfit state lives in URL params (`species`, `color`, `pose`, `style`, `objects[]`, `q[...]`). Every interaction is a GET request that generates a new URL. No client-side state management. Browser back/forward work naturally.
**Server-side rendering + Web Components**: All HTML is generated server-side. Lightweight web components (`<auto-submit-form>`, `<pose-picker-popover>`, `<tab-panel>`, `<outfit-viewer>`) add interactivity without framework overhead.
Add a link on each item card that opens the item's detail page.
Files to modify:
- app/views/wardrobe/items/_item_card_content.html.haml — Add info link
- app/assets/stylesheets/wardrobe/show.css — Style it
Approach:
- Add link_to to /items/:id with an info icon/emoji, target: "_blank"
- Style: subtle, visible on hover/focus-within, always visible on touch (@media (hover: none))
## Commit 2: [WV2] Add zone badges to search results
Show which zones each item occupies in search result cards.
Files to modify:
- app/views/wardrobe/items/_item_card_content.html.haml — Conditionally render zone badges
- app/views/wardrobe/items/badges/_zones.html.haml (new partial) — Render zone label badges
- app/assets/stylesheets/wardrobe/show.css — Style zone badges (muted, small)
- app/controllers/wardrobe_controller.rb — Load item appearances for search results so zone data is available
Approach:
- Only show zone badges in search results (not outfit items, where the zone group header provides context)
- Pass a local variable (e.g. show_zones: true) from the search results template to item_card_content
- Use Item.appearances_for(items, pet_type) to batch-load appearances for search result items
- Render each item's occupied zone labels as small badges
- Zone data comes from the item's SwfAsset layers for the current pet's body_id
Design decision: Zone badges are omitted from outfit items. When an item occupies multiple zones, the outfit view shows it under multiple zone group headers, which is sufficient context. The rare case
where it could be misleading (e.g., item occupies Background+Foreground but only Background has conflicts) is niche enough to accept for now.
## Commit 3: [WV2] Add ownership and wishlist badges
Show "Own" / "Want" badges when a logged-in user has items in their closet lists.
Files to modify:
- app/controllers/wardrobe_controller.rb — Call assign_closeted_to_items! on all visible items
- app/views/wardrobe/items/badges/_closet.html.haml (new partial) — Own/Want badges
- app/views/wardrobe/items/_item_card_content.html.haml — Include closet badge partial
- app/assets/stylesheets/wardrobe/show.css or app/assets/stylesheets/application/item-badges.css — Badge colors
Approach:
- In controller: current_user.assign_closeted_to_items!(all_items) if user_signed_in? where all_items is the combined set of worn + closeted + search result items
- Badge partial: green "Own" badge if item.owned?, blue "Want" badge if item.wanted?
- Badge styling patterns from app/assets/stylesheets/application/item-badges.css
## Commit 4: [WV2] Switch search to text-based filter syntax
Replace the structured search filter approach with from_text(), enabling the full search syntax (is:nc, occupies:background, user:owns, etc.) in a single text field.
- app/views/wardrobe/items/_pagination.html.haml (new partial) — Custom pagination UI
- app/assets/stylesheets/wardrobe/show.css — Style pagination bar
Approach:
- Layout: [← Prev] [Page <select> of N] [Next →]
- The <select> is inside an <auto-submit-form> for JS-enhanced page switching
- Prev/Next are regular links (work without JS)
- Without JS: select has a "Go" submit button (hidden when JS active via auto-submit-form:defined)
- Use will_paginate's collection methods (.current_page, .total_pages, .previous_page, .next_page) — keep .paginate() in controller, just replace the view rendering
- Single pagination bar (top of results, remove bottom duplicate)
## Verification
Test at localhost:3000/wardrobe/v2:
1. Info links: Hover over item cards → info link appears → click opens /items/:id in new tab
2. Zone badges: Search for items → results show zone badges (e.g., "Background", "Hat"). Outfit items do NOT show zone badges.
3. Ownership badges: Log in (test/test123) → search → items in closet show "Own"/"Want" badges. Log out → no badges.
