/** * Wishlist — the design-system skin for TI WooCommerce Wishlist (Premium). * * SURFACE: the wishlist page family — /wishlists/ (one list), * /manage-wishlists/ (rename / privacy / delete), /public-wishlists/, * /search-wishlist/ — plus the three modals the plugin appends to * (Create list, Notification settings, Move to list). Those pages are served * by templates/plain-page.php, so this sheet styles the plugin's markup * INSIDE the .cwpl shell; the shell itself (page title, width) is * plain-page.css's job and is left alone. * * WHY A THEME SHEET AND NOT A PLUGIN EDIT: same reasoning as * assets/css/pickup-delivery-popup.css — the wishlist is a customer-facing * surface of OUR store that happens to be rendered by a third-party plugin, * so the design lives here where a plugin update cannot revert it. Nothing in * this file depends on the plugin's own markup being changed. * * ------------------------------------------------------------------------ * THE ZONE — STEEL. Flat machined greys, and lime as the only colour on the * page. * ------------------------------------------------------------------------ * The wishlist is the come-back-later counterpart to the basket, so it is * built to READ as a sibling of assets/css/cart.css — same card, same 12px * radius, same row rhythm, same button geometry, same tabular numerals. * * What differs is that this surface is MONOCHROME. Every structural element — * the tabs, the table head, the totals band, the panels, the modals — is * drawn from the EXISTING ink ramp in cw-tokens.css (--cw-card, --cw-ground, * --cw-line/-2, --cw-ink/-2) — flat fills, no gradients anywhere. No new * colour was invented for any of it: --cw-ink-2 is the logo grey, i.e. * literally half the brand mark. (A first pass here used gradients for the * raised/recessed surfaces — user decision 2026-08-24: flat only, gradients * read as decoration this surface doesn't need.) * * WHY MONOCHROME IS THE POINT, not a limitation (user decision 2026-08-23, * replacing a first pass built on a purple complement — which read feminine * rather than factory): with nothing else on the surface competing, the one * lime "Add to Cart" is the only colour a customer sees, so the buy action * cannot be missed. That also resolves what had been the judgement call in * this file — "Add to Cart" / "Add All to Cart" stay LIME because buying is * the same act here as on the shop grid, the PDP and the basket, and steel * owns everything the wishlist itself is (the list, its structure, its * management actions: Create, Move, Rename, My Wishlists, Notifications, * Search). --wl-buy / --wl-buy-text are still the only two tokens that carry * it, so it stays a two-line change. * * MONOCHROME MEANS HOVER CANNOT BORROW A HUE. Two conventions do that work * instead, and both need to be kept if rules are added: controls DARKEN * (--wl-steel to --wl-steel-deep, matching the lime zone's own rule — a * filled control goes flat steel to flat ink, nothing fades), and content * links grow a rule underneath rather than changing colour. Do not reach for * a second hue, and do not reach for a gradient, to signal interaction. * * ------------------------------------------------------------------------ * SPECIFICITY / LOAD ORDER — read before adding a rule that "does nothing". * ------------------------------------------------------------------------ * The plugin ships THREE colour layers, and the third is the awkward one: * 1. assets/css/public.min.css handle `tinvwl` * 2. templates/soft_skin/theme.min.css handle `tinvwl-theme` * 3. a ~10KB