// the take
Official Salesforce sample app demonstrating Lightning Web Components and Experience Cloud, built around a fictitious e-bike retailer. It's a reference implementation for Salesforce developers learning LWC patterns, Apex integration, and how to wire up a community portal — not a standalone web app you can run outside the Salesforce platform.
Jest tests are present for most LWC components with realistic mock data, not just smoke tests. UTAM end-to-end tests on the Product Explorer page show how to do real browser automation against a Salesforce org, which almost no sample apps bother with. The LWC Message Service usage (ProductSelected/ProductsFiltered channels) demonstrates decoupled sibling communication correctly — the pattern that trips up most Salesforce devs new to the component model. CI pipeline with Prettier + ESLint pre-commit hooks means the code style is consistent and the toolchain is actually wired up.
Setup requires 12+ manual steps including XML file edits and org-specific domain substitution — a scratch org script exists but it still needs hand-holding. There's no abstraction layer between Apex controllers and SOQL, so ProductController.cls will get messy fast if anyone tries to extend this beyond the sample. The Aura component (pageTemplate_2_7_3) is a leftover that signals this wasn't fully migrated to LWC — Aura is legacy and Salesforce recommends against it for new work. Zero documentation on the Pub Sub API demo integration; it just points to a separate repo with no explanation of the architecture.
We read the README, the directory tree and a key source file in June 2026. Nobody pays to be listed. How we judge →