----------------------------------------------------------------------- SMS Default Pageset Version 2.0 January 28, 2004 ----------------------------------------------------------------------- This README.txt file is designed to provide development/customizable details for developers/media producers when implementing the pageset. ------------------------ How to use this document ------------------------ To view README.txt on your screen in Notepad, maximize the Notepad window. To print README.txt, open it in Notepad, WordPad, or another word processor. Then select the entire document and format the text in 10-point Courier font before printing. ------------------------------------- The following subjects are discussed: ------------------------------------- 1. List of included files 2. Instructions to implement directory structure 3. Overview of pages 4. Customizable pages w/ html 5. Customizable pages w/ javascript 6. Customizable images 7. Cascading Style Sheet customization 8. Plug- in customization 9. Tour Suite customization 10. Revisions/New releases communication 11. Product Support 1. Files included ----------------------------------------------------------------------- The following files are included in the Default Pageset: badcookie.html error.html expired.html expiresoon.html help.html login.html nocookie.html nodb.html order.html sitereq.html unauthmodule.html unauthrole.html style.css display/javascript/global.js 2. Instructions to implement directory structure ----------------------------------------------------------------------- If current directory structure is maintained, pages should be functional when unzipped and installed to a local folder. 3. Overview of pages ----------------------------------------------------------------------- badcookie.html This is an error state returned from SMS when the user attempts to login and their browser’s cookie is corrupt. error.html This error page is displayed upon submitting an unrecognized Login Name/Password combination. expired.html This error page is displayed upon submitting a Login Name/Password combination for which the user’s access to the currently relevant resource has expired. With javascript, the expiration date can be displayed. expiresoon.html This interstitial notification page is displayed upon submitting a Login Name/Password for which the user’s access to the currently relevant resource will expire within a predetermined number of days. With javascript, the expiration date can be displayed. help.html This page provides information designed to help users troubleshoot registration and login issues prior to emailing product support. login.html This page informs the user that he or she must register and/or log in to access the site, and provides links to information intended to answer questions users may have. A super-set of options will be built into the code of this page with the intention that only the relevant options will be hand-coded to appear on a case-by-case basis. nocookie.html This error page is displayed upon submitting a Login Name/Password combination when specific SMS cookies are not available. nodb.html This error page is displayed upon submitting a Login Name/Password combination when communication to the SMS database is not possible. order.html This page explains access options, with links to online purchase, renewal options, imprint catalogs, and sales rep locators. A super-set of options will be built into the code of this page with the intention that only the relevant options will be hand-coded to appear on a case-by-case basis. This page is only linked from login.html, expired.html,expiresoon.html, unauthmodule.html, unauthrole.html, and help.html. sitereq.html This informational page provides details of operating system and browser requirements for SMS authentication and login. It is not intended to reflect the needs of a specific volume -- i.e. content-specific plugins. Those items should be incorporated into help information available to logged in users of the site. Sitereq.html is intended as a “self-service” resource for users prior to emailing product support. This page is only linked from the help.html page. unauthmodule.html This error page is displayed when the user’s currently active SMS account does not allow them access to view this content. unauthrole.html This error page is displayed when the user’s role is not that which is required and access is restricted. 4. Customizable pages w/html ----------------------------------------------------------------------- The following pages contain commented code that highlight areas of customization: order.html Comment 5.1 This commented text should be displayed when Online Purchase is a valid option Comment 5.2 Modify link to include product id Comment 5.3 Display the ISBN for the students benefit Comment 5.4 Remove list of links and replace 'publisher's catalog with valid link. Comment 5.5 Uncomment this text if a trial period is offered Comment 5.6 Modify link to include product id make link active Comment 5.7 Display only if renewing online is a valid option for students Comment 5.8 Remove list of links and replace 'sales representative' with valid link to replocator Comment 5.9 Display only if renewing online is a valid option for instructors Comment 5.10 Make renew link active WPS USERS - How To Customize This Page: Make all necessary changes on a local copy of the html. Once complete, upload the manipulated page in the SMS Custom Files. The file must be named order.html to work properly. 5. Customizable Points w/javascript ----------------------------------------------------------------------- The following pages contain commented code that highlight areas of customization using javascript: error.html Comment 9.1 The “Login Name [Insert Textbox]” textbox field should be pre-populated with the text as entered by the user on the login.html page. The password field should be left blank. expired.html Comment 6.1 Display the subscription expiration date expiresoon.html Comment 7.1 Display the subscription expiration date nodb.html Comment 10.1 The “Login Name [Insert Textbox]” textbox field should be pre-populated with the text as entered by the user on the login.html page. The password field should be left blank. sitereq.html Comment 11.1 JavaScript is used to determine the user’s environment variables. From this information, a message is displayed on screen to notify the user if their screen resolution is sufficient to display the default pageset properly. unauthrole.html Comment 8.1 Display the requested role Comment 8.2 Display the requested role Comment 8.3 Display the requested role Comment 8.4 The “Login Name [Insert Textbox]” textbox field should be pre-populated with the text as entered by the user on the login.html page. The password field should be left blank. unauthmodule.htnl Comment 12.1 The “Login Name [Insert Textbox]” textbox field should be pre-populated with the text as entered by the user on the login.html page. The password field should be left blank. To populate these pages correctly, the above data should be passed in the URL by the plugin, then javascript is coded to pull the data from the URL to be displayed on the page. ***Note: If you are using any plugin controlled by CMG, the necessary coding has already been done for you. No changes to the Javascript or Plugin is necessary. 6. Customizable Images ----------------------------------------------------------------------- Upon request .psd are available for all Graphical Headlines for color changes. Upon request .psd are available for all button color changes. Requests can be made to Dena Lohse, dena.lohse@pearsoned.com, 617-848-7439 *You may want to keep all Photoshop sourcefiles in a local directory and not in the production environment Approved imprint images can be obtained at: http://intranet.pearsoned.com/ go to and select "Pearson Branding Program" under Internal Resources, you should see a link for the Logo Bank. The login.html page can display an Approved Book Cover Image and an Approved Partner Logo. These will be displayed on the left side of the page. The recommended (though not required) sizes for these images: partner_cover.gif: width="175" height="200" partner_logo.gif: width="175" height="75" These images should be uploaded to the SMS Custom Files area. If you upload images, for section 508 compliance (Accessibility), you also need to specify appropriate descriptions of the images as "alt text". To specify alt text for the partner_cover.gif image: 1) Copy the file "partner_cover_alt_text.js" to your local disk from either the Default Pageset zip file or from the extranet. 2) Edit the file and add the appropriate alt text within the double quotes. 3) In WPS, upload the file to your SMS Custom Files area. To specify alt text for the partner_logo.gif image: 1) Copy the file "partner_logo_alt_text.js" to your local disk from either the Default Pageset zip file or from the extranet. 2) Edit the file and add the appropriate alt text within the double quotes. 3) In WPS, upload the file to your SMS Custom Files area. 7. Cascading Style Sheets Customization ----------------------------------------------------------------------- The included .css can be customized to adjust the following aspects of the pageset: Background color (page & center content area) Font colors, size, type face *The current color scheme & design reflects usability & accessibility standards. 8. Plug- in Changes, if non CMG supplied plug-in ----------------------------------------------------------------------- The plug-in should be adjusted to start utilizing the following metadata sent in the authentication xml from SMS: - Subscription expiration date - # of days prior to expiration to begin showing "expiring soon" page - Role, if not already required by the application for other purposes The meta data should be included in the url. ***Note: If you are using any plugin controlled by CMG, the necessary coding has already been done for you. No changes to the Javascript or Plugin is necessary. 9. Tour Suite Customization ----------------------------------------------------------------------- The generic tour suite is linked to from login.html and help.html and contains the following tours: Registration – Student Version Registration – Educator Version Online Purchase Tours should only appear if they are applicable to your site. Currently, there are two sets of tours available. Tour Set 1) The set shown above. This is the default. Tour Set 2) The set above without the Online Purchace tour. To use Tour Set 1, no changes are necessary. To use Tour Set 2: 1) Copy the file "tours_link_no_olp.js" to your local disk from either the Default Pageset zip file or from the extranet. 2) Rename the file "tours_link.js". 3) In WPS, upload the file to your SMS Custom Files area. To further customize tour options to addresss specific volume needs, contact Dena Lohse dena.lohse@pearsoned.com, 617-848-7439 10. Revisions/New Releases ----------------------------------------------------------------------- Revisions/New Releases of the pageset can be found in the Subscription Services area of the CMG extranet. Each page contains the version within a comment in the body of the code. When upgrades are made, a notification email will be sent to SMS Release Team members for further dissemination. For WPS and protected content on the imprint sites: Volumes with no customized pages: New versions of the pageset will be uploaded as the Default, and live volumes will automatically receive the benefit of the updated default pages. No action necessary to adopt new releases if you do not customize pages. Volumes with customized pages: Pages that have been customized and uploaded into a custom files directory on a volume will not automatically receive the benefit of the updated default pages. To incorporate changes, the customized pages will need to be modified and the volume repromoted. For non-CMG managed applications/server environments, the BU "owner" of the application is responsible for ensuring pageset updates are incorporated. Minor updates that do not require scripting changes should be incorporated within 30 to 60 days. Major updates that affect core SMS implementation should be scheduled for the next available application release. 11. Product Support ----------------------------------------------------------------------- Product Support Website http://247.support.pearsoned.com/ Email Product Support http://247.support.pearsoned.com/email/index.asp Phone Product Support http://247.support.pearsoned.com/phone/index.asp