WordPress/WooCommerce (Elementor) Dev

Заказчик: AI | Опубликовано: 01.10.2025

Build Customer Reviews Slider on Single Product (Universal Reviews) Stack: WordPress, WooCommerce, Elementor, Site Reviews (plugin) Store type: Digital game shop with two product types: Accounts and Coins Goal Implement a reviews section on the single product page that: 1. Shows universal reviews (same pool across products; not per-product). 2. Displays a summary bar (avg rating + text), then a horizontal card slider with “Customer Reviews” heading on the left and arrow controls on the right. 3. No review form on the product page (form lives on a separate Reviews page). 4. Clean, responsive, dark-theme friendly; swipe on mobile, arrows/keys on desktop. Scope of Work 1. Pull Site Reviews data as universal (not assigned_to product). 2. Build a carousel/slider UI (minimal JS; can be custom or lightweight library) that: * Truncates long review text with ellipsis. * Keeps card height consistent. * Supports touch swipe and arrow buttons. * Hides entirely if no reviews exist. 3. Add and style a compact summary bar above the slider. 4. Integrate into the Elementor Single Product template for both product types (Accounts & Coins). 5. Remove/disable any default Woo reviews tab on product pages to avoid duplication. 6. Staging first, then deploy to live. Acceptance Criteria 1. Appears on all single product pages (Accounts + Coins). 2. Uses universal reviews only; no form rendered on product pages. 3. Smooth horizontal scroll (arrows + touch), stable layout, responsive. 4. Summary bar + “Customer Reviews” header render correctly; section auto-hides if there are no reviews. 5. Code added via child theme/snippet manager; no core edits. Deliverables 1. Updated Single Product template section (Elementor) with summary + slider. 2. Lightweight CSS/JS with comments. 3. Short admin note on: where the code/template lives, how to change heading text, how to enable/disable the block. Please Include in Your Proposal 1. 2–3 examples of Woo/Elementor review sliders you built. 2. Your approach (custom JS/CSS vs. lightweight library) and performance considerations. 3. Estimated timeline and fixed price (or hourly with cap). 4. Access needs and assumptions.