Developing Aurora starter store pages

Developing and maintaining store pages can become an efficient and consistent process by following the general practices used in existing Aurora starter store pages.

• Adding extension logic to all store pages
  We can configure the Aurora starter store to include custom extension logic, such as self contained JSP on all store pages. By using this configuration, we can easily embed common code on all store pages, or embed code for tracking the browsing history of shoppers.

• Enable subscription support in the order component
  In order to enable subscription support in the order component, the order configuration file must be updated.

• Enable and configuring site search statistics
  We can gather data for the site into search statistics reports so that we can view and analyze them in the Management Center.

• Catalog image requirements for the Aurora starter store
  For each catalog entry (product, SKU, bundle, and kit), the Aurora starter store displays images in various sizes in different locations. The catalog entry images must be at a path that follows a naming convention. For a catalog entry, images of various sizes must have the same file name.

• Dynamic caching in the Aurora starter store
  In the Aurora starter store, dynamic caching is enabled by default. Dynamic caching reduces the server load because significant segments of the page, such as store widgets, do not have to be retrieved from the server on every new page display.

• Commonly used JSTL variables in starter store pages
  The EnvironmentSetup.jspf file is a configuration file that is commonly included in starter store pages. The variables declared within this file can be modified to change the appearances and behaviors of storefront components.

• Override the loading of categories in the catalog browsing menu
  We can override the behavior for loading the catalog browsing menu on individual store pages to control the display of the menu and improve the performance of loading store pages. By configuring the behavior for the catalog browsing menu, we can configure whether a store page loads only the top-level category in the catalog browsing menu when the page loads or loads all categories in the menu. The catalog browsing menu is a pop-up menu that includes a list of departments and categories.

• Adding and changing messages in the Aurora store
  We can add new messages or change existing messages in starter store pages by modifying the file containing the store strings.

• Enable the progress bar in new Aurora starter store pages
  The progress bar is displayed when an AJAX request is triggered and removed when the request completes. It serves as a confirmation indicator on the page, where additional actions can still be performed by the customer. That is, it does not impede the customer from performing additional actions on the page.

• Enable the account activation by email function in the Aurora starter store
  We can enable account activation so that customers must click an activation URL before they become registered in the Aurora starter store.

• Disable the account activation by email function in the Aurora starter store
  We can disable the account activation by email function if the function is enabled.

• Shortening the context root of a store URL
  Shortening the context root of a store's URL makes it easier for shoppers to remember a link and also improves visibility in search engine results.

• (Enterprise) Uploading requisition lists
  We can create a requisition list in a text or spreadsheet editor and upload the requisition list to the store. A requisition list is a reusable list of items (SKUs) that we can use to create orders. Requisition lists are supported when the Aurora starter store is published as a B2B store.

• Enable a Subscribe link for an e-Marketing Spot feed in the Aurora starter store
  The Aurora starter store includes a feature that allows customers to subscribe to e-Marketing Spot feeds for catalog entry recommendations. To familiarize yourself with the Aurora implementation, we can enable and test the Subscribe link for an e-Marketing Spot on the Department page. Then, consider a similar implementation for our own store.

• Enable a Subscribe link for a wish list feed in the Aurora starter store
  The Aurora starter store includes a feature that allows shoppers to subscribe to wish list feeds. To familiarize yourself with the Aurora implementation, we can enable and test the Subscribe link for the wish list. Then, consider a similar implementation for our own store.

• Updating the Aurora starter store for key splitting
  The key splitting feature might potentially expose some JavaScript coding issues in the store JSP pages. JSP pages that passed or initialized JSTL variables of object's primary keys (or identifiers) into JavaScript variables as integers might be subject to unexpected behavior in the storefront.

• Enable image-based facets for the B2B Hardware category
  After you publish the Aurora starter store as a B2B store, we can enable certain facets for products in the Fasteners and Lighting categories. These facets, such as Head style for screws and Bulb shape for lighting products, have associated images to help buyers find the right product quickly. The enablement steps involve selecting the descriptive attributes to display as facets in the Catalogs tool in Management Center and then previewing the results.

• Enable the Cancel button for orders on the Order Details page
  To allow shoppers to cancel orders, we can enable the Cancel button on the Order Details page for the Aurora starter store. The enablement steps involve installing interim fixes that contain code required for the Cancel button to function and defining modification rules for order statuses in Sterling Order Management.

• Currency formatting in the Aurora starter store
  The Aurora starter store uses the JavaServer Pages Standard Tag Library (JSTL) API to format the currencies that are displayed on store pages.

• Methods for retrieving configuration parameters from the STORECONF table
  We can use the StoreConfigurationRegistry to access store configuration values in the STORECONF database table from either Java code or JSP files.