ForgeWP

Storefront Component Reference

Match real component names and props to their rendering responsibilities and integration limits.

Storefront component reference

Most components provide styled markup. For a custom interface, use the corresponding hooks. The names below are exported; ProductCard and CartDrawer are not package components.

Table · 2 columns
Component
Props and responsibility
WpCartProvider
Required children; Store API/provider cart path, with unresolved value/type mismatch.
WpProductGallery
Required numeric productId; gallery UI.
WpProductPrice
Required numeric productId; distinct from the no-argument price hook.
WpProductVariationSelector
Required numeric productId; variation UI.
WpProductStockStatus
Required numeric productId; availability display.
WpRelatedProducts
Numeric productId; optional limit, default 4.
WpProductReviews
Required numeric productId; review UI.
WpCartLineItems
No props; uses older cart-row fields. Verify against the chosen state path.
WpCartCouponForm
No props; coupon controls.
WpCartShippingCalculator
No props; assumes shippingAddress exists, although standalone state permits it to be absent.
WpCheckoutForm
Required children and optional className; state provider, not a submission form.
WpShippingSelector
No props; requires checkout context.
WpLoginForm
No props; commerce customer-hook login.
WpRegisterForm
No props; commerce customer-hook registration.
WpOrderHistory
No props; customer order display, not a permission check.
WpProductFilters
No props; filter interface.
WpWishlistButton
Required numeric productId.
WpWishlistList
No props; wishlist view.
WpStoreNotice
No props; hardcoded mock-store notice, currently not development-gated.
WpProductLoop
Required children; category?, limit=10, orderBy=date, order=desc, status=publish.

WpProductLoopProps is the exported loop prop type. CheckoutFormContext and WpCartContext are lower-level contexts. Some ready-made cart components currently disagree with the public cart types. Listing an interface here does not establish that all component combinations pass package-wide typing or WordPress acceptance.