Book a demo
Pricing

Build pages from blocks.

A flexible, block-based CMS inside the platform. Assemble pages from ready-made blocks, add your own modules, and let global components update in one place. Drag and drop to rearrange.

Book a demo Visual editor

A page is a stack of blocks.

The page builder

Blocks can be hidden per channel and scheduled, so a campaign page can sit ready and release itself.

Custom modules

Your own blocks, with your own fields.

A module is defined once.

A custom module is a block with its own field schema. The developer defines the fields and the template; the editor fills them in like any other block. New fields can be added without breaking existing pages.

  • Field types: text, rich text, image, file, number, choice, table, product relation, attribute
  • A module can read data from the PIM, from orders or from your own API
  • Permissions per module — who may use it and where
  • The same module works in the store, the B2B portal and landing pages

Global components — change once.

Reuse

A global component can be scheduled — the campaign banner goes in now and switches itself on come release day.

Drag and drop

Move, duplicate, hide.

Move

Grab the handle

Pick the block up and drop it where it belongs. The drop zone shows where it will land before you let go.

Reuse

Duplicate or make it global

A block can be duplicated on the page, or promoted to a global component if it belongs on several.

Control

Hide per channel and date

Any block can be hidden in a channel or scheduled, without anyone having to copy the whole page.

Coming soon

Visual editor

The next step is editing the page directly in the rendered view rather than in the block list. The blocks already exist — the editor adds a layer on top of them.

  • Click into the page to edit the text where it sits
  • Drag blocks in the real layout, not in a list
  • Switch between desktop, tablet and mobile while you edit
  • The same blocks, the same modules, the same permissions

Pages built today will work in the visual editor when it ships. Nothing needs redoing.

With a separate CMS

Two versions of the truth about one page

Product data has to be mirrored into the CMS

Two logins and two permission models

The campaign page knows nothing about stock

An extra subscription and an integration

With the CMS in the platform

The page knows the store

Blocks read products, prices and stock directly

The same roles govern pages, products and orders

Publishing is recorded in the activity log

The CMS is included — no extra licence

Questions about the CMS.

Common questions

Can editors build pages without a developer?+

Yes. Pages are assembled from blocks in the editor. Developers are only needed when you want a new module or a new block type.

What is the difference between a block and a global component?+

A block belongs to its page. A global component exists on several pages and is updated in one place — the change takes effect everywhere it is used.

Can blocks pull product data?+

Yes. Product rows, category tiles and custom modules read from the PIM and show current price and stock with no mirroring.

Can content be scheduled?+

Yes, per block and per global component. A campaign page can sit finished and publish itself.

When does the visual editor arrive?+

It is in development. Pages built in today’s block editor will work in it without rebuilding.

Can we control who edits what?+

Yes. Permissions are set per page, module and channel, so an agency can edit campaign pages without reaching product data.

See the editor

Build a campaign page in the demo.

We assemble a page from blocks in ten minutes and show how one global component ripples through the rest.