What this module is for

Use CMS / Configuration when operators need to manage shared design or content configuration keys instead of editing one banner or one page.

Included units

• List: configuration catalog with filters, status chips, publish and delete actions
• Detail: modal-based edit and publish flow for one configuration version
• Variables snapshot: comparison grid that shows configured values against theme defaults and related metadata

When operators usually open this module

• a shared design token or CMS configuration variable must be created
• a country-specific configuration should be added or updated
• a draft configuration version should be published
• operators need to compare admin-configured values with theme defaults
• a broken import or outdated configuration set must be exported, deleted, or restored

Common confusion

• Status and State are different. Status describes whether the configuration row is active or inactive. State describes the content version lifecycle such as draft or published.
• One logical configuration key can exist in versioned form. The core create service can generate keys like __vN when a base key already exists.
• The screen mixes two jobs: maintaining configuration rows and comparing the active rows with theme defaults. The variable snapshot is a support table, not a second persistence source.

Verification status

• status: verified_backend_and_core
• FE source: nx-admin-fe-workspace
• core source: nx-workspace/services/core
• gs-admin-backend: not required for the first verified save and publish flow