Admin CMS

The admin CMS is a single-page app for store managers. It talks to the backend admin API v2 with a JWT from /api/token/, and one instance works on one channel, set by VUE_APP_CHANNEL. What a channel is: Concepts.

What It Covers

• content pages and the blog, built with the visual page builder
• the catalog (products, attributes, categories, media)
• pricing, stock and promotions
• orders and customers
• forms and agreements
• FAQ
• translations
• suppliers
• leads

A panel appears only when its backend module is installed. The CMS asks the module registry (GET /api/munin/v2/) at runtime and hides the panels whose module is missing.

Stack

Vue 3, Pinia, Vue Router, the TipTap editor and axios, built with Vue CLI.

Run It Locally

From the Docker harness (entirius-zeno):

• make cms builds the image from the GitHub repo and serves it on http://localhost:8180/. Sign in as admin / admin123, the harness defaults.
• make cms-dev serves your clone in repos/pwa/entirius-pwa-cms with hot reload.

On its own, from a clone of the repo:

npm ci
cp .env.example .env
npm run serve

Configuration

Environment variables live in .env:

Variable	Meaning
VUE_APP_API_URL	Backend API base URL. Required.
VUE_APP_CHANNEL	The channel this instance edits. Required.
VUE_APP_LANG	Interface language, EN or PL.
VUE_APP_PANELS	Panel IDs to show when the module registry does not answer.
VUE_APP_SSO_API_BASE	Path of the backend SSO endpoints. When set, the login screen shows SSO login.
VUE_APP_DEBUG	API debug logging.

npm run build bakes the values into the static app, so a changed value needs a new build; the dev server (npm run serve) reads them when it starts.

When a required value is missing, the app shows a “Configuration Required” screen that lists it.

The page builder (section types, tile types, properties) is configured in __client/. That directory is not committed: npm run init:client generates it from __client_default/, and npm run serve does the same on first run. The full reference is docs/config-system.md in the repo.

Documentation

The repo documents itself:

• README
• AGENTS.md
• CHANGELOG
• docs/: panels-routing.md, config-system.md, navigation-editor.md, rich-content-building.md, sso-login.md, testing.md

Click-paths for the everyday tasks in the CMS are in CMS Guides.

Next

Storefront