Skip to content

Hyvä CMS

Hyvä CMS is a component-based content management system for Hyvä Commerce. It gives merchants a live visual editor for Magento content while giving developers a structured component system, Magento templates, versioned content, APIs, and extension points.

Liveview Editor

What Hyvä CMS Can Manage

Core Hyvä CMS supports:

  • CMS pages
  • CMS blocks
  • Product attributes such as descriptions
  • Category attributes such as descriptions
  • Templates and snippets for reusable content structures

Developers can also add Hyvä CMS support to custom entities, for example blog modules or other project-specific content types.

Key Features

  • Live Preview - edit content while seeing the storefront result in the Liveview Editor.
  • Draft And Publish Workflow - save drafts without changing live content, then publish when ready.
  • Version History - review, restore, compare, pin, and name previous versions.
  • Reusable Components - build pages from prebuilt and project-specific content components.
  • Rich Text and Variables - write formatted copy and insert dynamic Magento variables and directives in rich text fields.
  • Templates And Snippets - reuse complete layouts or smaller sections.
  • Translations - translate translatable fields per store view without duplicating the whole content structure.
  • Content Scheduling - schedule Hyvä CMS content publication independently from Adobe Content Staging.
  • Transfer Center - move pages, blocks, attributes, media, translations, history, and instance components between environments.
  • Personalized Editing - per-user editor preferences, favourite components, and customizable keyboard shortcuts.
  • REST And GraphQL APIs - integrate admin workflows through REST and fetch published page/block content through GraphQL.

Who Uses It

Merchants use Hyvä CMS to create and update content without editing Magento templates or CSS classes. Developers use it to define the reusable components, rendering templates, field types, and integration logic that keep the content output reliable.

The best projects treat Hyvä CMS as a design-system editor: merchants choose from clear, approved components, while developers control the HTML, styling, data access, and validation behind those components.

FAQs

Where can I use Hyvä CMS to manage content?

Core Hyvä CMS supports CMS pages, CMS blocks, product attributes, and category attributes. Developers can add support for custom entities by following the extension guidelines.

Is Hyvä CMS required when using Hyvä Commerce?

No. As with other Hyvä Commerce features, use Hyvä CMS where it fits your project needs.

Does Hyvä CMS replace Page Builder or the Magento WYSIWYG editor?

It can replace their frontend output for content where Hyvä CMS is enabled. The original Magento content is not deleted, so disabling Hyvä CMS for that entity returns output to the native Magento field. Hyvä CMS and Page Builder can coexist in the same installation.

Can I migrate content from Page Builder or WYSIWYG content?

Yes. You can manually rebuild content in Hyvä CMS or use the Page Builder migration tools as a starting point. Migrated content should still be reviewed before publishing.

Can I disable Page Builder when using Hyvä CMS?

Hyvä CMS does not have a hard dependency on Page Builder. It may be possible to disable or remove Page Builder in a project, but Hyvä does not provide general support guidance for that process.

Can I schedule content with Hyvä CMS?

Yes. Hyvä CMS has its own scheduling system for Hyvä CMS content. Adobe Commerce Content Staging can coexist with Hyvä CMS, but Adobe scheduling cannot publish Hyvä CMS draft content.

Can I translate content?

Yes. Fields that opt in to translation support can be translated per store view through the translation panel and CSV import/export workflow.

Can I create reusable templates or snippets?

Yes. Templates store full starting layouts, and snippets store selected reusable sections. Administrators can also configure default templates for new content types.

Can developers create custom components?

Yes. Developers can create code-defined components in components.json, override base component templates, create custom field types, and add support for other content types. Admin users with the right permissions can also create database-backed instance components.