Setup Guide V1 (last updated January 4th, 2007)

Designed for the Gen7 Series Templates and Modules

Generation7 Template Specifications:

Introduction

The purpose of creating a set of template product specs is threefold:

  • To provide an expectation for new and repeat customers

  •  To increase customer satisfaction by providing a consistent product spec, provide a high level of product support, and reduce the learning curve

  • To ensure that all templates meet a certain quality level with regards to web standards

Software Compatibility

  • FrontPage 2002 or 2003 for FrontPage templates (Expression Web Designer and SharePoint Designer will eventually replace FP2002.)

  • Dreamweaver MX 2004, or 8 for Dreamweaver templates

  • Fireworks (MX2004, 8) for graphic source files

  • Flash MX 2004, or 8 for Flash movie source files

 Industry Standards

  • Validated XHTML 1.0 Strict. 

  • DWT: Dynamic Web Templates for Microsoft FrontPage or Macromedia Dreamweaver follow DWTIG 1.0.

Website Testing

The following applications are used to test development compatibility:

  •  Microsoft Internet Explorer 5+

  •  Most recent versions of Opera, Netscape, Mozilla, and FireFox

  • Flash Player 7+

Website File Conventions

  • HTML files use .htm extension. The template uses the same extension throughout.

  • No spaces in file names

  • No capital letters in file names

  • Image files in .gif, .jpg, or .png.

Website Template Standards

Design and Layout – This covers the HTML and coding aspects of the design and layout. Requirements for the design itself are discussed in the Design Specifications.

CSS

  • Layout is CSS-based. Layouts using tables refer to CSS for rules.

  • Relative font sizes for all headings and body fonts..

  • Linked style sheets

Navigation

  •  CSS styled navigation bars to comply with XHTML Validation. No need to edit graphic buttons

Fonts

  • Standard system fonts (list here), including fonts used in logos, heading graphics, special graphics, etc.

Images

  • Include the ability to change main image(s) either with direct file substitution or using included graphics source file

  • Images are web-optimized .jpg’s or .pngs.

  • Image files named descriptively – for example, “menubg.gif,” “flash-image1.jpg”

Flash

  • Template does not require Flash program to make changes to Flash text and links. Dynamic variables are used. (update with a text file using notepad, FrontPage, or Dreamweaver)

  • Flash files over 40 kb include preloader.

  • Any text or hyperlinks in Flash movie, apart from links to the root directory, are dynamically updatable. Variables are held in an external text file.

Accessibility issues

  • If Flash is used for navigation, text links should are included somewhere in the page template (such as in the footer).

  • Flash intros include “skip” links on the HTML page.

  • Flash movies with sound should include an obvious “mute sound” link.

  • The SWFObject Flash detection and embed script are used to embed all Flash. This will allow consistent support as well as XHTML validation.

  • Alternative image (background image) is embedded into the template in conjunction with the SWFObject code.

Pages and Content

  • Templates include clear and visible link to documentation on all pages (may be in navigation bar). Labeled as “Setup Manual,” “Customization Information,” “Licensing.” And “Support”.

  • Template pages for each layout are included within the navigation or sub navigation.

  •  Sample content is used (latin), with fictitious names, web sites, addresses, phone numbers, and emails.

Dynamic Web Templates

  • Each column in a layout contains its own editable area.

  • The main content area is labeled as “body1”

  • The main vertical menu area is label as “vertical_menu”

  • The left content area is labeled as “body2”

  • The right content area is labeled as “body3”

  • The page title area is labeled as “special1”

  • The message box area is labeled as “special2” (optional)

Packaging Requirements

  • .zip format.(for Pixelmill packages) .exe format for Lucky Marble / i3dthemes

  • The template package is provided as an immediate downloadable zip / exe file, from your members page.

  • Once downloaded, double click on the .zip / exe file to begin extraction.

  • Please review instructions included in the installation file.

Package Contents

Template package includes several PDF documents and web folders 

  • productname_web (folder): Website package and files to build website.

  • sourcefiles (folder): Included source files (PNG, Flash)

  • licensing.pdf (document): Template license and other legal documents are located in the “licensing-information.pdf”

  • support-information.pdf (document): Support information provided by the designer / developer.

  • read-me-first.pdf (document)

Source Files

Source files are included in the website package, as a separate download file, or as a separate “free” product package if:

  • They are required to change the main image

  • A logo is specifically “integrated” into the design where a simple replacement will be insufficient

  • They are required to change the colors, fonts, text style, etc. of a website page element

  • They contain “styles,” “clipping masks,” or other features which a user may wish to apply to their own elements within the licensing terms

  • For web and graphic designers using this product and requiring the ability to tweak the colors, graphic elements, etc., all source Fireworks MX 2004 / 8 pre-sliced PNG files are included.
 

Back...