Skip to content

Early Access

What is Early Access?

Early Access is your chance to be an early adopter of the new Hyvä Commerce product.

You get a suite of modules that can be installed as a whole (via composer metapackage) or individually.

There is no need to wait to get familiar with our product, and you can share feedback and report issues that will help us shape our product offering and prioritise the features you, or your merchants, need.

To get Early Access, you still need to purchase a Hyvä Commerce license.

Development status

You can keep up to date on the status for all our Hyvä Commerce offerings during Early Access via our updates in the #hyva-commerce and #hyva-cms Slack channels.

Early Access vs General Availability

The following list outlines the features that have reached General Availability, as well as those currently in Early Access or Under Development. For a preview of upcoming features, please refer to our Hyvä Commerce Roadmap.

Missing Features & Known Issues

Below is our current list of noteworthy missing functionality and known issues for included features, that we will update with every release, or if new issues are discovered.

Hyvä CMS

Final Components and Structure

At present, the majority of components are still undergoing heavy development, both in terms of their structure, such as the fields included and the data they store, as well as their frontend templates in regard to markup, Tailwind styles and any JavaScript (e.g. Alpine) logic.

For a full list of components status, see Hyvä CMS Components.

CSP Support

Not all components that utilise JavaScript (Alpine.js) have full CSP support. This support will be provided before we reach General Availability at the latest, but likely much sooner.

Media Optimization Support

Hyvä CMS components that output imagery, are not yet integrated with our upcoming Media Optimization that will allow for image resizing and conversion to other formats (e.g. WebP/AVIF). These changes will affect the markup used within these components, replacing the current <img> output with a <picutre> that is rendered via a provided ViewModel.

Dependency Impact

While frontend template files will be updated with the above change, given our commitment to let you 'mix and match' which Hyvä Commerce features you use and install, you will still be able to use Hyvä CMS independently of Media Optimization as we'll include a base interface and empty implementation in the Hyva_Theme module, that is replaced only when Hyva_MediaOptimization is installed. Therefore, the only requirement will be to upgrade to the latest version of Hyva_Theme, which we always keep backwards compatible.

Image Editor Support

Once our Image Editor is available it will be integrated with the default Media Gallery, which will allow for use when selecting images anywhere within Hyvä CMS.

Restricting Components by Parent Component Type

At present, while a component can limit which components can be added as children, there is no inverse approach for restricting which components a component can be a parent of. This currently means that components that are intended to only be used as children of other components, appear when adding components to the root of the tree, or under other components with no child restrictions.

This currently affects both the child components for Accordion Lists (child: Accordion) and USP Lists (child: USP). The USP component will currently error when being added outside a USP List as it does not have its own dedicated template (it is rendered inside the USP List template).

Admin Editor Performance for Stores with Many Scopes

The scope switcher in the Liveview editor currently has no limit, which may cause performance issue if there are many (e.g. 100's of) scopes within a Magento instance. We plan to resolve this by limiting the initial results and providing a search feature.

CMS JIT Specificity Issues

We're still working on finalising support for CMS JIT, to allow including custom Tailwind CSS to components via the 'Classes' field in the 'Advanced' tab of a components edit panel. While this currently works, there are some specificity issues which can affect other areas of the page, which we're aiming to resolve soon.

Editor UI Translation Strings/Support

There is currently no translation CSV provided with the CMS modules to aid with translating UI areas of the Hyvä CMS Liveview editor, such as menu items and component names and field labels. This will be provided before we reach General Availability at the latest.

Denoting missing features and areas to refactor

In order to further aid your development and future upgradability decisions, we'll also add TODO comments to files where we are aware of missing functionality, or where we anticipate that we will make substantial changes, along with denoting what is likely to change.

Most IDEs either have built-in support for finding TODO comments, such as PhpStorm, or offer extensions/plugins.

Versioning

During Early Access our versioning will be slightly different from what you may be used to with the main Hyvä Theme (and accompanying Hyva_Theme module) to reflect the nature of modules that are not yet fully complete, but need some level of refactoring to ensure consistency and at that they meet Hyvä standards.

To help you understand which modules are in what status we'll be using the following versioning:

  • 0.x.x (e.g. 0.1.0) will be used to denote any module that has begun implementation but has key features missing and/or requires substantial refactoring* to meet Hyvä's standards
  • 1.x.x (e.g. 1.0.0) will be used to denote any module that has all key features implemented as does not require any substantial level of refactoring. At this stage all future versioning will follow that of our GA (General Availability) products, such as Hyvä Theme and Hyvä Checkout, where backwards incompatible changes are avoided, and in the cases they cannot, they will be supported by producing tools to provide seamless migration/upgrade paths.

Metapackage versioning & general availability

Our metapackage for Hyvä Commerce will also follow the above versioning and will remain in a 0.x.x state for the majority of Early Access, until all initial features within the metapackage reach 1.0.0 (or above). Therefore, once all modules reach version 1.0.0 (or above), this will indicate that Early Access has ended, and we will then enter General Availability.

Plans for managing future Early Access versions of new features (modules) alongside those already in General Availability will be shared at a later date.

Providing feedback & getting help

See our Overview page.