The custom pages feature is used to create or upload HTML pages and body content for use on your site. After you create or upload a custom page, you then use the files feature to upload the images, CSS, video files, and other resources that are used by the custom pages you have created or uploaded (see About Files for more about the files feature).
A custom page is simply an HTML file that will serve as the "body" content for a static page on your store. Custom pages are most often used as landing pages for marketing offers and promotions. They can also be used as static content pages (pages where the content does not change) such as the "Company Information" page, and so on.
Tip: If you want to use images or other resource files in your custom page, you should upload those files first, before you upload or create the custom page. This is because you will need to copy and paste paths to those images into the body content of your custom page.
There are two ways to get a custom page. You can either create the page using the Command Console or create the page outside the Command Console (using a third-party application) and upload it to the Command Console when finished. Regardless of how you create the page (whether it is in the Command Console or a third-party program) the basic rules and requirements are the same.
<body>
tags of the page. See Using HTML in the Command Console for more about how you should enter your HTML to create a Custom Page outside of the Command Console.As you work with custom pages, the status and version of the custom page will change based on what actions have been taken on the custom page.
Status | Definition |
---|---|
Design | Custom page has been created and saved, but not yet deployed. |
Deployed | Custom page has been created and deployed. Custom pages that are deployed were once in design. |
Retired | Custom page has been retired. Custom pages that are retired were once deployed. |
When you create a custom page, you can select which locales you want the custom page to be used with. If a shopper in a locale tries to access the custom page and you have not set that shopper's locales as supported, the custom page loaded for the default locale will be used.
When you create a custom page in the Command Console, you can use "tokens" to automatically apply attributes or insert content into the page. For example, you can use a token to automatically color the background of the page or insert the total price of the shopping cart. For more information about tokens, see Using Tokens.
Tokens are set up when your site is created and are customized by site. There are some tokens that are available on all sites but most tokens are set up for your site specifically when it is created. Contact your Store Operations team with further questions about getting tokens added to your site.
Custom pages are not accessible through your store until you create links to them. This means that after you create or upload a custom page, you should use the Links feature to create a link to the page so your shoppers can access it. You can also use links in your custom pages to perform actions such as adding a product to the cart. See About Links for more about creating or using links.
© 2019 Digital River, Inc.