Why do I have to use the templates?
The template package that has been created for this project will provide the desired consistent USC look and feel while still allowing the Web designer flexibility in the presentation of individual content. The template items have been tested for browser compatibility and user accessibility. The use of the server side includes (SSI), and cascading style sheets (CSS) within the template will allow updates to be propagated quickly.
Do not attempt to reverse-engineer a template under any circumstance. The template makes reference to standard resources (e.g., images, CSS, JavaScript) that a reproduction may not take into account.

Where are the templates?
The templates can be downloaded directly from the Web Presence site.

How can I avoid common mistakes?
The most common mistake is re-engineering the template. While certain aspects of the template cannot be altered, the system was created to be a starting point and a framework to build on. The template is a frame providing consistently placed navigational regions and a central content area that can be customized by the designer to create a distinctive site. Examples are found here. For example, in the Tool-Tip Split Template (see Template Options), the Left Navigation Bar is divided by the black Tool-Tip Bar into two sections, with a garnet area and white menu items above and a gray area with black menu items below. This design was created to delineate the natural break between two distinct types of menu items. Not all sites have this natural break and thus do not necessarily need the divided Left Navigation Bar. A solid Left Navigation Bar is an acceptable variation to the template.

Other things to consider as you create your site.

Avoid too many menu items in the Left Navigation Bar. The idea is to keep it simple and clear to viewers unfamiliar with your area. Organize your main links in broad categories with short labels such as "Faculty and Staff" and "Departments" as much as possible. Be aware that you can use the Header Navigation Bar and the content area of your page for additional links.
Give your page a little breathing room to make it clean and readable. The USC Web Presence recommends a 15-pixel space between the Header and Left Navigation Bars and the content items (headlines, body text, photos, etc.) on your pages. It is also a good idea to keep at least that same amount of space between content items and the Footer Bar.
Keep your text alignment consistent. The University's design looks best when text in the content area of a page is aligned flush left. Mixing the alignment of heads, subheads, and body text (centered, flush left, and flush right) creates a fragmented feel and can be harder for the viewer to follow.
Clearly label downloadable files. If a menu item links to file formats other than to HTML pages, such as pdf, tiff, or jpeg images, add the extension in parenthesis to the item. For example, "Application Form (pdf)" would be an appropriate label for a downloadable file. This will warn the reader that they will be downloading a file rather than linking to a new page.
Make sure your menu items match your page titles. Even when your title in the banner area remains the same throughout your site, you can set a headline at the top of your content area that matches the menu item, so the reader knows immediately that they have gone to the right page.
Do not use frames. Frames corrupt usability and interfere with search engine indexing and bookmarks.
Avoid "splash" pages. A splash page (a branding page that appears before a site's homepage) frequently adds no useful content to a Web site.
Do not create navigation systems that require Flash, Java, or JavaScript to function. All pages in a site should be reachable with a browser that only understands straight HTML. For instance, many main University Web pages use JavaScript to enhance the navigation with rollovers and tool-tips. These extra features do not appear in browsers without JavaScript support, but the navigation labels and links still work as expected. Enhancing an interface with JavaScript is allowed, but requiring JavaScript for a page to function properly is unacceptable.
Do not build in hit counters. Hit counters typically do not provide accurate or useful content to users. Virtually all Web servers generate log files that can be processed to generate useful statistics for Web masters about user activity.
Do not use blinking text. Blinking text in general is considered an annoyance.
Do not post "Under Construction" notices. If a page is under construction, do not provide a link to it or place it online until it contains useful, relevant content.
Do not post your site until it has been reviewed. Remember to keep your site on a secure server as you build it. The Web Presence Team will provide a design and technical review of your site when you are ready, offer suggestions, and provide support to help you make the transition. An editorial review of your content is also available. If you desire, a University Publications editor will check your content for style, grammar, and accuracy.

Do I have to have my site reviewed?
Yes. The Web Presence Team will be glad to look at your site at any stage to offer design, editorial, or technical suggestions, answer questions, and provide constructive comments to help you through the process. You will need a final review when you have your site complete and before it goes live. E-mail your request for a review to webpresence@sc.edu.

What will a review of my site include?
Currently, the Web Presence Team from University Technology Services and University Publications review sites for design and technical compatibility. If, on the Template Request Form, you indicate a desire for an editorial review, an editor will check your text for style, grammar, and accuracy. Your text should follow the conventions in the University's Editorial Style Guide. From the design perspective, team members will check for things like the proper use of type (typographic style sheets are built into the template), color, spacing, and the overall appearance of the site. The design review may also offer suggestions for photos and organization, but will not alter the general content of the page. This review process is intended to be helpful and is performed with the University's overall Web Presence in mind.

The technical review checks to make sure the template system is used. Source code will be reviewed to ensure that the critical parts of the template are not comprised. Links are spot-checked to make sure there are no dead ends for the user. This review is always done before a site goes live and can be done at different stages of progress as the site is being built and questions arise. It is recommended that sites be designed "behind the scenes" on a separate server to avoid public access during this production phase. Once final approval is given, the site can go live.

Please be aware that the review will take time. The Web Presence Team has many other committments, but will do their best to complete your review in a timely manner. E-mail your request for a review to webpresence@sc.edu.