Ektron
This chapter uses a fictitious site, EktronStore.com, to demonstrate how to set up, build, and deploy an online marketplace using Ektron. EktronStore.com sells furniture and accessories and leverages many eCommerce features.
Before starting to build EktronStore.com, consider the goals of your online marketplace. Do you want to simply sell as many products as possible? Or, do you see your store as a value-added component designed to enhance the customer (site visitor) experience?
When considering store design and functionality, what you intend to sell plays a significant role in this endeavor. For example, are you selling durable goods? Subscriptions? Access to premium content? All of the above? Make sure you consider this when planning the store's layout.
Shipping options, payment methods, taxation, and the general look-and-feel of your store also need to be determined. Make sure you address the general workflow of your store—that is, how shoppers are guided through the entire shopping experience.
It all starts by planning the basic architecture of the store. This is called a “sitemap,” and depicts the architecture of the website. It can be either a document used as a planning tool for Web design, or a Web page that lists the pages on a website, typically organized in hierarchical fashion.
Essentially, the sitemap identifies the major pages, sections, sub-sections, and shared elements of the site.
Next, plan and scope out the major pages in your store. Using pencil and paper or software, sketch the basic architecture and components of individual store pages. This visual guide is referred to as a “wireframethe architecture of a Web page containing columns, dropzones, and layout information.”.
When using eCommerce, a customer sees images that represent products or services for sale. The following list shows each image that appears on an eCommerce website, and its source.
NOTE: The sample catalog entries are based on Product Types whose XML Smart Forman Ektron-defined Web page that contains XML (hidden from the end user) to display content, and receive, verify, and save user input. includes an Image field. As a result, the product description, (which appears at the top of the Product Server control) includes an image. This is not required, merely a suggested implementation.
NOTE: To control the thumbnail display, use the XSLT files generated by the Product, Product List, Product Search, and Recommendation server controls.
When a customer clicks a thumbnail, the corresponding full image appears.
Because the Media screen can have several images, several thumbnails can appear. They appear left to right reflecting their sequence (top to bottom) on the Media screen. If an image’s Gallery Display field is set to Yes, its smallest thumbnail appears on the Product server control, below the content area. (This assumes you are using the control’s default XSLTExtensible Stylesheet Language Transformations.) See Also: Determining Thumbnail Size