Hyvä CMS FAQs

Common questions about what Hyvä CMS does, how it fits alongside the native Magento content tools, and what merchants and developers can do with it.

Where can I use Hyvä CMS to manage content?

Core Hyvä CMS supports CMS pages, CMS blocks, and product and category attributes such as descriptions. Developers can add support for custom entities; see Extending for Other Content Types.

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 rebuild content manually in Hyvä CMS, or use the Page Builder migration tools as a starting point. Review migrated content before publishing.

Can I disable Page Builder when using Hyvä CMS?

Hyvä CMS has no 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 content scheduling. 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 and 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; see Working with Components. Admin users with the right permissions can also create database-backed instance components.