Game menus, promotion pages, skin-specific layouts, jurisdiction-specific content rules. Operators control it. Developers stay focused on what actually needs them. Built on Blazor — fast, reactive, no page reloads.
Adapting WordPress to manage a casino lobby ends with custom plugins, brittle deployments, and a permissions model that doesn't match how operators actually work. WebPrefer's CMS is built from the start around game providers, brands, skins, jurisdictions, and the back-office permission model.
Drag-and-drop sections, featured games, category ordering — across all brands from one editor. Changes propagate live.
Build promo pages with bonus code wiring built in. Page schedules, regional visibility, and CTA tracking all native.
Each brand has its own skin without forking templates. Marketing changes one brand's hero without touching another.
Sweden players see Sweden-compliant terms. Ontario players see Ontario CTAs. Rules enforced at render time, not by guesswork.
Fast, reactive editor with no page reloads. Same .NET stack as the rest of the platform — one toolchain, one deploy.
Same RBAC as PAM. Content editors get exactly the access they need — no separate user system to maintain.
CMS lives inside the WebPrefer platform — same auth, same RBAC, same back-office shell. Operators don't switch tools to publish content or to manage players. Developers don't maintain a parallel content stack.
Most CMS workflows assume one site, one audience, one editor. iGaming reality is multiple brands, multiple jurisdictions, regulated copy reviews, and a marketing team that wants to publish a promo at midnight without paging an engineer. The workflow is shaped accordingly.
Marketing creates or edits a page targeting a specific brand and jurisdiction. Drafts stay private. Linked bonus codes, game menus, and promotion windows wire in without leaving the editor.
Regulated markets need a legal review before terms or bonus T&Cs go live. The CMS supports approval gates by permission — drafts can require a reviewer with a specific role before publish is enabled.
Publish writes the new version to the database and invalidates the matching Redis cache keys. The next player request hits a cold cache once, then everyone after gets fresh content from cache — usually within 100ms of publish.
Every save and publish is a new version with editor, timestamp, brand, and diff. Roll back to any version with one click. Audit entries flow into the same event log as the rest of the platform.
CMS is a module inside the WebPrefer platform. No separate deployment, no second user system, no parallel permission model. Operators install PAM and get CMS in the box.
Fast, reactive editor with no page reloads. Same toolchain and deploy pipeline as the rest of PAM.
Every save creates a new version. Compare any two versions, roll back instantly, never lose a draft.
Editor scoping enforced at query time. A marketing manager for Brand A literally cannot see Brand B drafts.
Published content hits Redis cache. Player site reads are sub-millisecond — DB hit only on first request after publish.
A single page definition renders differently per skin via the skin selector — no template forks, no copy-paste across brands.
Every publish and draft change writes to the same audit pipeline as wallet operations and KYC reviews.
We'll show how operators run game lobbies, promotion pages, and skin-specific content for several brands from a single editor — and how it plugs into the rest of the platform.