Requirements for Websites
Brand and Style Guide
The NPS Shield
Downloads (Internal Only)
Policies and Requirements
Section 5 Responsibilities, Subsection K
Each subordinate page under a website's top-level home page will have a POC identified for information on that page. Page Maintainers develop and maintain the information that resides on the web server.
Page Maintainers will:
- Ensure that page content and presentation is consistent with Navy and NPS policy per NPS Web Advisory Board guidelines.
- Ensure that all links from pages under their control are appropriate and valid.
- If required, ensure proper access and security controls are in place and operational.
- Ensure that outdated or superseded information is removed from the system. If such material is maintained for historical record, ensure that it is clearly indicated.
- Incorporate a feedback mechanism for users' comments.
Section 6 Requirement
The following are general requirements for NPS websites/pages:
- Publicly accessible NPS websites and pages will present a polished and professional appearance and support intuitive navigation of available information.
- Organizational home pages will clearly identify the organization and its affiliation with NPS.
- Do not copy files from other sources. Information should remain as closely controlled by the source as possible to ensure its currency and accuracy. Reference this information with a link rather than repeat it.
- Do not use or copy copyright material without providing proper credit to the source. This material is usually clearly indicated, but not always. Use caution when using or linking any materials from the Internet.
- Reference (g) prohibits "hogging" network resources. Web pages can consume significant bandwidth if not constructed with care. Website Administrators and Page Maintainers should avoid the use of large, high-resolution graphics and push technology ("webcasting"). Abuse of network resources may result in the loss of network privileges.
- The NPS webmaster will initiate an NPS-wide website review annually to ensure compliance with current informational and operational security directives.
Recommendations for web page design at the Naval Postgraduate School and tenant commands
Prepared by the NPS Web Advisory Board
- Top-level web pages should be considered a directory of information contained in subsequent pages and should not contain detailed subject matter. Specifics should reside on subsequent pages.
- Avoid long lists of hot links on top-level organizational pages; a single link to a separate links page is much more effective.
- Top-level organizational pages should have the same "look and feel" so that users will be able to know when they have navigated off the main pages.
- Web pages are dynamic, evolving documents that can frequently change. ''Under construction" notices should be used sparingly.
- Designers should recognize that graphics consume significant bandwidth. Provide thumbnail graphics of large graphics with a link to the full version. Graphics will also load faster if the height and width are supplied in the Hypertext Mark-up Language source tag.
- Use numbered or bulleted lists to condense text and to break up the page visually.
- If you choose to use a background image or background color, make sure your text is readable. White or light colored backgrounds are the most readable.
- Limit the number of different font styles and colors on a page. A good rule of thumb is to use no more than three different fonts on a page.
- Text and graphics that move can be particularly annoying. Use blinking text, scrolling marquees, animated gifs and Java applets very sparingly, if at all.
- Proofread your pages carefully. Test all the links to make sure they work. Your potential audience may be using a different browser than you are, so it is recommended that you view your pages with more than one browser.
- Regularly review your pages to ensure that all links are still active and all information is still current. Building a web page is just the start!