Rendered from storefront/allowed.md

Storefront — Allowed

This gauge covers Chapter 19: customer-facing ecommerce layout patterns after Admin UI, Tables, Forms, Grid, and Flexbox.

Learning goal

Compose storefront surfaces — store chrome, product grids, filter catalogs, product detail buy boxes, cart and checkout summaries, account hubs, and invoices — while keeping native controls and accessible names.

Inherited tools

Everything allowed through ../admin-ui/allowed.md remains available, including forms from Chapter 12 and tables and lists from Chapter 13. Layout tools from Flexbox, Grid, Responsive, Positioning, Variables, and Pseudo-classes may be used as needed for store chrome.

New presentation patterns

Learning rules

  1. Keep one visible main for the primary storefront content.
  2. Product cards may use card elevation because they are the unit of browsing interaction. Do not wrap the entire page in nested decorative cards.
  3. Filter groups use fieldset and legend. Keep visible labels on every control; placeholders are examples, not names.
  4. Use real table markup for carts, wishlists, specs, and invoices. Do not use tables for page layout.
  5. Sticky order summaries must remain keyboard-reachable in source order.
  6. Static tab chrome may show one panel. Changing tabs with script belongs to the JavaScript workbook.
  7. Delivery and payment choices are radio groups or native selects with visible labels and helper text.
  8. Prefer CSS variables for surface, border, muted text, price, and badge fills.
  9. Status and stock badges use text as well as colour.

Not allowed

Pages

Rules to lean on

Rules 2, 10, 34–38, 54–59, 72–80, 99–110, 111–122, 135–144, 175–195, and storefront rules added for Chapter 19.