Rendered from admin-commerce/allowed.md

Admin Commerce — Allowed

This gauge covers Chapter 20: operator ecommerce layouts and table chrome after Storefront, Admin UI, and Tables.

Learning goal

Compose admin commerce surfaces — table variants, ops table toolbars, add-product forms, list pages, and entity detail panels — while keeping native controls and accessible names. Interactive search, sort, pagination, and bulk select wait for JavaScript Phase 9.

Inherited tools

Everything allowed through ../storefront/allowed.md and ../admin-ui/allowed.md remains available, including forms, tables, dashboard shells, dropzones, and input groups from earlier chapters.

New presentation patterns

Learning rules

  1. Table modifiers change presentation only. Keep caption, thead/tbody, and scope from Chapter 13.
  2. Status pills communicate state with text as well as colour.
  3. Row-action menus may be static open markup in this chapter. Opening them with script belongs to JavaScript.
  4. Pagination links and search inputs may be non-functional chrome. Wiring them belongs to JavaScript Phase 9 (List.js).
  5. Add-product pricing fields may reuse input-group prefixes and suffixes from Chapter 12.
  6. Prefer one elevation system on the admin canvas, matching Chapter 18.
  7. Dropzone chrome still wraps a real file input.
  8. Prefer CSS variables for surface, border, muted text, success, and danger.

Not allowed

Pages

Rules to lean on

Rules 2, 10, 99–110, 111–122, 175–195, storefront rules, and admin commerce rules added for Chapter 20.