138919 OTH

Specs/Reqs -------------------- General guidelines All Content text will be provided in PDF format, requiring programmer to copy and paste into HTML documents and removing any hard returns or similar unwanted text artifacts. All Content images will either be provided within a PSD (eg: template assets), or a ZIP file containing appropriately named, sized and optimized JPGs. Recommended naming convention is welcome. All Content text will need to be treated and styled using a thoroughly commented external CSS document. All HTML will need to be thoroughly commented. Any content that diverts from the standard template structure (eg: isolated secondary pages) will be provided in mock-up JPGs for reference. All pages, throughout the site, will feature the main template: top horizontal �header containing pri nav element and header photo, footer element. All pages, except for Product pages, will feature the two vertical columns as well. Total page width is 1050 but live area is 750. the remaining 300 pixels is occupied by 150 pixels of cloud background on each side. Because of this, the left vertical column can take up more horizontal space (see mock ups), but the right column shall remain the same size. Meta Data must be populated on all pages. Main Pages: Primary Navigation: Each �button� will use an alternate �onFocus� graphic If possible, we'd prefer to use text-based replication of the current graphic-based navigation. Doing this would only be acceptable if the graphic look and feel can be replicated in a similar visual outcome. Horizontal Photo: We will supply a set of photos, already cropped and sized, to be used in a rotating manner for all pages. Some pages, which we will specify, will have a static photo which will be specifically chosen to coincide with the content of the page. For example, the B2B (Professionals) landing page will have a photo that is to appear only on that page. Some of these photos will have text superimposed on them, some will not. Structure: All pages will use the template outlined in the provided mock-ups. To be clear, the main template is set up to include a header area, containing the primary navigation (blue) and a header photo just below it. Below that are 2 vertical columns, the left column significantly wider than the right. In secondary pages, when further sub-navigation is needed, this will appear at the top of the right column. If no secondary navigation is needed for a given page, then the right column will contain a number of �modules.� These modules consist of: Sign-up, What the Experts are Saying, Recent Blog Posts) With the exception of �Sign-up� these modules will feature content that is dynamically generated. Upon refresh, content will be populated on a rotating basis. These modules should also have the flexibility to change display order The bottom of the template features a traditional �footer� which will contain any �footer� nav elements and necessary legal designations. Secondary Pages: Secondary Navigation: In some instances, secondary pages will feature a Secondary Nav element. This will be placed at the top of the right column, above any other module content. The �links� should be text links, and when required can feature AJAX-based techology for expanding vertically. There are a couple of secondary page template variables that will need to be accommodated. Any content that diverts from the standard template structure (eg: isolated secondary pages) will be provided in mock-up JPGs for reference. Some of these isolated pages call for a second horizontal area below the header photo which will contain various content presented in a graphic manner. For further clarification, please view secondary page mock-ups. Below this second horizontal area will contain the same configuration of two vertical columns (found in the main template), left one being considerably wider than the right one. Product Pages: All product pages essentially use the same header elements, primary nav and header photo. Below this will feature content strictly related to the actual product interface, except for the �footer� at the bottom. The product content will feature its own navigation schema for navigating within the product content. The product content is only accessible to users who've registered. A detailed requirements document will be provided for the Product interface when needed. Sign-up Page: This page will feature the standard header, footer and vertical column elements, except the left column content will be limited to actual registration data input. (to be provided) CAPTCHA mechanism will need to be built into the sign-up page Log-in Page: This page will feature the standard header, footer and vertical column elements, except the left column content will be limited to actual registration data input. (to be provided) Thanks for Registering Page: This page will feature the standard header, footer and vertical column elements, except the left column content will be limited to something like- �Thanks for Signing Up. You've just started the exciting journey of discovering your True Home. Click here to get started.� Content Updates and Management: Content will be obtained and updated via CVS. Edits must be performed via the Visual Studios Express: VIsual Web Developer tool for managing master files or other components that leverage the .NET 2.0 CLR. Browser and Platform minimums: All code will need to be validated XHTML 1.0 transitional Windows platform compatibility � Windows 2000 and above Explorer 5.5 and above Macintosh Platform compatibility � Mac OSX 10.x Safari and Mozilla compliant