CMS

Content Management

Compose rich pages from reusable widgets—fully headless

What it does and who it's for

Geins CMS lets teams compose rich, modular pages from reusable widgets while keeping the frontend fully headless. Content and brand teams can ship campaigns fast, and developers can build custom widgets and layouts when needed.

Filters target content by channel, language, customer group, category, brand, product, or campaign; pages include localized URLs and metadata, and scheduling handles time‑based publishing.

Key capabilities

Areas and containers

Pre‑configured areas for Start, Product list, Product, and Pages

Filters

Channel, Language, Customer group, Category, Brand, Product, Campaign

Widgets

Built‑in catalog and custom widget designer

Menus

Hierarchical menus linking to catalog entities or custom links

Scheduling

Time‑bound content at area/container/widget levels

What you can build

With these capabilities, you can compose modular landing pages, targeted PLP/PDP modules, navigation, and scheduled campaigns—while keeping the rendering fully headless. A/B variants and audience filters let you test and iterate without hard‑coding layouts.

Modular landing pages
Build pages from reusable widgets and containers, with content editors in control.
PLP hero & targeted modules
Target category and brand‑specific modules to drive merchandising and campaigns.
PDP content blocks
Add size guides, UGC, comparison tables, and more—localized per market.
Navigation menus
Link menus to catalog entities or custom URLs to keep navigation consistent.
Scheduled campaigns & takeovers
Schedule time‑boxed homepages and promotions with built‑in publishing controls.
A/B content variants
Use container swaps and audience filters to test variants without code changes.

How it works in Geins

CMS content is organized into areas per page type, with containers that hold widgets. Filters determine where content appears across channels, languages, and audiences, while localization maintains market‑specific texts and metadata.

Your storefront renders everything headlessly by mapping widgets to components.

Areas & containers
Define areas per page type and manage containers that organize widgets.
Filters & targeting
Target by channel, language, customer group, category, brand, product, or campaign.
Localization & SEO
Localize content and metadata per market/language, including URLs and hreflang.
Headless rendering
Map widgets to storefront components; fetch data via Merchant API.

Integrations

Geins CMS plugs into your storefront via Merchant API and pairs with Promotions and Feeds to power dynamic content. You can also integrate external services through custom widgets.

  • Merchant API for storefront rendering
  • Promotions & Feeds for dynamic content
  • Custom widget endpoints/services

Real‑world outcomes

With headless rendering and reusable widgets, teams ship campaigns faster with fewer developer bottlenecks. Scheduling and scoped filters reduce risk, and customers get a consistent experience across product, category, and landing pages.

Faster campaign launches
Empower content teams to build and publish without blocking development.
Safer publishing
Schedule and scope changes to reduce risk during releases and campaigns.
Consistent UX
Keep PDP/PLP/landing pages aligned with reusable, localized building blocks.

Get started

Map page types

Map your page types to CMS areas and define containers.

Configure targeting

Set filters and audience rules; localize content and metadata.

Build & compose

Build or extend widgets as needed and compose pages from reusable blocks.

Render & deploy

Integrate rendering via Merchant API, test, and deploy.


Best practices

Practical tips for scaling content with a headless storefront.

Reusable widget library
Keep a small, shared library of widgets to speed up authoring and maintenance.
Prefer filters over code
Use audience and catalog filters instead of hard‑coding layouts to stay flexible.
Localize content & SEO
Localize texts, URLs, and metadata together to keep each market consistent.

FAQs

Ship content fast—keep your frontend headless