Aurora static HTML starter store

During the design and implementation phases of your project, use the static HTML starter store to demonstrate starter store features to key stakeholders in your organization early in the project cycle and create a fit gap analysis document to identify all customization that is required in the store. You can also accelerate your web design cycle by using the static HTML starter store to mock up any user interface changes by using the CSS or HTML pages.

After a web designer modifies the static HTML starter store pages, a store developer can identify the affected JSP files by using the highlight feature and then implement the changes in JSP files. When the project is complete, a store developer can generate static HTML store pages for the customized store. The generated static HTML files can serve as a basis for the design phase in future projects.

Use the static HTML starter store to:
  • Preview basic functions in the starter store during the implementation phase of your project. The static HTML files contain all the store pages and their different supported flows. For example, there are different pages to demonstrate an empty shopping cart, a shopping cart page that contains more than 20 items with pagination. The files are also mobile and can be opened in the browsers that are supported by the store.
  • Identify changes to the appearance of functionality of the store.
  • Modify HTML and CSS files without using a development environment. The changes can be incorporated into the corresponding JSP files by a JSP developer at a more convenient time.
  • Determine the JSP files that dynamically render the different areas on specific pages in a storefront. You can use the highlight feature tool by pressing Ctrl + Alt H to identify the JSP files that make up the page you are on. It marks off each area of the page that a JSP file represents and shows the file name in the upper left corner.
The package consists of five main components:
Index HTML file Provides links to the different flows available for the Aurora starter store, with a description. The static HTML store pages within a flow that use the dynamic links on the pages.
Static HTML store pages Divided into a series of different flows that represent the core functionality of the store. For example, one flow contains the pages that are seen during a guest checkout. Another contains the pages that are seen during a Quick Checkout flow that is completes by a registered customer.
CSS, image, and JavaScript files Determine the appearance of the storefront and some of its behavior.
Dojo framework Allows the static HTML store pages to mimic their standard behavior when they are run on a WebSphere Commerce Server.
bin directory Contains the tools that are required to generate your own set of static pages.
Note: Static HTML packages rely on Dojo to load locally on the user's personal computer, otherwise the package breaks, and JavaScript errors are visible on the page. Most browsers implement a security feature that blocks JavaScript and Dojo from running local files. Configure your browser to prevent JavaScript errors from happening:
  • Chrome - Open Chrome with "--allow-file-access-from-files" option
  • Firefox - Browse to the about:config page. Set security.fileuri.strict_origin_policy to false. Close and then restart Firefox.
  • Internet Explorer - No configuration changes are required.