saleor-dashboard-entity-detail

Use DetailPageLayout with TopNav, a main content column ordered as identity settings, primary content, then SEO last, a right sidebar for membership assigns, and a Savebar. Add DetailPageSectionLayout with DetailSectionNav only when the page has four or more scroll sections.

Use DetailSettingsCard for primary settings sections in the main column; it owns title typography, an optional intro band, and a headerEnd slot that coerces buttons to small size. Do not use SettingsSection, which belongs to Configuration hubs.

Use FixedAtCreationField, which renders a disabled Input with a lock icon and a required helper text explaining the alternative. Never use a disabled Combobox or Select, since the chevron implies the field is editable.

Use DetailPageSectionLayout with a section nav rail when the page has four or more scroll targets, as on channel details. Use DetailPageContent for simpler single-column pages like collections or gift cards, and never nest DetailPageContent inside DetailPageSectionLayout.

Do not apply these conventions to Configuration hubs such as Orders settings, Tax, or Site settings; those use the Settings* components in src/components/Settings/. The entity detail language targets daily-workflow models like channels, products, and warehouses.