1. Developing Open Storefront Framework Applications for Oracle Commerce
  2. Design Storefront Pages
  3. Understand how to use the Design page with OSF applications

Understand how to use the Design page with OSF applications

If you are experienced using the Design page in the administration interface to work with classic framework design assets, you will find working with OSF design assets to be a nearly identical experience.

Not all Design page features you are used to using with the classic framework are available for OSF applications. This section describes differences you may encounter when working with OSF design assets in the administration interface.

  • OSF widgets and layouts are associated with applications that have been deployed to the Commerce server. In order to view and access an application's widgets and layouts on the Design page, you must first select the application. See Select an application for more information.
  • The Design Code Utility (on the Design page's Developer tab) is still available to download and use with classic framework applications, but it is not available to use with OSF applications. OSF application code is managed in a developer’s local workspace. See Develop and Deploy Applications for more information.
  • In the classic framework, global text snippets enable you to directly access your web store’s customizable global text, which can include messages, labels and help tips. In OSF applications, shared locale strings are the equivalent of global text snippets. You cannot use the administration interface to edit an application's shared locale strings. These can be edited only in a local workspace. See Configure widgets in the administration interface for more information.
  • In the classic framework, a theme is a set of styling configurations, including colors, fonts, and other design elements, that defines the overall look and feel of the online store. OSF applications do not use themes and so the Theme tab is not available for OSF applications. Design elements controlled by themes in classic storefront are controlled by CSS styling in OSF applications. CSS files must be configured by a developer in a local workspace. See Build a Widget for an example of creating styles CSS files in a local workspace.
  • On a widget’s details page, the Extend JavaScript, Go to Widget Code, and Download Source buttons are not available. This is because OSF widget code is created and edited in a developer’s local workspace. See Create Custom Widgets for more information.