What this module is for

CMS / Banners is the operator workspace for banner inventory, banner creation, and the editor route where content teams control draft content, publication, and banner visibility.

Main surfaces

• List is the inventory grid with filters, untranslated-language stats, and the create-banner modal.
• Form is the lightweight creation flow where operators register a new banner key and display name.
• Detail is the full editor where operators change content, audience, country restrictions, visibility, and publication status.

How operators usually use it

1. Filter the grid by key, name, type, state, or publication status.
2. Create a shell banner record from the modal.
3. Open the detail route to fill content, upload media, and define who should see the banner.
4. Save draft changes first, then publish when the banner is ready for casino delivery.

Common confusion

• State is the operational visibility of the banner (active or disabled).
• Status is the content lifecycle of the editor snapshot (draft, published, archived).
• Publishing does not create the banner. The banner record exists after create; publish only promotes the current draft content.

Verification note

The current backoffice banner surfaces do not use gs-admin-backend banner CRUD as their canonical write path. The active operator flow is backed by nx-workspace/services/core under /api/core/banners*, so this module is verified as verified_backend_and_core.