Open source components versus building a custom replacement
Key Takeaway
If a standard component nearly meets the need, customize its open source version. If the feature resembles no standard component, build a custom Lightning web component.
When a standard store component is close to what you need but not quite right, an open source component gives you its editable source code. You can then change the component without rebuilding it from scratch. A custom component is built from the ground up, so check the standard and open source options first.
Start with standard components
Components make up B2B store pages. You make a store template your own by dragging components onto store pages in Experience Builder and setting their component properties.
Starting with Summer '23, all new B2B stores are built on the Lightning Web Runtime (LWR) platform. Some older B2B stores still run on the Aura platform. Salesforce recommends migrating those stores to an LWR template.
An LWR store already has dozens of standard Lightning web components, so review them before you build anything custom. Salesforce recommends using up-to-date standard components first. Before you create a custom component, check whether a standard component can meet the need, using CSS overrides if needed.
Standard components in the Experience Builder palette are optimized for both client-side and server-side rendering. They also usually include the latest performance improvements.
Use expressions instead of static text to make a standard component more dynamic without writing a new one.
Using standard components also means keeping them current. On existing sites, check Experience Builder pages for any component marked as deprecated.