Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Cloud UI 1.2 introduces a initial separate UI that can be used for most product detail pages, extending on the 1.0 release, which enabled separate UI for the Pricing Calendar. Cloud UI is our standalone application layer that decouples frontend code from the nopCommerce backend. Separating the UI from the API infrastructure provides the following benefits:

  • More frequent, lower-risk frontend-only releases

  • Creation of distinct, releasable units

  • Shift toward a modern application server framework

  • Improved page load performance over time as more of the site is migrated to this framework

The Cloud UI is the foundation for our upcoming redesign of the shopping pages.

IMPORTANT: While Cloud UI is supported for most product detail pages, there are some features and configuration options that are not yet supported in the Cloud UI, that will continue to work if loaded on legacy. In this guide we detail which product detail pages should NOT be moved over and detail how to ensure that these products continue to load and work on the legacy UI, while other (supported) products will load in the new separate Cloud UI.

Detailed Setup Guide

Most products are Cloud UI compatible, but there are some exceptions. For these exception products, there is a new product-level setting that enables some products to continue to load for users in the legacy UI, and for the majority of products to load in the new Cloud UI. To flag a product so that it continues to load in the legacy ui, find the product from Catalog > Products >Edit.

A new product-level setting called “Use Legacy Product Page” has been added to the set of Aspenware Commerce settings that should only be turned on if a product is incompatible with the Cloud UI (details below).

Which products are incompatible with Cloud UI V1?

If a product has any of the following features/configurations enabled on the PDP it should NOT load on the Cloud UI and should be flagged to continue to display legacy PDP. These products will continue to work so long as they are not loaded on Cloud UI.

  • Assigned to attribute enabling Assignment on the PDP

  • Affirm enabled products

  • Products that can only be accessed using a valid voucher

  • Payment Plan products

  • Reservation products

  • IKON Friends and Family ticket

  • Fast Flow

  • Arrive Parking

  • Retail

Initially the user experience and UI will be identical between legacy and cloud pages, however, with Cloud 1.3, the Cloud UI product detail pages will have a refreshed look and feel and theme application according to our design system, while legacy product detail pages will remain unchanged.


 


  • No labels